-It's time for Home Assistant 0.97! This has been a very busy release cycle as we have been fine tuning development. This will make it easier to maintain and contribute to Home Assistant in the future.
+It's time for Home Assistant 0.97! It has been a very busy release cycle as we have been fine-tuning our development process, which makes it easier to maintain and contribute to Home Assistant in the future.
## Python 3.5 support has been dropped
@@ -21,40 +21,44 @@ As per previous announcements, this is the first release that requires at least
## Docker
-This is the latest release for which our Docker image `homeassistant/home-assistant` is based on Debian. As decided in [ADR006 Docker Images](https://github.com/home-assistant/architecture/blob/master/adr/0006-docker-images.md), the image will now be based on Alpine Linux starting with the next release. This will be the same Home Assistant image that powers Hass.io. You don't need to change anything unless you were installing Debian packages or making any other changes to the running container. In that case you'll need to find the Alpine equivalent of whatever you were doing.
+This is the last release that bases our Home Assistant Docker image (`homeassistant/home-assistant`) on Debian. As decided in [Architecture Decision Record 0006: Docker Images](https://github.com/home-assistant/architecture/blob/master/adr/0006-docker-images.md), the image will be based on Alpine Linux starting with the 0.98 release. These new Docker images will be running same the Home Assistant Docker image that powers Hass.io. You don't need to change anything unless you have installed Debian packages manually or made any other changes to the running container. However, if that is the case, you'll need to find the Alpine equivalent of whatever you were doing.
-The main driver behind this change is that by re-using images, maintenance will be easier and users of the `homeassistant/home-assistant` image can benefit of the many optimizations that went into the hass.io images.
+The main driver behind this change is that by re-using images, maintenance becomes easier, and users of the `homeassistant/home-assistant` image can benefit from the many optimizations that went into the Hass.io images.
-## Reload scenes from configuration.yaml
+## Reload scenes from `configuration.yaml`
-Thanks to [@balloob] it is now possible to reload scenes from configuration.yaml without restarting Home Assistant. This is part of an effort for Home Assistant 1.0 to make scenes a first class citizen of Home Assistant, including creating/restoring scenes on the fly in the future. To track this effort, [follow this page](https://github.com/home-assistant/home-assistant/issues/25681).
+Thanks to [@balloob] it is now possible to reload scenes from `configuration.yaml` without restarting Home Assistant. This is part of an effort for Home Assistant 1.0 to make scenes a first-class citizen of Home Assistant, including creating/restoring scenes on the fly in the future. To track this effort, [follow this page](https://github.com/home-assistant/home-assistant/issues/25681).
## Home Assistant Cast
-In case you missed the announcement, we released Home Assistant Cast yesterday. It allows you to transform any Cast interface into a display for Home Assistant. [Read the announcement for more information.](/blog/2019/08/06/home-assistant-cast/)
+In case you missed the announcement, we released Home Assistant Cast yesterday. It allows you to transform any Cast interface into a display for Home Assistant. [Read the announcement for more information.](/blog/2019/08/06/home-assistant-cast/).
