Various fixes

source/_components/binary_sensor.flic.markdown

@@ -65,6 +65,7 @@ timeout:
 If discovery is enabled, you can add a new button by pressing it for at least 7 seconds. The button will be paired with the flic service and added to Home Assistant. Otherwise, you have to manually pair it with the flic service. The Home Assistant platform will not scan for new buttons and will only connect to buttons already paired.
 
 #### {% linkable_title Timeout %}
+
  When the flic button is triggered while disconnected from flic service, it will queue all events and try to connect and transmit them as soon as possible. The timeout variable can be used to stop events from triggering if too much time passed between the action and the notification in Home Assistant.
 
 #### {% linkable_title Events %}

source/_components/binary_sensor.rfxtrx.markdown

@@ -33,7 +33,7 @@ binary_sensor:
   automatic_add: true
 ```
 
-Open your local home-assistant web UI and go to the "states" page.
+Open your Home Assistant frontend and go to the "states" page.
 Then make sure to trigger your sensor. You should see a new entity
 appear in the *Current entities* list, starting with "binary_sensor."
 and some hexadecimal digits. Those hexadecimal digits are your device id.

source/_components/homekit.markdown

@@ -310,4 +310,4 @@ filter:
     - light
 ```
 
-Restart Home-Assistant and re-attempt pairing - a persistent status should now correctly appear.
+Restart Home Assistant and re-attempt pairing - a persistent status should now correctly appear.

source/_components/media_player.aquostv.markdown

@@ -38,7 +38,7 @@ Configuration variables:
 
 <p class='note warning'>
 When you set **power_on_enabled** as True, you have to turn on your TV on the first time with the remote.
-Then you will be able to turn on with Home-Assistant.
+Then you will be able to turn on with Home Assistant.
 Also, with **power_on_enabled** as True, the Aquos logo on your TV will stay on when you turn off the TV and your TV could consumes more power.
 </p>
 

source/_components/media_player.kodi.markdown

