Fixes

changelog/v1.10.0.rst

@@ -138,7 +138,7 @@ Other notable changes:
   where the error appeared. Try it, it's so much better. Next step will be to upgrade to a better YAML reader
   to provide better error messages when the YAML syntax is invalid.
 - Added a bunch of guides (and helpers) for creating custom components. Also new: ``esphomeyaml.libraries``,
-  ``esphomeyaml.includes`` and ``esphomeyaml.platformio_options`` (:doc:`/components/esphomeyaml`)
+  ``esphomeyaml.includes`` and ``esphomeyaml.platformio_options`` (:doc:`/components/esphome`)
 - Saved a lot of flash space on ESP8266 boards. Previously, platformio would allocate about 1/4 of flash for SPIFFS,
   but esphomelib doesn't use that so now you have that as extra storage. Thanks `@brandond <http://github.com/brandond>`
 - You can now use Home Assistant to get time in ESPHome, so no more need for SNTP. See :ref:`time`.

changelog/v1.7.0.rst

@@ -77,15 +77,15 @@ New Features
   can be used to tell esphomelib what to do if the wakeup pin is already in the wakeup level when attempting
   to enter deep sleep. 🛌
 
-- There are two new triggers available now: :ref:`esphomeyaml.on_boot <esphomeyaml-on_boot>` and
-  :ref:`esphomeyaml.on_shutdown <esphomeyaml-on_shutdown>` with which you can do some advanced cleanup/setup
+- There are two new triggers available now: :ref:`esphomeyaml.on_boot <esphome-on_boot>` and
+  :ref:`esphomeyaml.on_shutdown <esphome-on_shutdown>` with which you can do some advanced cleanup/setup
   on boot and shutdown of the node.
 
 - All Hass.io add-on builds have now been more or less completely automated using a private Gitlab server. You
   can find all the new docker files `here <https://github.com/OttoWinter/esphomeyaml/tree/master/docker>`__.
 
 - Added a new ``build_path`` option in the ``esphomeyaml`` section with which you can customize where
-  esphomeyaml stores the platformio project files. See :doc:`/components/esphomeyaml`.
+  esphomeyaml stores the platformio project files. See :doc:`/components/esphome`.
 
 Breaking Changes
 ****************

changelog/v1.8.0.rst

@@ -114,7 +114,7 @@ Other notable changes
 - Fixed YAML anchors not working (you can now prefix keys with ``.`` to make esphomeyaml ignore them)
 - Made Dallas and DHT temperature sensor a bit more reliable by making the code a bit more efficient and thus resolving some timing issues.
 - A ``heartbeat`` filter has been added to :ref:`binary sensors <binary_sensor-filters>`.
-- The :ref:`esphomeyaml-on_loop` trigger has been added.
+- The :ref:`esphome-on_loop` trigger has been added.
 - esphomeyaml now know about more ESP8266/ESP32 boards, so now you can use the board-specific pin
   names with even more board types.
 - The mqtt client has a new option ``shutdown_message`` which will be sent when the board shuts down safely.

changelog/v1.9.0.rst

@@ -30,7 +30,7 @@ awesome things with DIY hardware!
 
 The features I'm particularly excited about are:
 
-* :ref:`esphomeflasher <esphomeflasher>` - Experiencing problems flashing esphomelib firmwares using esphomeyaml?
+* :ref:`esphomeflasher <esphome-flasher>` - Experiencing problems flashing esphomelib firmwares using esphomeyaml?
   No problem, esphomeflasher is a tool designed to make that super easy. Just let esphomeyaml generate the binary and flash
   from your PC.
 * :doc:`Over-the-Air Updates </components/ota>` have been completely re-written to make them a lot more
@@ -74,9 +74,9 @@ New Features
 
 - Compiling for ESP32s is now possible on RPis 🎉
 
-- esphomelib now has a new tool: `esphomeflasher <https://github.com/OttoWinter/esphomeflasher>`__ to simplify
+- esphomelib now has a new tool: `esphomeflasher <https://github.com/esphome/esphome-flasher>`__ to simplify
   flashing on Windows/MacOS machines **without having to install esphomeyaml**. So if esphomeyaml for some reason
