From 151de0cd4839c8958de446fcfd3f2aab53dd98be Mon Sep 17 00:00:00 2001
From: Paulus Schoutsen <paulus@paulusschoutsen.nl>
Date: Mon, 22 Aug 2016 01:25:36 -0700
Subject: [PATCH] Some title tweaks

---
 source/_components/foursquare.markdown |  4 ++--
 source/_components/mqtt.markdown       | 12 ++++++------
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/source/_components/foursquare.markdown b/source/_components/foursquare.markdown
index 7121988a595..b2277da003d 100644
--- a/source/_components/foursquare.markdown
+++ b/source/_components/foursquare.markdown
@@ -28,7 +28,7 @@ Configuration variables:
 - **access_token** (*Required*): A Foursquare API access token.
 - **push_secret** (*Required*): The push secret that Foursquare provides to you in the app dashboard.
 
-#### {% linkable_title Real-Time API %}
+### {% linkable_title Real-Time API %}
 
 The component accepts pushes from Foursquare at `/api/foursquare`. The route does not require authentication.
 
@@ -45,7 +45,7 @@ automation:
       entity_id: script.my_action
 ```
 
-#### {% linkable_title Check ins %}
+### {% linkable_title Check ins %}
 
 To check a user in, use the `foursquare/checkin` service.
 
diff --git a/source/_components/mqtt.markdown b/source/_components/mqtt.markdown
index f4388c54a67..6a106b62fe6 100644
--- a/source/_components/mqtt.markdown
+++ b/source/_components/mqtt.markdown
@@ -48,7 +48,7 @@ Configuration variables:
 
 The MQTT component needs you to run an MQTT broker for Home Assistant to connect to. There are four options, each with various degrees of ease of setup and privacy.
 
-#### {% linkable_title Use the embedded broker %}
+### {% linkable_title Embedded broker %}
 
 Home Assistant contains an embedded MQTT broker. If no broker configuration is given, the [HBMQTT broker](https://pypi.python.org/pypi/hbmqtt) is started and Home Asssistant connects to it. Embedded broker default configuration:
 
@@ -75,7 +75,7 @@ mqtt:
     # http://hbmqtt.readthedocs.org/en/latest/references/broker.html#broker-configuration
 ```
 
-#### {% linkable_title Run your own %}
+### {% linkable_title Run your own %}
 
 Most private option but requires a bit more work. There are two free and open-source brokers to pick from: [Mosquitto](http://mosquitto.org/) and [Mosca](http://www.mosca.io/).
 
@@ -94,7 +94,7 @@ mqtt:
 There is an issue with the Mosquitto package included in Ubuntu 14.04 LTS. Specify `protocol: 3.1` in your MQTT configuration to work around this issue.
 </p>
 
-#### {% linkable_title Public MQTT %}
+### {% linkable_title Public broker %}
 
 The Mosquitto project runs a [public broker](http://test.mosquitto.org). Easiest to setup but there is 0 privacy as all messages are public. Use this only for testing purposes and not for real tracking of your devices.
 
@@ -110,7 +110,7 @@ mqtt:
   certificate: /home/paulus/downloads/mosquitto.org.crt
 ```
 
-#### {% linkable_title CloudMQTT %}
+### {% linkable_title CloudMQTT %}
 
 [CloudMQTT](https://www.cloudmqtt.com) is a hosted private MQTT instance that is free up to 10 connected devices. This is enough to get started with for example [OwnTracks](/components/device_tracker.owntracks/) and give you a taste of what is possible.
 
@@ -174,7 +174,7 @@ The MQTT component will register the service `publish` which allows publishing m
 
 ### {% linkable_title Logging %}
 
-The [logger](/components/logger/) component allow the logging of received MQTT messages. 
+The [logger](/components/logger/) component allow the logging of received MQTT messages.
 
 ```yaml
 # Example configuration.yaml entry
@@ -228,7 +228,7 @@ $ mosquitto_sub -h 127.0.0.1 -v -t "home-assistant/#"
 For the embeeded MQTT broker the command looks like the sample below.
 
 ```bash
-$ mosquitto_sub -v -V mqttv311 -t "#" 
+$ mosquitto_sub -v -V mqttv311 -t "#"
 ```
 
 Add the username `homeassistant` and your API password if needed.