mirror of
https://github.com/home-assistant/developers.home-assistant.git
synced 2025-07-16 05:46:30 +00:00
Spelling and grammar fixes
This commit is contained in:
parent
d7109b2e78
commit
3336b07f87
@ -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.
|
||||
|
||||
|
@ -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)).
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user