Terminology: standardize spelling of three dots menu (#39825)

source/_docs/automation/using_blueprints.markdown

@@ -75,7 +75,7 @@ The quickest way to get these changes, is by re-importing the blueprint. This wi
 ### To re-import a blueprint
 
 1. Go to **{% my blueprints title="Settings > Automations & Scenes > Blueprints" %}**.
-2. On the blueprint that you want to re-import, select the three-dot menu, and select **Re-import blueprint**.
+2. On the blueprint that you want to re-import, select the three dots {% icon "mdi:dots-vertical" %} menu, and select **Re-import blueprint**.
 
 ## Updating an imported blueprint in YAML
 

source/_docs/configuration/troubleshooting.markdown

@@ -127,7 +127,7 @@ Once you enable debug logging, you ideally need to make the error happen. Run yo
 
 ### Download diagnostics
 
-After you download logs, you will also want to download the diagnostics for the integration giving you trouble. If the integration provides diagnostics, it will appear in the three dot menu next to the integration configuration.
+After you download logs, you will also want to download the diagnostics for the integration giving you trouble. If the integration provides diagnostics, it will appear in the three dots {% icon "mdi:dots-vertical" %} menu next to the integration configuration.
 
 <p class='img'>
   <img src='/images/docs/configuration/download-diagnostics.png' alt='Example of Download Diagnostics'>

source/_docs/organizing/areas.markdown

@@ -93,7 +93,7 @@ Follow these steps to delete an area. It will be removed from all the floors it
 If you used this area in automations or script as targets, or with voice assistant, these will no longer work.
 
 1. Go to {% my areas title="**Settings** > **Areas, labels & zones**" %} and select the area card.
-2. In the top right corner, select the three dot menu. Then, select **Delete**.
+2. In the top right corner, select the three dots {% icon "mdi:dots-vertical" %} menu. Then, select **Delete**.
 
     ![Delete area](/images/organizing/area_delete.png)
 

source/_docs/organizing/categories.markdown

@@ -52,7 +52,7 @@ To rename or delete a category, follow these steps:
 2. In the top left, select the **Filters** button.
 
     ![Select the filter button](/images/organizing/filters_01.png)
-3. In the list, find the category you want to edit and select the three dot menu next to it.
+3. In the list, find the category you want to edit and select the three dots {% icon "mdi:dots-vertical" %} menu next to it.
 4. Select **Edit category** or **Delete category**.
 
     ![Screenshot showing the edit and delete buttons for categories](/images/organizing/edit-delete-category.png)

source/_docs/tools/dev-tools.markdown

@@ -28,7 +28,7 @@ The Developer Tools is meant for **all** (not just for the developers) to quickl
 
 The YAML tab provides buttons to trigger a check of configuration files and to reload the configuration. Reloading is needed to apply changes that you've made to the configuration.
 
-It is almost the same as the option under **Settings** > three dot menu (top right) > **Restart Home Assistant** > **Quick reload**. The only difference is that **Quick reload** reloads all the configuration, whereas this YAML tab allows you to only reload one specific configuration at a time.
+It is almost the same as the option under **Settings** > three dots {% icon "mdi:dots-vertical" %} menu (top right) > **Restart Home Assistant** > **Quick reload**. The only difference is that **Quick reload** reloads all the configuration, whereas this YAML tab allows you to only reload one specific configuration at a time.
 
 ### Reloading the YAML configuration
 

source/_includes/common-tasks/beta_version.md

@@ -10,7 +10,7 @@ If you would like to test next release before anyone else, you can install the b
   content: |
 
     1. In Home Assistant, go to {% my updates title="**System** > **Updates**" %}.
-    2. In the top-right corner, select the three-dots menu.
+    2. In the top-right corner, select the three dots {% icon "mdi:dots-vertical" %} menu.
     3. Select **Join beta**.
     4. Go to the {% my configuration title="**Configuration**" %} panel.
     5. Install the update that is presented to you.

source/_includes/integrations/remove_device_service_steps.md

@@ -1,3 +1,3 @@
 1. Go to {% my integrations title="**Settings** > **Devices & services**" %} and select the integration card.
 2. From the list of devices, select the integration instance you want to remove.
-3. Next to the entry, select the three-dot {% icon "mdi:dots-vertical" %} menu. Then, select **Delete**.
+3. Next to the entry, select the three dots {% icon "mdi:dots-vertical" %} menu. Then, select **Delete**.

source/_integrations/application_credentials.markdown

@@ -49,6 +49,6 @@ To delete an application credential, for example because you created a new one,
     ![Devices and services overflow menu](/images/integrations/application_credentials/devices-and-services-menu.png)
 
 2. In the top right corner, select the three dots {% icon "mdi:dots-vertical" %} menu and select **Application credentials**.
-3. Select the credential from the list, select the three-dots menu and select **Delete**.
+3. Select the credential from the list, select the three dots {% icon "mdi:dots-vertical" %} menu and select **Delete**.
 
     ![Application credential list](/images/integrations/application_credentials/application-credential_delete.png)

source/_integrations/dlna_dms.markdown

@@ -19,7 +19,7 @@ The DLNA Digital Media Server integration allows you to browse and play media fr
 
 ## Renaming
 
-The name/title of the DMS device is the same as the title of the config entry. It can be changed on the Integrations Configuration page from the three-dot menu.
+The name/title of the DMS device is the same as the title of the config entry. It can be changed on the Integrations Configuration page from the three dots {% icon "mdi:dots-vertical" %} menu.
 
 ## Media source URIs
 

source/_integrations/heos.markdown

@@ -70,7 +70,7 @@ Password:
 Once setup, the host name or IP address used to access the HEOS System can be changed by reconfiguring the integration.
 
 1. Go to **{% my integrations icon title="Settings > Devices & Services" %}**.
-2. Select **Denon HEOS**. Click the three-dot {% icon "mdi:dots-vertical" %} menu and then select **Reconfigure**.
+2. Select **Denon HEOS**. Click the three dots {% icon "mdi:dots-vertical" %} menu and then select **Reconfigure**.
 3. Enter a new [host name or IP address](/integrations/heos/#host).
 4. Click Submit to complete the reconfiguration.
 
@@ -79,7 +79,7 @@ Once setup, the host name or IP address used to access the HEOS System can be ch
 This integration follows standard integration removal. No extra steps are required.
 
 1. Go to **{% my integrations icon title="Settings > Devices & Services" %}**.
-2. Select **Denon HEOS**. Click the three-dot {% icon "mdi:dots-vertical" %} menu and then select **Delete**.
+2. Select **Denon HEOS**. Click the three dots {% icon "mdi:dots-vertical" %} menu and then select **Delete**.
 
 ## Actions
 

source/_integrations/homee.markdown

@@ -100,7 +100,7 @@ This integration supports reconfiguration, allowing you to change the IP address
 
 1. Go to {% my integrations title="**Settings** > **Devices & services**" %} and select the homee integration card.
 2. From the list of hubs, select the one you want to reconfigure.
-3. Next to the entry, select the three-dot {% icon "mdi:dots-vertical" %} menu. Then, select **Reconfigure**.
+3. Next to the entry, select the three dots {% icon "mdi:dots-vertical" %} menu. Then, select **Reconfigure**.
 
 ## Removing the integration
 

source/_integrations/matter.markdown

@@ -313,11 +313,11 @@ Follow these steps if you want to remove a device from a particular Matter contr
 
 1. Go to {% my integrations title="**Settings** > **Devices & services**" %} and on the **Matter** integration card, select **Devices**.
 2. From the list of devices, select the device you want to remove from a controller.
-3. In the **Device info** section, next to **Share device**, select the three-dot menu. Then, select **Manage fabrics**.
+3. In the **Device info** section, next to **Share device**, select the three dots {% icon "mdi:dots-vertical" %} menu. Then, select **Manage fabrics**.
 4. From the list, remove the controller of interest.
    - If you want to remove Apple Home, also remove the Apple Keychain entry.
    ![image](/images/integrations/matter/matter-remove-from-network.png)
-5. If you want to remove the device from Home Assistant itself, select the three-dot menu and select **Delete**.
+5. If you want to remove the device from Home Assistant itself, select the three dots {% icon "mdi:dots-vertical" %} menu and select **Delete**.
 
 ## About Matter device information
 

source/_integrations/monzo.markdown

@@ -41,9 +41,9 @@ The **Monzo** {% term integration %} allows you to connect your Monzo bank accou
 ### Adding a second account
 
 1. To add a second Monzo account in Home Assistant, repeat the above process for creating an OAuth client.
-2. Then, in Home Assistant, add the new credentials *before* trying to add the new entry. 
-   - In the top right of **Devices & services** page, select the three dot menu, open **Application Credentials**, and select **Add application credentials**
-   - It is recommended to include the person's name in the *Name* field so you can distinguish it later. 
+2. Then, in Home Assistant, add the new credentials *before* trying to add the new entry.
+   - In the top right of **Devices & services** page, select the three dots {% icon "mdi:dots-vertical" %} menu, open **Application Credentials**, and select **Add application credentials**
+   - It is recommended to include the person's name in the *Name* field so you can distinguish it later.
 3. Once added, you can return to **Devices & services** > **Monzo** > **Add Entry** to proceed with authentication.
 
 ## Sensor

source/_integrations/ntfy.markdown

@@ -44,7 +44,7 @@ The ntfy integration can be used to send push notifications from automations and
 
 3. **Adding a topic**
 
-    To set up topics for notifications, select the three-dot {% icon "mdi:dots-vertical" %} menu next to the entry of the previously configured ntfy service, then click **{% icon "mdi:plus" %} Add topic**.
+    To set up topics for notifications, select the three dots {% icon "mdi:dots-vertical" %} menu next to the entry of the previously configured ntfy service, then click **{% icon "mdi:plus" %} Add topic**.
 
     You can now choose one of the following options:
 

source/_integrations/onkyo.markdown

@@ -32,7 +32,7 @@ Listening modes:
   description: List of listening modes supported by the receiver.
 {% endconfiguration_basic %}
 
-The above settings can also be adjusted later. To change **Host** or **Volume Resolution**, select the three-dot menu on the integration entry and select **Reconfigure**.
+The above settings can also be adjusted later. To change **Host** or **Volume Resolution**, select the three dots {% icon "mdi:dots-vertical" %} menu on the integration entry and select **Reconfigure**.
 
 {% include integrations/option_flow.md %}
 

source/_integrations/reolink.markdown

@@ -529,7 +529,7 @@ Removing a camera from a NVR/Home Hub can be done by deleting the device followi
 3. Go to {% my integrations title="**Settings** > **Devices & services**" %} and select the integration card.
 4. From the list of integration entries, select the **x devices** underneath the integration instance of the NVR/Home Hub from which you want to remove a camera.
 5. Select the camera you want to remove from the list of devices
-6. Underneath the **Device info**, select the three-dot {% icon "mdi:dots-vertical" %} menu. Then, select **Delete**.
+6. Underneath the **Device info**, select the three dots {% icon "mdi:dots-vertical" %} menu. Then, select **Delete**.
 
 ### Removing a chime
 
@@ -538,7 +538,7 @@ Removing a chime from a doorbell can be done by deleting the chime following the
 1. Go to {% my integrations title="**Settings** > **Devices & services**" %} and select the integration card.
 2. From the list of integration entries, select the **x devices** underneath the integration instance of the Doorbell/NVR/Home Hub from which you want to remove a chime.
 3. Select the chime you want to remove from the list of devices
-4. Underneath the **Device info**, select the three-dot {% icon "mdi:dots-vertical" %} menu. Then, select **Delete**.
+4. Underneath the **Device info**, select the three dots {% icon "mdi:dots-vertical" %} menu. Then, select **Delete**.
 
 This will also decouple the chime from the doorbell in the Reolink app/client. Therefore, the chime will no longer ring when the doorbell is pressed.
 

source/_integrations/telegram_bot.markdown

@@ -107,7 +107,7 @@ To allowlist the chat ID, [retrieve the chat ID](/integrations/telegram#methods-
 
 1. Go to **{% my integrations title="Settings > Devices & services" %}**.
 2. Select the Telegram bot integration.
-3. Next to the entry, select the three-dot {% icon "mdi:dots-vertical" %} menu. Then, select **Add allowed chat ID**.
+3. Next to the entry, select the three dots {% icon "mdi:dots-vertical" %} menu. Then, select **Add allowed chat ID**.
 
 {% configuration_basic %}
 Chat ID:

source/_integrations/xiaomi_ble.markdown

@@ -58,7 +58,7 @@ Flower Care firmware update steps:
 - Press the "+" button on the top right in the devices tab of the app
 - Add the plant sensor to the app and select an arbitrary plant
 - Wait for the synchronization of the sensor to finish, and a dialog asking for a firmware update should appear (this might take a few minutes)
-- The installed and latest firmware version can be verified by selecting the plant -> three-dot menu -> Hardware settings -> Hardware update
+- The installed and latest firmware version can be verified by selecting the plant -> three dots menu -> Hardware settings -> Hardware update
 - The Flower Care account and app are not required any further for this integration to work
 
 Also note that the battery level of the plant sensor can only be retrieved by connecting to the device (reading characteristics), while the other sensor data is broadcasted passively. To prevent battery drainage, a connection is made only once a day. Connecting to the device also requires that the device has a good signal strength.

source/_integrations/zha.markdown

@@ -558,7 +558,7 @@ Prerequisites and steps can vary depending on the device type, manufacturer, and
 {% endnote %}
 
 1. Navigate to the Zigbee device's configuration page,
-2. In the options menu (the "three-dots" icon), select **Manage Zigbee device**,
+2. In the options menu (the "three dots" icon), select **Manage Zigbee device**,
 3. Select the **Bindings** tab in the pop-up dialog,
 4. Choose the device from the dropdown list of _Bindable devices_ (or _Bindable groups_),
 5. Confirm the Bind or Unbind action:

source/_integrations/zwave_js.markdown

@@ -1082,7 +1082,7 @@ Many users have reported issues with interference when the adapter was directly
 ##### Enable Z-Wave JS logging
 
 1. Go to the Z-Wave integration panel: {% my integration badge domain="zwave_js" %}
-2. In the top-right corner, select the three-dot {% icon "mdi:dots-vertical" %} menu and select **Enable debug logging**.
+2. In the top-right corner, select the three dots {% icon "mdi:dots-vertical" %} menu and select **Enable debug logging**.
    - **Result**: The log level will be set to `debug` for the integration, library, and optionally the driver (if the driver log level is not already set to `verbose`, `debug`, or `silly`), and all Z-Wave JS logs will be added to the Home Assistant logs.
 3. If you want to change the log level, on the Z-Wave integration panel: {% my integration badge domain="zwave_js" %}, select the cogwheel {% icon "mdi:cog-outline" %}.
    - Select the **Logs** tab, then select the log level.
@@ -1090,7 +1090,7 @@ Many users have reported issues with interference when the adapter was directly
 ##### Disable Z-Wave JS logging
 
 1. Go to the Z-Wave integration panel: {% my integration badge domain="zwave_js" %}
-2. In the top-right corner, select the three-dot {% icon "mdi:dots-vertical" %} menu and select **Disable debug logging**.
+2. In the top-right corner, select the three dots {% icon "mdi:dots-vertical" %} menu and select **Disable debug logging**.
    - **Result**: The log level will be reset to its previous value for the integration, library, and driver, and the Home Assistant frontend will automatically send you the Z-Wave logs generated during that time period for download.
 
 #### The advanced way
@@ -1198,7 +1198,7 @@ This removes all paired Z-Wave devices and their entities, the Z-Wave JS add-on,
      - This usually involves finding the device in your household and pressing a button.
 2. Remove the Z-Wave integration.
    - Go to {% my integrations title="**Settings** > **Devices & services**" %} and select the integration card.
-   - Next to the integration entry, select the three-dot {% icon "mdi:dots-vertical" %} menu.
+   - Next to the integration entry, select the three dots {% icon "mdi:dots-vertical" %} menu.
    - Select **Delete**.
 3. If it hasn't been deleted automatically, remove the Z-Wave JS add-on.
    - Go to {% my supervisor_addon addon="core_zwave_js" title="**Settings** > **Add-ons** > **Z-Wave JS**" %}.

source/getting-started/onboarding_dashboard.markdown

@@ -122,7 +122,7 @@ In the following steps, we will create a new dashboard and edit some card settin
 12. Now let's delete the other weather card.
     - In the top right corner, select the pencil.
     ![Dashboard - edit the dashboard](/images/getting-started/onboarding_edit_dashboard_01.png)
-    - On the card, select the three-dot menu and select **Delete**.
+    - On the card, select the three dots {% icon "mdi:dots-vertical" %} menu and select **Delete**.
     ![Dashboard - delete card](/images/getting-started/onboarding_dashboard_delete_card.png)
 13. Finally, we want to move the weather card to the top left corner.
     - On the bottom of the card, select the number or use the minus button to enter `1`.

source/voice_control/aliases.markdown

@@ -33,12 +33,12 @@ There are multliple ways to add an alias of an entity:
 ## Adding an alias of a floor
 
 1. To add an alias for a floor, go to **Settings** > **Areas, labels & zones**.
-2. Next to the floor of interest, select the three-dot menu, then select **Edit floor**.
+2. Next to the floor of interest, select the three dots {% icon "mdi:dots-vertical" %}, then select **Edit floor**.
 3. Select **Add alias** and enter the alias you want to use for that floor.
 4. **Save** your changes.
 
 
-### Area-less aliases for entities with an assigned area 
+### Area-less aliases for entities with an assigned area
 
 It’s good practice to add areas to entity canonical names, such as Living room lamp. However, since Assist can both infer the area and explicitly extract it from sentences, it’s a very good idea to add simplified aliases to all your exposed entities. In this case, having the Lamp alias set for the Living room lamp would allow you to turn on the lamp in the living room or simply turn on the lamp, when asking a satellite in the living room.