FAQ: fixed location of re-add when unavailable (#3650)

esphome · Feb 28, 2024 · 89f7224 · 89f7224
1 parent eb3cfff
commit 89f7224
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/components/deep_sleep.rst b/components/deep_sleep.rst
@@ -23,7 +23,7 @@ to wake up on any RTC pin (``GPIO0``, ``GPIO2``, ``GPIO4``, ``GPIO12``, ``GPIO13
 While in deep sleep mode, the node will not do any work and not respond to any network traffic,
 even Over The Air updates. If the device's entities are appearing as **Unavailable** while your device is actively
 sleeping, this component was likely added after the device was added to Home Assistant. To prevent this behavior,
-you can remove and re-add the device within ESPHome.
+you can remove and re-add the device in Home Assistant.
 
 .. code-block:: yaml
 

diff --git a/guides/faq.rst b/guides/faq.rst
@@ -456,7 +456,7 @@ Why do entities show as Unavailable during deep sleep?
 
 The :doc:`Deep Sleep </components/deep_sleep>` component needs to be present within the config when the device
 is first added to Home Assistant. To prevent entities from appearing as Unavailable, you can remove and re-add the
-device within ESPHome.
+device in Home Assistant.
 
 See Also
 --------