diff --git a/Gemfile.lock b/Gemfile.lock
index 61d62673531..97f57c177c5 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -3,7 +3,7 @@ GEM
   specs:
     addressable (2.7.0)
       public_suffix (>= 2.0.2, < 5.0)
-    chunky_png (1.3.11)
+    chunky_png (1.3.12)
     colorator (1.1.0)
     commonmarker (0.21.0)
       ruby-enum (~> 0.5)
diff --git a/source/_integrations/braviatv.markdown b/source/_integrations/braviatv.markdown
index 3cd489bbb97..142f3e20b9f 100644
--- a/source/_integrations/braviatv.markdown
+++ b/source/_integrations/braviatv.markdown
@@ -42,7 +42,7 @@ If you have previously set up your TV with any Home Assistant instances, you mus
 
 <div class='note warning'>
 
-New setups via `configuration.yaml` file are currently not be supported.
+New setups via `configuration.yaml` file are currently not supported.
 
 </div>
 
diff --git a/source/_integrations/camera.markdown b/source/_integrations/camera.markdown
index 2fd093ffb90..c60d11ec573 100644
--- a/source/_integrations/camera.markdown
+++ b/source/_integrations/camera.markdown
@@ -132,7 +132,7 @@ Turn on camera. Not all camera models support this service, please consult indiv
 
 ### Test if it works
 
-A simple way to test if you have set up your `camera` platform correctly, is to use <img src='/images/screenshots/developer-tool-services-icon.png' alt='service developer tool icon' class="no-shadow" height="38" /> **Services** from the **Developer Tools**. Choose your service from the dropdown menu **Service**, enter something like the sample below into the **Service Data** field, and hit **CALL SERVICE**.
+A simple way to test if you have set up your `camera` platform correctly, is to use **Services** from the **Developer Tools**. Choose your service from the dropdown menu **Service**, enter something like the sample below into the **Service Data** field, and hit **CALL SERVICE**.
 
 ```yaml
 entity_id: camera.living_room_camera
diff --git a/source/_integrations/ecovacs.markdown b/source/_integrations/ecovacs.markdown
index 98fcd6c50b6..743e5e0680d 100644
--- a/source/_integrations/ecovacs.markdown
+++ b/source/_integrations/ecovacs.markdown
@@ -51,6 +51,8 @@ continent:
 
 Note: For some countries, you will need to set `continent` to `ww` (meaning worldwide.) There is unfortunately no way to know the correct settings other than guessing and checking. See the [sucks library protocol documentation](https://github.com/wpietri/sucks/blob/master/protocol.md) for more information about what has been figured out about the Ecovacs servers.
 
+Additional note: There are some issues during the password encoding. Using some special characters (e.g., `-`) in your password does not work.
+
 ### Stability and Reporting Bugs
 
 The library that talks to the Ecovacs servers is in a very early state and still under development. As such, it is likely that not all regions and devices will work at the current time.
diff --git a/source/_integrations/synology.markdown b/source/_integrations/synology.markdown
index fdabff91b72..704f8f5299f 100644
--- a/source/_integrations/synology.markdown
+++ b/source/_integrations/synology.markdown
@@ -10,12 +10,6 @@ ha_domain: synology
 
 The `synology` camera platform allows you to watch the live streams of your [Synology](https://www.synology.com/) Surveillance Station based IP cameras in Home Assistant.
 
-<div class='note'>
-
-Synology has disabled the livestreaming API and the integration is currently broken if you are using Surveillance Station version 8.2.3-5828.
-There is an unsupported preview fix available. (8.2.3-5829) - Instructions can be found [here](https://www.vcloudinfo.com/2019/04/how-to-manually-upgrade-your-synology-surveillance-system-firmware.html) for updating manually.
-
-</div>
 
 ## Configuration