diff --git a/source/_integrations/smarthab.markdown b/source/_integrations/smarthab.markdown
index 382f1014c6e..aa317d8b391 100644
--- a/source/_integrations/smarthab.markdown
+++ b/source/_integrations/smarthab.markdown
@@ -13,7 +13,7 @@ ha_codeowners:
ha_domain: smarthab
---
-If your home is fitted with [SmartHab](https://www.smarthab.fr/en/home/)'s
+If your home is fitted with [SmartHab](https://smarthab.fr/index.php/home-en)'s
devices and you have access to their app-based services, you will be able
to control your lights and shutters with the SmartHab integration for Home
Assistant.
diff --git a/source/_integrations/velux.markdown b/source/_integrations/velux.markdown
index 6aeca027e3c..4272304154d 100644
--- a/source/_integrations/velux.markdown
+++ b/source/_integrations/velux.markdown
@@ -13,7 +13,7 @@ ha_domain: velux
[Velux](https://www.velux.com/) integration for Home Assistant allows you to connect to a Velux KLF 200 interface, to control [io-homecontrol](http://www.io-homecontrol.com) devices like windows and blinds. The module allows you to start scenes configured within KLF 200.
-At least firmware version > 2.0.0.0 is required on the KLF 200 device. The firmware images may be obtained [here](https://www.velux.com/api/klf200) and may be imported via the webinterface of your KLF 200.
+At least firmware version > 2.0.0.0 is required on the KLF 200 device. The firmware images may be obtained [here](https://www.velux.com/klf200) and may be imported via the webinterface of your KLF 200.
There is currently support for the following device types within Home Assistant:
@@ -27,8 +27,8 @@ A `velux` section must be present in the `configuration.yaml` file and contain t
```yaml
# Example configuration.yaml entry
velux:
- host: "192.168.1.23"
- password: "VELUX_PASSWORD"
+ host: IP_ADDRESS
+ password: VELUX_PASSWORD
```
{% configuration %}
diff --git a/source/_posts/2016-05-21-release-020.markdown b/source/_posts/2016-05-21-release-020.markdown
index 355de586afa..c2ad7797887 100644
--- a/source/_posts/2016-05-21-release-020.markdown
+++ b/source/_posts/2016-05-21-release-020.markdown
@@ -8,7 +8,7 @@ author_twitter: balloob
categories: Release-Notes
---
-
+
Tons of new supported things in 0.20.
diff --git a/source/_posts/2016-07-30-custom-frontend-panels--jupyter-notebooks--directv.markdown b/source/_posts/2016-07-30-custom-frontend-panels--jupyter-notebooks--directv.markdown
index c38afccea8b..ab81d5afd8e 100644
--- a/source/_posts/2016-07-30-custom-frontend-panels--jupyter-notebooks--directv.markdown
+++ b/source/_posts/2016-07-30-custom-frontend-panels--jupyter-notebooks--directv.markdown
@@ -20,7 +20,7 @@ The brand-new [iFrame panel component][iframe_panel] allows you to add other web
I would like to do a shoutout to [@fabianhjr]. He has started adding [typing] data ([PEP484]) to the Home Assistant core. This will help us identify issues before they are released.
-
+
- Frontend: Support for [iFrame panels][iframe_panel] to adding other sites to sidebar ([@balloob])
- Allow components to register [custom frontend panels][custom-panels] ([@balloob])
diff --git a/source/_posts/2016-09-10-notify-group-reload-api-pihole.markdown b/source/_posts/2016-09-10-notify-group-reload-api-pihole.markdown
index 8481d2f683a..d6ca4e749ed 100644
--- a/source/_posts/2016-09-10-notify-group-reload-api-pihole.markdown
+++ b/source/_posts/2016-09-10-notify-group-reload-api-pihole.markdown
@@ -32,7 +32,7 @@ The validation of the configuration is still on-going. Approximately 80 % is don
### All changes
-
+
- Light: Added bitfield to Flux LED since we are supporting effects ([@tchellomello])
- Device tracker: [Owntracks] waypoint import ([@pavoni])