From 905676ba691680a1d6555f8ad8f66c84ebc02081 Mon Sep 17 00:00:00 2001 From: DubhAd Date: Sat, 15 Sep 2018 13:32:40 +0100 Subject: [PATCH] Spelling/grammar tweaks --- source/_docs/authentication/providers.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_docs/authentication/providers.markdown b/source/_docs/authentication/providers.markdown index 6d3aa2360b0..de5e223b015 100644 --- a/source/_docs/authentication/providers.markdown +++ b/source/_docs/authentication/providers.markdown @@ -31,7 +31,7 @@ Home Assistant automatically configures the standard auth providers and you **do

-Legacy API password auth provider wouldn't be loaded if your API password located in separete package. This is because Home Assistant process `auth_provider` during the `core` section loading, it is earlier then do the `packages` processing. +The legacy API password auth provider won't be loaded if your API password is located in a package. This is because Home Assistant processes the `auth_provider` during the `core` section loading, which is earlier than the `packages` processing.

Authentication providers are configured in your `configuration.yaml` under the `homeassistant:` block: