From 8a6fa5a803708014d6491af68c804229b543025e Mon Sep 17 00:00:00 2001 From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com> Date: Sat, 18 Nov 2023 11:29:00 +0100 Subject: [PATCH] Docs: apply sentence-style capitalization (#29891) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Docs: apply sentence-style capitalization * Update source/_docs/automation/trigger.markdown * Apply suggestions from code review Co-authored-by: Joakim Sørensen --------- Co-authored-by: Joakim Sørensen --- source/_docs/authentication/providers.markdown | 4 ++-- source/_docs/automation/templating.markdown | 6 +++--- source/_docs/automation/trigger.markdown | 2 +- source/_docs/automation/yaml.markdown | 2 +- source/_docs/configuration/securing.markdown | 2 +- source/_docs/frontend/icons.markdown | 2 +- 6 files changed, 9 insertions(+), 9 deletions(-) diff --git a/source/_docs/authentication/providers.markdown b/source/_docs/authentication/providers.markdown index 04920ebb4a9..35329f4e970 100644 --- a/source/_docs/authentication/providers.markdown +++ b/source/_docs/authentication/providers.markdown @@ -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. diff --git a/source/_docs/automation/templating.markdown b/source/_docs/automation/templating.markdown index 2fef062f41d..692ad2f6d68 100644 --- a/source/_docs/automation/templating.markdown +++ b/source/_docs/automation/templating.markdown @@ -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 | | ---- | ---- | diff --git a/source/_docs/automation/trigger.markdown b/source/_docs/automation/trigger.markdown index b56874587f4..89becc5c24f 100644 --- a/source/_docs/automation/trigger.markdown +++ b/source/_docs/automation/trigger.markdown @@ -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 | | -------- | -------- | ---------------------------------------- | diff --git a/source/_docs/automation/yaml.markdown b/source/_docs/automation/yaml.markdown index 48d9fd9ee28..e26907af3e9 100644 --- a/source/_docs/automation/yaml.markdown +++ b/source/_docs/automation/yaml.markdown @@ -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. diff --git a/source/_docs/configuration/securing.markdown b/source/_docs/configuration/securing.markdown index 1af61618588..18e5a015e9d 100644 --- a/source/_docs/configuration/securing.markdown +++ b/source/_docs/configuration/securing.markdown @@ -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. diff --git a/source/_docs/frontend/icons.markdown b/source/_docs/frontend/icons.markdown index eebac52093a..7e1e2fb8f79 100644 --- a/source/_docs/frontend/icons.markdown +++ b/source/_docs/frontend/icons.markdown @@ -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.

Icon Picker in Home Assistant