diff --git a/docs/auth_permissions.md b/docs/auth_permissions.md index c8363901..e2e636d8 100644 --- a/docs/auth_permissions.md +++ b/docs/auth_permissions.md @@ -29,7 +29,7 @@ Each category can further split into subcategories that describe parts of that c } ``` -If a category is ommitted, the user will not have permission to that category. +If a category is omitted, the user will not have permission to that category. When defining a policy, any dictionary value at any place can be replaced with `True` or `None`. `True` means that permission is granted and `None` means use default, which is deny access. diff --git a/docs/config_entries_index.md b/docs/config_entries_index.md index e9252997..9da03d1c 100644 --- a/docs/config_entries_index.md +++ b/docs/config_entries_index.md @@ -7,7 +7,7 @@ Config Entries are configuration data that are persistently stored by Home Assis ## Setting up an entry -During startup, Home Assistant first call the [normal component setup](https://developers.home-assistant.io/docs/en/creating_component_index.html), +During startup, Home Assistant first calls the [normal component setup](https://developers.home-assistant.io/docs/en/creating_component_index.html), and then call the method `async_setup_entry(hass, entry)` for each entry. If a new Config Entry is created at runtime, Home Assistant will also call `async_setup_entry(hass, entry)` ([example](https://github.com/home-assistant/home-assistant/blob/0.68.0/homeassistant/components/hue/__init__.py#L119)).