diff --git a/source/_posts/2018-08-29-release-77.markdown b/source/_posts/2018-08-29-release-77.markdown
index fdaf74551a6..36e35235bf9 100644
--- a/source/_posts/2018-08-29-release-77.markdown
+++ b/source/_posts/2018-08-29-release-77.markdown
@@ -23,7 +23,7 @@ Once logged in, you will have access to the following new features:
  - Configure multifactor authentication (TOTP)
  - Manage other users (limited to account created during onboarding)
 
-Although it's possible to configure authentication, we stronlgy recommend to stick with the default authentication configuration.  If you had auth providers configured in a previous Home Assistant release, we recommend to remove the configuration and start using the default.
+Although it's possible to configure authentication, we strongly recommend to stick with the default authentication configuration.  If you had auth providers configured in a previous Home Assistant release, we recommend to remove the configuration and start using the default.
 
 It will take some time before all of the Home Assistant ecosystem has been migrated over to the new auth system. Home Assistant will print a warning whenever an application connects to Home Assistant with the legacy authentication. This will help users notify the application developers to transition to use the new [OAuth2](https://developers.home-assistant.io/docs/en/auth_api.html) authentication. For non-interactive scripts or other applications that are unable to update, we are planning to introduce a migration path for components to adopt url specific auth tokens and also introduce long lived access tokens to replace API passwords. A list of impacted components can be found [here](https://github.com/home-assistant/home-assistant/issues/15376#issuecomment-415890552).