Username: streamline spelling (#32973)

source/_docs/configuration/basic.markdown

@@ -22,7 +22,7 @@ To change the general settings that were defined during onboarding, follow these
 1. Go to {% my general title="**Settings** > **System** > **General**" %} and make your changes.
 2. To change network-related configuration, such as the network name, go to {% my network title="**Settings** > **System** > **Network**" %}.
 3. If some of the settings are not visible, you may need to enable **Advanced mode**.
-   - In the bottom left, select your user name to go to your {% my profile title="**User profile**" %}, and enable **Advanced mode**.
+   - In the bottom left, select your username to go to your {% my profile title="**User profile**" %}, and enable **Advanced mode**.
 4. **Troubleshooting**: If any of the settings are grayed out and can't be edited, this is because they are defined in the {% term "`configuration.yaml`" %} file.
    - If you prefer editing the settings in the UI, you have to delete these entries from the {% term "`configuration.yaml`" %} file.
    - For more information about the general settings in YAML, refer to the [Home Assistant Core integration documentation](/integrations/homeassistant/).

source/_docs/locked_out.md

@@ -3,7 +3,7 @@ title: "I'm locked out!"
 description: "Options for regaining access"
 related:
   - docs: /common-tasks/os/#listing-all-users-from-the-command-line
-    title: Listing all user names via command line
+    title: Listing all usernames via command line
   - url: https://yellow.home-assistant.io/guides/factory-reset/
     title: Reset the Yellow
   - url: https://green.home-assistant.io/guides/reset/
@@ -13,7 +13,7 @@ related:
 The sections below deal with recovering from a situation where you are not able to sign in,
 or need to recover your data.
 
-## Forgot user name
+## Forgot username
 
 If you’ve forgotten your username, ask the owner to help you.
 If you are using the {% term "Home Assistant Operating System" %} and have access to the Home Assistant server, you can connect a terminal and enter the `auth list` command. This command lists all users that are registered on your Home Assistant.

source/_includes/common-tasks/file_access.md

@@ -25,7 +25,7 @@ To install the add-on, follow these steps:
 2. On the **Configuration** tab, define **Username** and **Password**, store them in a safe place, and save your changes.
    - You can specify any username and password.
    - They are not related to the login credentials you use to log in to Home Assistant or to log in to the computer from which you are accessing the files.
-   - The add-on won't start if user name and password are not defined.
+   - The add-on won't start if username and password are not defined.
 3. For further configuration information, refer to the **Documentation** tab.
 4. To start the add-on, on the **Information** tab, select **Start**.
 

source/_integrations/decora_wifi.markdown

@@ -36,7 +36,7 @@ light:
 
 {% configuration %}
 username:
-  description: Your "My Leviton" app email address/user name.
+  description: Your "My Leviton" app email address/username.
   required: true
   type: string
 password:

source/_integrations/discord.markdown

@@ -158,7 +158,7 @@ Note that `verify_ssl` defaults to `True`, and that any remote hosts will need t
 
 ## Notes
 
-You can tag any user inside a channel by using their user ID in the message like so: `<@userid>` replacing `userid` with the ID you copied. To get the user ID right click on the user name to copy the ID like you did for the channel ID up above.
+You can tag any user inside a channel by using their user ID in the message like so: `<@userid>` replacing `userid` with the ID you copied. To get the user ID right click on the username to copy the ID like you did for the channel ID up above.
 
 For more information about creating and authorizing bots, visit the [OAuth2 information page](https://discordapp.com/developers/docs/topics/oauth2)
 

source/_integrations/egardia.markdown

@@ -106,7 +106,7 @@ There seem to be multiple versions of software running on GATE-02 devices; we ha
 ## Advanced configuration
 
 1. Log in to your alarm system's control panel. You will need to access http://[IP of your control panel]. You know this already since you need it in the basic configuration from above. Log in to the control panel with your Egardia/Woonveilig username and password.
-2. Once logged in, go to *System Settings*, *Report* and change the Server Address for your primary server to the IP or hostname of your Home Assistant machine. You can leave the port number set to 52010 or change it to anything you like. **Make sure to change the settings of the primary server otherwise the messages will not come through. Note that this will limit (or fully stop) the number of alarm messages you will get through Egardia's / Woonveilig services.** Maybe, that is just what you want. Make sure to save your settings by selecting 'OK'. **If the system support XMPP, disable XMPP by invalidating the configuration in the XMPP menu (for example by changing the user name). This is required for recent firmwares of the GATE-03 system as it does not use the Reporting server at all in the case of a valid XMPP configuration.**
+2. Once logged in, go to *System Settings*, *Report* and change the Server Address for your primary server to the IP or hostname of your Home Assistant machine. You can leave the port number set to 52010 or change it to anything you like. **Make sure to change the settings of the primary server otherwise the messages will not come through. Note that this will limit (or fully stop) the number of alarm messages you will get through Egardia's / Woonveilig services.** Maybe, that is just what you want. Make sure to save your settings by selecting 'OK'. **If the system support XMPP, disable XMPP by invalidating the configuration in the XMPP menu (for example by changing the username). This is required for recent firmwares of the GATE-03 system as it does not use the Reporting server at all in the case of a valid XMPP configuration.**
 3. The Egardia integration relies on capturing the status codes that your alarm emits when something happens (status change or trigger). These codes will be unique for every situation - i.e., the code emitted by the alarm when a sensor is triggered is unique to that sensor. Also, if you have multiple users or remotes, each remote has unique codes that are emitted by the alarm when status is changed using that remote or by that user. For the Egardia integration to work correctly you will need to capture the codes. To do this, on your Home Assistant machine run `$ sudo python3 egardiaserver.py`. Refer to the [python-egardia repository](https://github.com/jeroenterheerdt/python-egardia) for detailed documentation on parameters. This will receive status codes from your alarm control panel and display them. Record the codes shown as well as the status they relate to (see step 4 below). Make sure to change the status of your alarm to all states (disarm, arm, home) by all means possible (all users, remotes, web login, app) as well as trigger the alarm in all ways possible to get 100% coverage of all the codes the alarm system generates. You will need to run this script once and stop it once you have captured all the possible codes. Also, if you ever add users, remotes or sensors to your alarm system, make sure to re-run the script to capture the extra codes so you can update your configuration (see step 4 below). **For comfort, before triggering the alarm it might be good to disable the siren temporarily (can be done in Panel Settings).**
 4. Once you have the codes, update your {% term "`configuration.yaml`" %}:
    ```yaml

source/_integrations/elkm1.markdown

@@ -77,7 +77,7 @@ version of the TLS protocol, the user must specify the TLS version to connect.
 
 ### Global Setting 35
 
-The ElkM1 integration tracks the user number and name of the last user name to
+The ElkM1 integration tracks the user number and name of the last username to
 arm or disarm the panel. The `changed_by` and `changed_by_id` attributes of
 the `alarm_control_panel` hold those two attributes.
 

source/_integrations/fritzbox_callmonitor.markdown

@@ -26,7 +26,7 @@ To use the FRITZ!Box call monitor in your installation, a user with at least `Vo
 3.  Navigate to **System** -> **FRITZ!Box User**.
 4.  Click the `Add User` button.
 5.  Enable the option `User account enabled`.
-6.  Enter a user name and password.
+6.  Enter a username and password.
 7.  Check the rights box next to `Voice messages, faxes, FRITZ!App Fon and call list`.
 8.  Click the `Apply` button.
 

source/_integrations/imap.markdown

@@ -120,7 +120,7 @@ The custom event data template is an advanced feature. The option is available o
 server:
   description: The IMAP server name
 username:
-  description: The IMAP user name
+  description: The IMAP username
 search:
   description: The IMAP search configuration
 folder:

source/_integrations/owntracks.markdown

@@ -71,7 +71,7 @@ waypoints:
   default: true
   type: boolean
 waypoint_whitelist:
-  description: "A list of user names (as defined for [OwnTracks](/integrations/owntracks)) who can export their waypoints from OwnTracks to Home Assistant. This would be the `username` portion of the Base Topic Name, (e.g., owntracks/username/iPhone)."
+  description: "A list of usernames (as defined for [OwnTracks](/integrations/owntracks)) who can export their waypoints from OwnTracks to Home Assistant. This would be the `username` portion of the Base Topic Name, (e.g., owntracks/username/iPhone)."
   required: false
   default: All users who are connected to Home Assistant via OwnTracks.
   type: list

source/_integrations/telegram.markdown

@@ -29,7 +29,7 @@ To create your first [Telegram bot](https://core.telegram.org/bots#how-do-i-crea
      - Store the token somewhere safe.
 2. To get a chat ID, send any message to the [GetIDs bot](https://t.me/getidsbot).
    - Then, enter `/start`. 
-   - The bot will return your chat ID and the user name.
+   - The bot will return your chat ID and the username.
 3. Create a [Telegram bot in Home Assistant](/integrations/telegram_bot):
    - Paste this into your [configuration file](/docs/configuration/):
    - Replace the `api_key` and the `allowed_chat_ids` with your data.

source/_integrations/wake_on_lan.markdown

@@ -119,7 +119,7 @@ from Home Assistant running on another Linux computer (the **server**).
 
 1. On the **server**, log in as the user account Home Assistant is running under. In this example it's `hass`.
 2. On the **server**, create SSH keys by running `ssh-keygen`. Just press enter on all questions.
-3. On the **target**, create a new account that Home Assistant can ssh into: `sudo adduser hass`. Just press enter on all questions except password. It's recommended using the same user name as on the server. If you do, you can leave out `hass@` in the SSH commands below.
+3. On the **target**, create a new account that Home Assistant can ssh into: `sudo adduser hass`. Just press enter on all questions except password. It's recommended using the same username as on the server. If you do, you can leave out `hass@` in the SSH commands below.
 4. On the **server**, transfer your public SSH key by `ssh-copy-id hass@TARGET` where TARGET is your target machine's name or IP address. Enter the password you created in step 3.
 5. On the **server**, verify that you can reach your target machine without password by `ssh TARGET`.
 6. On the **target**, we need to let the `hass` user execute the program needed to suspend/shut down the target computer. Here is it `pm-suspend`, use `poweroff` to turn off the computer. First, get the full path: `which pm-suspend`. On my system, this is `/usr/sbin/pm-suspend`.