@@ -17,7 +17,7 @@ ha_iot_class: "Local Push"
 
 The `kodi` platform allows you to control a [Kodi](http://kodi.tv/) multimedia system from Home Assistant.
 
-The preferred way to set up the Kodi platform is by enabling the [discovery component](https://www.home-assistant.io/components/discovery/) which requires enabled [web interface](https://kodi.wiki/view/Web_interface) on your Kodi installation.
+The preferred way to set up the Kodi platform is by enabling the [discovery component](/components/discovery/) which requires enabled [web interface](https://kodi.wiki/view/Web_interface) on your Kodi installation.
 
 In case the discovery does not work, or you need specific configuration variables, you can add the following to your `configuration.yaml` file:
 
@@ -39,7 +39,7 @@ port:
   type: integer
   default: 8080
 tcp_port:
-  description: The TCP port number. Used for websocket connections to Kodi.
+  description: The TCP port number. Used for WebSocket connections to Kodi.
   required: false
   type: integer
   default: 9090
@@ -48,7 +48,7 @@ name:
   required: false
   type: string
 proxy_ssl:
-  description: Connect to kodi with HTTPS and WSS. Useful if Kodi is behind an SSL proxy.
+  description: Connect to Kodi with HTTPS and WSS. Useful if Kodi is behind an SSL proxy.
   required: false
   type: boolean
   default: false
@@ -69,7 +69,7 @@ turn_off_action:
   required: false
   type: list
 enable_websocket:
-  description: Enable websocket connections to Kodi via the TCP port. The websocket connection allows Kodi to push updates to Home Assistant and removes the need for Home Assistant to poll. If websockets don't work on your installation this can be set to `false`.
+  description: Enable websocket connections to Kodi via the TCP port. The WebSocket connection allows Kodi to push updates to Home Assistant and removes the need for Home Assistant to poll. If websockets don't work on your installation this can be set to `false`.
   required: false
   type: boolean
   default: true

source/_components/nuimo_controller.markdown

@@ -64,4 +64,4 @@ Troubleshooting:
 
 - install the newest version of [pygattlib](https://bitbucket.org/OscarAcena/pygattlib) from the repository, either because there is no binary package for your system or the pip version contains errors, with `pip install hg+https://bitbucket.org/OscarAcena/pygattlib --target $HOME/.homeassistant/deps`.
 (Dependencies of pygattlib: `sudo apt-get install pkg-config libboost-python-dev libboost-thread-dev libbluetooth-dev libglib2.0-dev python-dev`)
-Then invoke home-assistant with `hass --skip-pip`.
+Then invoke Home Assistant with `hass --skip-pip`.

source/_components/sensor.sensehat.markdown

@@ -42,8 +42,9 @@ Configuration variables:
 #### Customizing the Sense HAT data
 
 **Format the sensor values**
-Add the following to your `sensor`
+Add the following to your `sensor`:
 
+{% raw %}
 ```yaml
 # Example configuration.yaml entry
 sensor:
@@ -56,18 +57,19 @@ sensor:
   - platform: template
     sensors:
       sensehat_temperature:
-        value_template: '{% raw %}{{ states.sensor.temperature.state | round(1) }}{% endraw %}'
+        value_template: '{{ states.sensor.temperature.state | round(1) }}'
         unit_of_measurement: '°C'
       sensehat_pressure:
-        value_template: '{% raw %}{{ states.sensor.pressure.state | round(1) }}{% endraw %}'
+        value_template: '{{ states.sensor.pressure.state | round(1) }}'
         unit_of_measurement: 'mb'
       sensehat_humidity:
-        value_template: '{% raw %}{{ states.sensor.humidity.state | round(1) }}{% endraw %}'
+        value_template: '{{ states.sensor.humidity.state | round(1) }}'
         unit_of_measurement: '%'
 ```
+{% endraw %}
 
 **Give the values friendly names & icons**
-Add the following to your `customize`
+Add the following to your `customize`:
 
 ```yaml
 # Example configuration.yaml entry
@@ -84,7 +86,7 @@ customize:
 ```
 
 **Create a group**
-Add the following to your `groups`
+Add the following to your `groups`:
 
 ```yaml
 # Example configuration.yaml entry
@@ -106,9 +108,11 @@ group:
 
 
 ### Directions for installing on Raspberry Pi All-In-One installer and HASSbian:
+
 Here are the steps to make the _SenseHAT_ sensor work _successfully_ with the virtual environment versions.
 
 #### Install SenseHAT package to _homeassistant_venv_
+
 ```bash
 # switch to the homeassistant_venv environment
 sudo -u homeassistant -H -s
@@ -118,7 +122,9 @@ source /srv/homeassistant/homeassistant_venv/bin/activate
 pip3 install sense-hat
 # be patient, this will take a long while
 ```
+
 #### Return to `pi`
+
 Type `exit` to quit out of the _homeassistant_venv_ back to your `pi` environment.
 
 As all of the following steps should be under the `pi` user environment.
@@ -141,8 +147,8 @@ ln -s /usr/lib/python3/dist-packages/RTIMU.cpython-35m-arm-linux-gnueabihf.so /s
 sudo reboot
 ```
 
-Unfortunately enabling the SenseHAT Sensor component for a Virtual Environment install of Home-Assistant fails with errors.
-_(The Raspberry Pi All-In-One installer and HASSbian both run Home-Assistant in an virtual environment)._
+Unfortunately enabling the SenseHAT Sensor component for a Virtual Environment install of Home Assistant fails with errors.
+_(The Raspberry Pi All-In-One installer and HASSbian both run Home Assistant in an virtual environment)._
 These issues have been discussed in the repository issue (#5093)[https://github.com/home-assistant/home-assistant/issues/5093)
 
 This fix has been tested with a clean install of:
@@ -151,6 +157,6 @@ This fix has been tested with a clean install of:
 
 and
 
-* [Home-Assistant 0.37.1](/getting-started/installation-raspberry-pi-all-in-one/)
+* [Home Assistant 0.37.1](/getting-started/installation-raspberry-pi-all-in-one/)
 
 For setting up the Sense HAT's RGB LED matrix as lights within Home Assistant, please see the [Sense HAT light component](/components/light.sensehat/).