-  can't find your USB port, you now can use the esphomeflasher app. See :ref:`esphomeflasher`.
+  can't find your USB port, you now can use the esphomeflasher app. See :ref:`esphome-flasher`.
 
 - ESP8266s now save the states of lights/switches/... internally and restores them on boot.
   Additionally, esphomelib can now operate in fully offline mode if your WiFi network goes down

components/esphome.rst

@@ -66,7 +66,7 @@ Automations:
 .. _esphome-esphome_core_version:
 
 ``esphome_core_version``
-----------------------
+------------------------
 
 With the ``esphome_core_version`` parameter you can tell ESPHome which version of the C++ framework
 to use when compiling code. For example, you can configure using the most recent (potentially unstable)

cookbook/h801.rst

@@ -59,7 +59,9 @@ and the :doc:`ESP8266 Software PWM output </components/output/esp8266_pwm>` comp
         white: pwm_w
 
 
-Make your node in the esphome dashboard and compile/upload it. (if it fails OTA it must be uploaded manually with your favorite ESP flasher, e.g. :ref:`esphomeflasher <esphomeflasher>`)
+Make your node in the esphome dashboard and compile/upload it.
+(if it fails OTA it must be uploaded manually with your favorite ESP flasher,
+e.g. :ref:`esphome-flasher <esphome-flasher>`)
 
 .. figure:: images/gpio.jpg
     :align: center

guides/automations.rst

@@ -337,7 +337,7 @@ All Actions
 - :ref:`fan.toggle <fan-toggle_action>` / :ref:`fan.turn_off <fan-turn_off_action>` / :ref:`fan.turn_on <fan-turn_on_action>`
 - :ref:`output.turn_off <output-turn_off_action>` / :ref:`output.turn_on <output-turn_on_action>` / :ref:`output.set_level <output-set_level_action>`
 - :ref:`deep_sleep.enter <deep_sleep-enter_action>` / :ref:`deep_sleep.prevent <deep_sleep-prevent_action>`
-- :ref:`sensor.template.publish <sensor-template-publish_action>` / :ref:`binary_sensor.template.publish <binary_sensor.template.publish_action>` /
+- :ref:`sensor.template.publish <sensor-template-publish_action>` / :ref:`binary_sensor.template.publish <binary_sensor-template-publish_action>` /
   :ref:`cover.template.publish <cover-template-publish_action>` / :ref:`switch.template.publish <switch-template-publish_action>` /
   :ref:`text_sensor.template.publish <text_sensor-template-publish_action>`
 

guides/contributing.rst

@@ -212,19 +212,11 @@ Build
 *****
 .. note::
 
-    The easiest way is to use the `esphomedocs docker image <https://hub.docker.com/r/ottowinter/esphomedocs/>`__:
-
-    On Linux
+    The easiest way is to use the `esphome-docs docker image <https://hub.docker.com/r/esphome/esphome-docs/>`__:
 
     .. code-block:: bash
 
-        docker run --rm -v "$PWD/":/data -p 8000:8000 -it ottowinter/esphomedocs
-
-    On Windows (PowerShell)
-
-    .. code-block:: powershell
-
-        docker run --rm -v ${PWD}/:/data -p 8000:8000 -it ottowinter/esphomedocs
+        docker run --rm -v "${PWD}/":/data -p 8000:8000 -it esphome/esphome-docs
 
     And then go to ``<CONTAINER_IP>:8000`` in your browser.
 

guides/getting_started_command_line.rst

@@ -162,7 +162,7 @@ Bonus: ESPHome dashboard
 ESPHome features a dashboard that you can use to easily manage your nodes
 from a nice web interface. It was primarily designed for
 :doc:`the Hass.io add-on <getting_started_hassio>`, but also works with a simple command on
-*nix machines (sorry, no windows).
+\*nix machines (sorry, no windows).
 
 To start the ESPHome dashboard, simply start ESPHome with the following command
 (with ``config/`` pointing to a directory where you want to store your configurations)