Fix broken links

docs/asyncio_index.md

@@ -15,5 +15,5 @@ For a task to be able to suspend itself, all code that it calls has to have this
 
 The backwards compatible API works by scheduling a task from a different thread and blocking that thread until the task has been processed by the event loop.
 
-[0.29]: /blog/2016/09/29/async-sleepiq-emoncms-stocks/
+[0.29]: https://www.home-assistant.io/blog/2016/09/29/async-sleepiq-emoncms-stocks/
 [ben]: https://github.com/bbangert/

docs/development_checklist.md

@@ -9,5 +9,5 @@ Before you commit any changes, check your work against these requirements:
 - New dependencies are added to `requirements_all.txt` (if applicable), using `script/gen_requirements_all.py`
 - The `.coveragerc` file is updated to exclude your platform if there are no tests available or your new code uses a third-party library for communication with the device, service, or sensor
 - Documentation is developed for [home-assistant.io](/)
-   * It's OK to start with adding a docstring with configuration details (for example, sample entry for `configuration.yaml` file) to the file header. Visit the [website documentation](documentation_index.md) for more information about contributing to [home-assistant.io](https://github.com/home-assistant/home-assistant.github.io).
+   * It's OK to start with adding a docstring with configuration details (for example, sample entry for `configuration.yaml` file) to the file header. Visit the [website documentation](https://www.home-assistant.io/developers/documentation/) for more information about contributing to [home-assistant.io](https://github.com/home-assistant/home-assistant.github.io).
 

docs/hassio_debugging.md

@@ -4,7 +4,7 @@ title: "Debugging Hass.io"
 
 > This section is not for users. Use the [SSH add-on] to SSH into Hass.io. This is for <b>developers</b> of Hass.io. Do not ask for support if you are using these options.
 
-[SSH add-on]: /addons/ssh/
+[SSH add-on]: https://www.home-assistant.io/addons/ssh/
 
 The following debug tips and tricks are for people who are running the Hass.io image and are working on the base image. If you use the generic Linux installer script, you should be able to access your host and logs as per your host.
 

docs/internationalization_custom_component_localization.md

@@ -5,7 +5,7 @@ title: "Custom Component Localization"
 ## Translation Strings
 Unlike localized strings merged in the home-assistant repository, custom components cannot take advantage of Lokalise for user submitted translations. However, custom component authors can still include translation with their components. These will be read from the `.translations` directory, adjacent to the component source file. They are named `<component/platform name>.<language_code>.json`, unless the custom component exists in its own directory, in which case the file is simply named `<language_code>.json` in the `.translations` directory.
 
-These files follow the same formatting as [backend translation string files](/developers/internationalization/backend_localization/), but a copy will exist for each translated language.
+These files follow the same formatting as [backend translation string files](internationalization_backend_localization.md), but a copy will exist for each translated language.
 
 The language codes follow the [BCP47](https://tools.ietf.org/html/bcp47) format. The [frontend translation files](https://github.com/home-assistant/home-assistant-polymer/tree/master/translations) can also be referred to if you are unsure of the correct language code to use.