Skip to content

Commit 81ad15e

Browse files
JudgeDreddKLCfabaff
authored andcommitted
minor grammar changes to improve readability (home-assistant#5092)
minor grammar changes to improve readability
1 parent d42f6df commit 81ad15e

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

source/_docs/configuration/packages.markdown

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,9 @@ footer: true
1010
redirect_from: /topics/packages/
1111
---
1212

13-
Packages in Home Assistant provides a way to bundle different component's configuration together. We were already introduced to the two configuration styles (specifying platforms entries together or individually) on the [adding devices](/docs/configuration/devices/) page. Both of these configuration methods require you to create the component key in the main `configuration.yaml` file. With packages we have a way to include different components, or parts of configuration using any of the `!include` directives introduced in [splitting the configuration](/docs/configuration/splitting_configuration).
13+
Packages in Home Assistant provides a way to bundle different component's configuration together. We already learned about the two configuration styles (specifying platforms entries together or individually) on the [adding devices](/docs/configuration/devices/) page. Both of these configuration methods require you to create the component key in the main `configuration.yaml` file. With packages we have a way to include different components, or different configuration parts using any of the `!include` directives introduced in [splitting the configuration](/docs/configuration/splitting_configuration).
1414

15-
Packages are configured under the core `homeassistant/packages` in the configuration and take the format of a packages name (no spaces, all lower case) followed by a dictionary with the package config. For example, package `pack_1` would be created as:
15+
Packages are configured under the core `homeassistant/packages` in the configuration and take the format of a package name (no spaces, all lower case) followed by a dictionary with the package config. For example, package `pack_1` would be created as:
1616

1717
```yaml
1818
homeassistant:
@@ -22,7 +22,7 @@ homeassistant:
2222
...package configuration here...
2323
```
2424
25-
The package configuration can include: `switch`, `light`, `automation`, `groups` or the majority of the Home Assistant components.
25+
The package configuration can include: `switch`, `light`, `automation`, `groups`, or most other Home Assistant components.
2626

2727
It can be specified inline or in a separate YAML file using `!include`.
2828

@@ -81,7 +81,7 @@ Components inside packages can only specify platform entries using configuration
8181

8282
### {% linkable_title Create a packages folder %}
8383

84-
One way to organize packages would be to create a folder named "packages" in your Home Assistant configuration directory. In the packages directory you can store any number of packages in a YAML file. This entry in your `configuration.yaml` will load all packages:
84+
One way to organize packages is to create a folder named "packages" in your Home Assistant configuration directory. In the packages directory you can store any number of packages in a YAML file. This entry in your `configuration.yaml` will load all packages:
8585

8686
```yaml
8787
homeassistant:

0 commit comments

Comments
 (0)