diff --git a/docs/hassio_hass.md b/docs/hassio_hass.md
index 6644fce5..c9d8b326 100644
--- a/docs/hassio_hass.md
+++ b/docs/hassio_hass.md
@@ -14,16 +14,16 @@ To develop for the frontend, we're going to need API access to the supervisor.
 - Add our developer Add-on repository: https://github.com/home-assistant/hassio-addons-development
 - Install the Add-on "Remote API proxy"
 
-For some API commands you need explicit the Home Assistant API token, but 99% of the functionality work with `Remote API proxy`. This token change some times but you can read the current legal token on host system with:
+For some API commands you need explicit the Home Assistant API token, but 99% of the functionality work with `Remote API proxy`. This token change sometimes but you can read the current legal token on host system with:
 ```sh
 $ docker inspect homeassistant | grep HASSIO_TOKEN
 ```
 
  ## Having Home Assistant connect to remote Hass.io
 
- The connection with the supervisor is hidden inside the host and is only accessible from applications running on the host. So to make it accessible for our Home Assistant instance, we will need to route the connection to our computer running Home Assistant. We're going to do this by forwarding the API with "Remote API proxy" Add-on.
+ The connection with the supervisor is hidden inside the host and is only accessible from applications running on the host. So to make it accessible for our Home Assistant instance we will need to route the connection to our computer running Home Assistant. We're going to do this by forwarding the API with "Remote API proxy" add-on.
 
-First, make sure Home Assistant will load the Hass.io component by adding `hassio:` to your `configuration.yaml` file. Next, we will need to tell Hass.io component how to connect to the remote Hass.io instance, we do this by setting the `HASSIO` and `HASSIO_TOKEN` environment variables when starting Home Assistant. Note that the `HASSIO` value is not the same as the one that we saw above and the `HASSIO_TOKEN` is available inside log output of "Remote API Add-on" (This change every restart of this Add-on!).
+First, make sure Home Assistant will load the Hass.io component by adding `hassio:` to your `configuration.yaml` file. Next, we will need to tell the local Home Assistant instance how to connect to the remote Hass.io instance. We do this by setting the `HASSIO` and `HASSIO_TOKEN` environment variables when starting Home Assistant. Note that the `HASSIO` value is not the same as the one that we saw above and the `HASSIO_TOKEN` is available inside log output of "Remote API Add-on" (This changes every restart of the add-on!).
 
 ```bash
 HASSIO=<IP OF HASS.IO>:80 HASSIO_TOKEN=<VALUE OF HASSIO_TOKEN> hass
@@ -49,9 +49,9 @@ To build a local version of the Hass.io panel, go to the frontend repository and
 
 ```bash
 cd hassio
-script/build_hassio
+script/develop
 ```
 
 Now start Home Assistant as discussed in the previous section and it will now connect to the remote Hass.io but show your local frontend.
 
-We're currently transitioning in how we're building the frontend so we don't have an incremental development mode just yet. For now, after making a local change, run `script/build_hassio` again.
+Once you have `script/develop` the hassio panel will be rebuilt whenever you make changes to the source files.