Merge branch 'current' into next

.github/workflows/test.yml

@@ -10,7 +10,7 @@ jobs:
       - name: Check out files from GitHub
         uses: actions/checkout@v2
       - name: Setting up Node.js ${{ matrix.node-version }}
-        uses: actions/setup-node@v2.1.4
+        uses: actions/setup-node@v2.1.5
         with:
           node-version: 12.x
       - name: Setup NPM cache
@@ -33,7 +33,7 @@ jobs:
       - name: Check out files from GitHub
         uses: actions/checkout@v2
       - name: Setting up Node.js ${{ matrix.node-version }}
-        uses: actions/setup-node@v2.1.4
+        uses: actions/setup-node@v2.1.5
         with:
           node-version: 12.x
       - name: Setup NPM cache

source/_includes/common-tasks/development_version.md

@@ -51,7 +51,7 @@ ha os update --version {{current_version}}
 3. Download and install the version you want
 
     ```bash
-    pip3 install --upgrade git+git://github.com/home-assistant/home-assistant.git@dev
+    pip3 install --upgrade git+git://github.com/home-assistant/core.git@dev
     ```
 
 4. When that is complete restart the service for it to use the new files.

source/_integrations/knx.markdown

@@ -92,7 +92,7 @@ config_file:
   required: false
   type: string
 individual_address:
-  description: The KNX individual address (IA) that shall be used for routing or if a tunnelling server doesn't assign an IA at connection.
+  description: The KNX individual address (IA) that shall be used for routing or if a tunneling server doesn't assign an IA at connection.
   required: false
   type: string
   default: "15.15.250"
@@ -124,7 +124,7 @@ Under normal conditions no connection configuration should be needed. The integr
 
 ### Tunneling
 
-If you want to connect to a sepcific tunnelling server or if the auto detection of the KNX/IP device does not work the IP or/and port of the tunneling device can be configurated.
+If you want to connect to a specific tunneling server or if the auto detection of the KNX/IP device does not work the IP or/and port of the tunneling device can be configurated.
 
 ```yaml
 knx:
@@ -180,10 +180,10 @@ event_filter:
 
 Every telegram that matches the filter with its destination field will be announced on the event bus as a `knx_event` event containing data attributes
 
-- `data` contains the raw payload data (eg. 1 or "[12, 55]").
-- `destination` the KNX group address the telegram is sent to as string (eg. "1/2/3).
+- `data` contains the raw payload data (e.g., 1 or "[12, 55]").
+- `destination` the KNX group address the telegram is sent to as string (e.g., "1/2/3).
 - `direction` the direction of the telegram as string ("Incoming" / "Outgoing").
-- `source` the KNX indidividual address of the sender as string (eg. "1.2.3").
+- `source` the KNX individual address of the sender as string (e.g., "1.2.3").
 - `telegramtype` the APCI service of the telegram. "GroupValueWrite", "GroupValueRead" or "GroupValueResponse" generate a knx_event.
 
 ## Services
@@ -333,12 +333,12 @@ entity_id:
   required: false
 attribute:
   description: Attribute of the entity that shall be sent to the KNX bus. If not set (or `None`) the state will be sent.
-    Eg. for a light the state is eigther "on" or "off". With `attribute` you can expose its "brightness".
+    For example for a light the state is either "on" or "off". With `attribute` you can expose its "brightness".
   type: string
   required: false
 default:
   description: Default value to send to the bus if the state or attribute value is `None`.
-    Eg. a light with state "off" has no brightness attribute so a default value of `0` could be used.
+    For example a light with state "off" has no brightness attribute so a default value of `0` could be used.
     If not set (or `None`) no value would be sent to the bus and a GroupReadRequest to the address would return the last known value.
   type: [boolean, string, integer, float]
   default: None
@@ -442,7 +442,7 @@ name:
   required: false
   type: string
 counter:
-  description: Set to 2 if your only want the action to be executed if the button was pressed twice. To 3 for three times button pressed.
+  description: Set to 2 if you only want the action to be executed if the button was pressed twice. Set to 3 for three times button pressed.
   required: false
   type: integer
   default: 1
@@ -720,7 +720,7 @@ move_long_address:
   required: false
   type: string
 move_short_address:
-  description: KNX group address for moving the cover short time up or down. *DPT 1*
+  description: KNX group address for moving the cover short time up or down. Used by some covers also as the means to stop the cover, if no dedicated `stop_address` exists on the actuator. *DPT 1*
   required: false
   type: string
 stop_address:
@@ -754,7 +754,7 @@ travelling_time_up:
   default: 25
   type: integer
 invert_position:
-  description: Set this to `true` if your actuator report fully closed as 0% in KNX.
+  description: Set this to `true` if your actuator reports fully closed as 0% in KNX.
   required: false
   default: false
   type: boolean

source/_integrations/spotify.markdown

@@ -83,7 +83,7 @@ modification to the `configuration.yaml` file is needed. Multiple Spotify
 accounts can be linked to a _single_ Spotify application.
 
 To add an additional Spotify account to Home Assistant, go to the Spotify website and log out, then repeat _only_ the steps
-in the [Activating the Spotify integration](#activating-the-spotify-integration) section. 
+in the [Configuration](#configuration) section. 
 
 ## Playing Spotify playlists