* Sample in url configuration variable
An example structure for the url property has been added. To prevent the full url from being written base_url + /api/telegram_webhooks
* Minor change
* Added information about Hass.io update process.
Hass.io users end up on this page when an update is available, but then can't see what they have to do. This is because of the the updater component and the inevitable delay in updates getting into the hass.io build.
This update informs users about an updates transition from HA into Hass.io, how to install it, and suggests disabling the updater component to alleviate 'notification stress'.
* Removed 'Note'
Removed 'Note' and left the upgrading section at the bottom of the page.
* Remove double space
* Xiaomi token retrieval moved and extended.
* Misleading sentence removed.
* Additional item added to the trouble shooting section.
* API token reference removed from the Xiaomi Gateway introduction.
* The iOS app method does not work anymore. The ZToken column contains a 96 character encrypted token now. A 32 character token is still needed.
* Add information on the purge_days
That the purge happens every other day is only documented in the code, and in issue #6302. This is to raise the visibility of this, and help people understand that if they restart frequently the purge will never happen.
* Spelling & Grammar fixes
* Added link to Hassio
A Hassio link was added to the 'note' section about avoiding permission errors, but I think we need to add a link up top too so that folks can go see the upgrading section of the Hassio documentation. Thanks
* Update updating.markdown
Mentioning that it's the root of the boot partition the key file needs to be places in (when I first attempted it I presumed it was the root of the partition called "root").
* Documentation for Xiaomi Philips Light component added.
* HA version added.
* Syntax error fixed.
* Section "Retrieving the Access Token" has a central place now.
* Spelling & grammar fixed.
I wasn't sure what the /tablet/tablet section of the state_topic part meant so had to google a bit to figure it out. With this change, users will immediately understand what they should set as the topic.
* Includes 2 vital details to make Alexa work
I spent several hours trying to figure out why this guide didn't work for me and it overlooked two very important things that must be done.
1. either forward 443 requests or change your serving port to 443
2. add "alexa:" to your configuration file. otherwise, the .../api/alexa?api_password=xxxxxxxxx will not exist.
* Minor changes
