diff --git a/source/_integrations/ombi.markdown b/source/_integrations/ombi.markdown index 7cb3c788e08..d0e3014bb18 100644 --- a/source/_integrations/ombi.markdown +++ b/source/_integrations/ombi.markdown @@ -13,11 +13,11 @@ ha_platforms: ha_integration_type: integration --- -The `Ombi` integration monitors data from your [Ombi](https://ombi.io) instance. +The Ombi integration monitors data from your [Ombi](https://ombi.io) instance. ## Setup -This component needs to authenticate to your Ombi instance with either a user `password` or an `api_key`. +This integration needs to authenticate to your Ombi instance with either a user `password` or an `api_key`. To find your `api_key` open the Ombi web interface. Navigate to **Settings** and then to **Ombi**, you should then be able to see your `api_key`. diff --git a/source/_integrations/onewire.markdown b/source/_integrations/onewire.markdown index 4b1cd21540f..a21cb464c6d 100644 --- a/source/_integrations/onewire.markdown +++ b/source/_integrations/onewire.markdown @@ -19,7 +19,7 @@ ha_platforms: ha_integration_type: hub --- -The `onewire` platform supports sensors which that using the One wire (1-wire) bus for communication. +The Onewire integration supports sensors that use the 1-wire bus for communication. Every 1-wire device has a (globally) unique ID that identifies the device on the bus. The first two digits identify a device family and the last 14 digits are a globally unique number given to it during manufacturing. diff --git a/source/_integrations/onvif.markdown b/source/_integrations/onvif.markdown index a584fcd51ee..971b257ee5f 100644 --- a/source/_integrations/onvif.markdown +++ b/source/_integrations/onvif.markdown @@ -20,7 +20,7 @@ ha_integration_type: integration ha_dhcp: true --- -The `onvif` camera platform allows you to use an [ONVIF](https://www.onvif.org/) Profile S conformant device in Home Assistant. This requires the [`ffmpeg` integration](/integrations/ffmpeg/) to be already configured. +The ONVIF camera integration allows you to use an [ONVIF](https://www.onvif.org/) Profile S conformant device in Home Assistant. This requires the [`ffmpeg` integration](/integrations/ffmpeg/) to be already configured. {% include integrations/config_flow.md %} diff --git a/source/_integrations/openalpr_cloud.markdown b/source/_integrations/openalpr_cloud.markdown index ee2598b6d36..c7b6989a2a3 100644 --- a/source/_integrations/openalpr_cloud.markdown +++ b/source/_integrations/openalpr_cloud.markdown @@ -9,12 +9,12 @@ ha_domain: openalpr_cloud ha_integration_type: integration --- -[OpenALPR](https://www.openalpr.com/) integration for Home Assistant allows you -to process license plates from a camera. You can use them to open a garage door -or trigger any other [automation](/integrations/automation/). +The [OpenALPR](https://www.openalpr.com/) integration for Home Assistant allows you +to process license plates from a camera. This allows you to open a garage door +or trigger any other [automation](/integrations/automation/) based on a license plate. For using the result inside an automation rule, -take a look at the [component](/integrations/image_processing/) page. +take a look at the [integration](/integrations/image_processing/) page. ### Configuration diff --git a/source/_integrations/openuv.markdown b/source/_integrations/openuv.markdown index 19c104b0b8f..56c1537ef5b 100644 --- a/source/_integrations/openuv.markdown +++ b/source/_integrations/openuv.markdown @@ -18,17 +18,17 @@ ha_platforms: ha_integration_type: service --- -The `openuv` integration displays UV and Ozone data from [openuv.io](https://www.openuv.io/). +The OpenUV integration displays UV and Ozone data from [openuv.io](https://www.openuv.io/).
-The guidelines within this documentation constitute estimates and are intended to help -informed decision making. They should not replace analysis, advice or diagnosis from a +The guidelines within this documentation constitute estimates which are intended to help +informed decision making. They should not replace analysis, advice, or diagnosis from a trained medical professional.
## Generating an API Key -To generate an API key, simply log in at [the OpenUV website](https://www.openuv.io/). +To generate an API key, log in at [the OpenUV website](https://www.openuv.io/). {% include integrations/config_flow.md %} @@ -57,7 +57,7 @@ update data via the `homeassistant.update_entity` service. Beginning February 1, 2019, the "Limited" plan (which is what new users are given by default) is limited to 50 API requests per day. Because different API plans and -locations will have different requirements, the `openuv` component does not automatically +locations will have different requirements, the OpenUV integration does not automatically query the API for new data after it initially loads. To request new data, the `homeassistant.update_entity` service should be used.