Spelling and Markdown fixes: Part 4

source/_docs/autostart/init.d.markdown

@@ -6,31 +6,31 @@ redirect_from: /getting-started/autostart-init.d/
 
 Home Assistant can run as a daemon within init.d with the script below.
 
-### 1. Copy script
+## 1. Copy script
 
 Copy either the daemon script or the Python environment script at the end of this page to `/etc/init.d/hass-daemon` depending on your installation.
 
 After that, set the script to be executable:
 
 ```bash
-$ sudo chmod +x /etc/init.d/hass-daemon
+sudo chmod +x /etc/init.d/hass-daemon
 ```
 
-### 2. Select a user.
+## 2. Select a user
 
-Create or pick a user that the Home Assistant daemon will run under. Update script to set `RUN_AS` to the username that should be used to execute hass.
+Create or pick a user that the Home Assistant daemon will run under. Update script to set `RUN_AS` to the username that should be used to execute Home Assistant.
 
-### 3. Change hass executable and other variables if required.
+## 3. Change `hass` executable and other variables if required
 
 Some installation environments may require a change in the Home Assistant executable `hass`. Update script to set `HASS_BIN` to the appropriate `hass` executable path. Please also check the other variables for the appropriate value. In general the defaults should work
 
-### 4. Install this service
+## 4. Install this service
 
 ```bash
-$ sudo service hass-daemon install
+sudo service hass-daemon install
 ```
 
-### 5. Create logrotate rule
+## 5. Create logrotate rule
 
 This logrotate script at `/etc/logrotate.d/homeassistant` will create an outage of a few seconds every week at night. If you do not want this add `--log-rotate-days 7` to the `FLAGS` variable in the init script.
 
@@ -55,11 +55,11 @@ File `/var/log/homeassistant/home-assistant.log`:
 
 That's it. Restart your machine and Home Assistant should start automatically.
 
-If HA does not start, check the log file output for errors at `/var/log/homeassistant/home-assistant.log`
+If Home Assistant does not start, check the log file output for errors at `/var/log/homeassistant/home-assistant.log`
 
-### Extra: Running commands before hass executes
+### Extra: Running commands before Home Assistant executes
 
-If any commands need to run before executing hass (like loading a virtual environment), put them in PRE_EXEC. This command must end with a semicolon.
+If any commands need to run before executing Home Assistant (like loading a virtual environment), put them in PRE_EXEC. This command must end with a semicolon.
 
 ### Daemon script
 

source/_docs/backend/updater.markdown

@@ -6,7 +6,7 @@ redirect_from: /details/updater/
 
 Starting with 0.31 the [updater component](/integrations/updater/) sends an optional report about Home Assistant instance.
 
-If you want to opt-in to include integration information, add `include_used_components` to your config. This will allow the Home Assistant developers to focus development efforts on the most popular components.
+If you want to opt-in to include integration information, add `include_used_components` to your configuration. This will allow the Home Assistant developers to focus development efforts on the most popular components.
 
 ```yaml
 updater:
@@ -16,7 +16,7 @@ updater:
 We are only collecting this information to better understand our user base to provide better long term support and feature development.
 
 | Name                  | Description                                | Example                            | Data Source    |
-|-----------------------|--------------------------------------------|------------------------------------|----------------|
+| --------------------- | ------------------------------------------ | ---------------------------------- | -------------- |
 | `arch`                | CPU Architecture                           | `x86_64`                           | Local Instance |
 | `distribution`        | Linux Distribution name (only Linux)       | `Ubuntu`                           | Local Instance |
 | `docker`              | True if running inside Docker              | `false`                            | Local Instance |

source/_docs/configuration.markdown

@@ -9,19 +9,19 @@ The web interface can be found at `http://ip.ad.dre.ss:8123/` - for example if y
 
 The location of the folder differs between operating systems:
 
-| OS | Path |
-| -- | ---- |
-| macOS | `~/.homeassistant` |
-| Linux | `~/.homeassistant` |
+| OS      | Path                       |
+| ------- | -------------------------- |
+| macOS   | `~/.homeassistant`         |
+| Linux   | `~/.homeassistant`         |
 | Windows | `%APPDATA%/.homeassistant` |
-| Hass.io | `/config` |
-| Docker | `/config` |
+| Hass.io | `/config`                  |
+| Docker  | `/config`                  |
 
-If you want to use a different folder for configuration, use the config command line parameter: `hass --config path/to/config`.
+If you want to use a different folder for configuration, use the configuration command line parameter: `hass --config path/to/config`.
 
 Inside your configuration folder is the file `configuration.yaml`. This is the main file that contains integrations to be loaded with their configurations. Throughout the documentation you will find snippets that you can add to your configuration file to enable functionality.
 
-If you run into trouble while configuring Home Assistant, have a look at the [configuration troubleshooting page](/getting-started/troubleshooting-configuration/) and at the [configuration.yaml examples](/cookbook/#example-configurationyaml).
+If you run into trouble while configuring Home Assistant, have a look at the [configuration troubleshooting page](/getting-started/troubleshooting-configuration/) and at the [`configuration.yaml` examples](/cookbook/#example-configurationyaml).
 
 <div class='note tip'>