Docs: apply sentence-style capitalization (#29891)

* Docs: apply sentence-style capitalization

* Update source/_docs/automation/trigger.markdown

* Apply suggestions from code review

Co-authored-by: Joakim Sørensen <joasoe@gmail.com>

---------

Co-authored-by: Joakim Sørensen <joasoe@gmail.com>
This commit is contained in:
c0ffeeca7 2023-11-18 11:29:00 +01:00 committed by GitHub
parent f9dae99569
commit 8a6fa5a803
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
6 changed files with 9 additions and 9 deletions

View File

@ -55,7 +55,7 @@ If you don't specify any `auth_providers` section in the `configuration.yaml` fi
### Trusted networks
The Trusted Networks auth provider defines a range of IP addresses for which no authentication will be required (also known as "allowlisting"). For example, you can allowlist your local network so you won't be prompted for a password if you access Home Assistant from inside your home.
The trusted networks auth provider defines a range of IP addresses for which no authentication will be required (also known as "allowlisting"). For example, you can allowlist your local network so you won't be prompted for a password if you access Home Assistant from inside your home.
When you log in from one of these networks, you will be asked which user account to use and won't need to enter a password.
@ -154,7 +154,7 @@ Assuming you have only the owner created though onboarding process, no other use
### Command line
The Command Line auth provider executes a configurable shell command to perform user authentication. Two environment variables, `username` and `password`, are passed to the command. Access is granted when the command exits successfully (with exit code 0).
The command line auth provider executes a configurable shell command to perform user authentication. Two environment variables, `username` and `password`, are passed to the command. Access is granted when the command exits successfully (with exit code 0).
This provider can be used to integrate Home Assistant with arbitrary external authentication services, from plaintext databases over LDAP to RADIUS. A compatible script for LDAP authentication is [this one](https://github.com/bob1de/ldap-auth-sh), for instance. Please note, this will only work when using the Home Assistant Core installation type.

View File

@ -80,7 +80,7 @@ These are the properties available for a [MQTT trigger](/docs/automation/trigger
### Numeric state
These are the properties available for a [Numeric State trigger](/docs/automation/trigger/#numeric-state-trigger).
These are the properties available for a [numeric state trigger](/docs/automation/trigger/#numeric-state-trigger).
| Template variable | Data |
| ---- | ---- |
@ -148,7 +148,7 @@ These are the properties available for a [Time trigger](/docs/automation/trigger
### Time pattern
These are the properties available for a [Time Pattern trigger](/docs/automation/trigger/#time-pattern-trigger).
These are the properties available for a [time pattern trigger](/docs/automation/trigger/#time-pattern-trigger).
| Template variable | Data |
| ---- | ---- |
@ -157,7 +157,7 @@ These are the properties available for a [Time Pattern trigger](/docs/automation
### Persistent notification
These properties are available for a [Persistent Notification trigger](/docs/automation/trigger/#persistent-notification-trigger).
These properties are available for a [persistent notification trigger](/docs/automation/trigger/#persistent-notification-trigger).
| Template variable | Data |
| ---- | ---- |

View File

@ -687,7 +687,7 @@ automation:
### Input datetime
The Entity ID of an [Input Datetime](/integrations/input_datetime/).
The entity ID of an [input datetime](/integrations/input_datetime/).
| has_date | has_time | Description |
| -------- | -------- | ---------------------------------------- |

View File

@ -264,7 +264,7 @@ If you want to migrate your manual automations to use the editor, you'll have to
### Deleting automations
When automations remain visible in the Home Assistant Dashboard, even after having deleted in the YAML file, you have to delete them in the UI.
When automations remain visible in the Home Assistant dashboard, even after having deleted in the YAML file, you have to delete them in the UI.
To delete them completely, go to UI **{% my entities title="Settings -> Devices & Services -> Entities" %}** and find the automation in the search field or by scrolling down.

View File

@ -15,7 +15,7 @@ Here's the summary of what you *must* do to secure your Home Assistant system:
## Remote access
If you want secure remote access, the easiest option is to use [Home Assistant cloud](/cloud/) by which you also [support](https://www.nabucasa.com/about/) the founders of Home Assistant.
If you want secure remote access, the easiest option is to use [Home Assistant Cloud](/cloud/) by which you also [support](https://www.nabucasa.com/about/) the founders of Home Assistant.
Another option is to use TLS/SSL via the add-on [Duck DNS](/integrations/duckdns/) integrating Let's Encrypt.

View File

@ -17,7 +17,7 @@ Every entity in Home Assistant has a default icon assigned to it. There are way
### Icon picker
The most common way you can find icons is by using the icon picker built right into Home Assistant. Click into the "Icon" field when customizing an entity and start typing. The list will filter to icons that match your search criteria. You can also scroll through all available icons when the field is empty.
The most common way you can find icons is by using the icon picker built right into Home Assistant. Select the "Icon" field when customizing an entity and start typing. The list will filter to icons that match your search criteria. You can also scroll through all available icons when the field is empty.
<p class='img'>
<img src='/images/screenshots/icon-picker.png' alt='Icon Picker in Home Assistant' />