Fix file extension of configuration file (#6238)

source/_components/binary_sensor.pilight.markdown

@@ -39,7 +39,7 @@ Configuration variables:
 A full configuration example could look like this:
 
 ```yaml
-# Example configuration.yml entry
+# Example configuration.yaml entry
 binary_sensor:
   - platform: pilight
     name: 'Motion'

source/_components/cover.aladdin_connect.markdown

@@ -19,14 +19,16 @@ The `aladdin_connect` cover platform lets you control Genie Aladdin Connect gara
 Only doors that are owned by your Aladdin Connect account will be available. Doors that your account has been granted shared access to are not yet supported.
 </p>
 
+## {% linkable_title Configuration %}
+
 To use your Aladdin Connect cover in your installation, add the following to your `configuration.yaml` file:
 
 ```yaml
-# Example configuration.yml entry
+# Example configuration.yaml entry
 cover:
   - platform: aladdin_connect
-    username: user@email.com
+    username: YOUR_USERNAME
-    password: password
+    password: YOUR_PASSWORD
 ```
 
 {% configuration %}

source/_components/lock.mqtt.markdown

@@ -101,8 +101,9 @@ In this section you will find some real life examples of how to use this lock.
 
 The example below shows a full configuration for a MQTT lock.
 
+{% raw %}
 ```yaml
-# Example configuration.yml entry
+# Example configuration.yaml entry
 lock:
   - platform: mqtt
     name: Frontdoor
@@ -113,8 +114,9 @@ lock:
     optimistic: false
     qos: 1
     retain: true
-    value_template: '{% raw %}{{ value.x }}{% endraw %}'
+    value_template: '{{ value.x }}'
 ```
+{% endraw %}
 
 Keep an eye on retaining messages to keep the state as you don't want to unlock your door by accident when you restart something.
 

source/_components/sensor.pilight.markdown

@@ -42,7 +42,7 @@ This section shows a real life example how to use values of a weather station.
 
 
 ```yaml
-# Example configuration.yml entry
+# Example configuration.yaml entry
 sensor:
   - platform: pilight
     name: 'Temperature'

source/_components/sensor.radarr.markdown

@@ -50,7 +50,7 @@ In this section you find some real life examples of how to use this sensor.
 ### {% linkable_title Get Episodes airing in next 2 days %}
 
 ```yaml
-# Example configuration.yml entry
+# Example configuration.yaml entry
 sensor:
   - platform: radarr
     api_key: YOUR_API_KEY
@@ -65,7 +65,7 @@ sensor:
 SSL may run on a different port than the default (7878). The SSL port can be bound to any port in Radarr, so it should be set in the config here (unless it is changed to 7878).
 
 ```yaml
-# Example configuration.yml entry
+# Example configuration.yaml entry
 sensor:
   - platform: radarr
     api_key: YOUR_API_KEY
@@ -80,7 +80,7 @@ sensor:
 ### {% linkable_title Get disk space for all storage locations %}
 
 ```yaml
-# Example configuration.yml entry
+# Example configuration.yaml entry
 sensor:
   - platform: radarr
     api_key: YOUR_API_KEY
@@ -94,7 +94,7 @@ sensor:
 The storage locations Radarr returns are in the system page and in some cases this can list duplicates if sub paths are mounted separately. By listing paths to include, you can choose what data is reported by the sensor.
 
 ```yaml
-# Example configuration.yml entry
+# Example configuration.yaml entry
 sensor:
   - platform: radarr
     api_key: YOUR_API_KEY
@@ -112,7 +112,7 @@ The Radarr API returns available space in bytes, but this sensor will default to
 *This calculation is done using base 2 math, and may differ from systems calculating using base 10 math.*
 
 ```yaml
-# Example configuration.yml entry
+# Example configuration.yaml entry
 sensor:
   - platform: radarr
     api_key: YOUR_API_KEY

source/_components/sensor.sonarr.markdown

@@ -53,7 +53,7 @@ In this section you find some real life examples of how to use this sensor.
 ### {% linkable_title Get Episodes airing in next 2 days %}
 
 ```yaml
-# Example configuration.yml entry
+# Example configuration.yaml entry
 sensor:
   - platform: sonarr
     api_key: YOUR_API_KEY
@@ -68,7 +68,7 @@ sensor:
 SSL may run on a different port than the default (8989). The SSL port can be bound to any port in Sonarr, so it should be set in the config here (unless it is changed to 8989). See the [Sonarr site](https://github.com/Sonarr/Sonarr/wiki/SSL) for details on SSL in Sonarr.
 
 ```yaml
-# Example configuration.yml entry
+# Example configuration.yaml entry
 sensor:
   - platform: sonarr
     api_key: YOUR_API_KEY
@@ -83,7 +83,7 @@ sensor:
 ### {% linkable_title Get disk space for all storage locations %}
 
 ```yaml
-# Example configuration.yml entry
+# Example configuration.yaml entry
 sensor:
   - platform: sonarr
     api_key: YOUR_API_KEY
@@ -97,7 +97,7 @@ sensor:
 The storage locations Sonarr returns are in the system page and in some cases this can list duplicates if sub paths are mounted separately. By listing paths to include, you can choose what data is reported by the sensor.
 
 ```yaml
-# Example configuration.yml entry
+# Example configuration.yaml entry
 sensor:
   - platform: sonarr
     api_key: YOUR_API_KEY
@@ -115,7 +115,7 @@ The Sonarr API returns available space in bytes, but this sensor will default to
 *This calculation is done using base 2 math, and may differ from systems calculating using base 10 math.*
 
 ```yaml
-# Example configuration.yml entry
+# Example configuration.yaml entry
 sensor:
   - platform: sonarr
     api_key: YOUR_API_KEY