From d35e999e6b4d68c90f643cd480388845928c552b Mon Sep 17 00:00:00 2001
From: c0ffeeca7 <38767475+c0ffeeca7@users.noreply.github.com>
Date: Thu, 16 Nov 2023 12:36:01 +0100
Subject: [PATCH] u-z integrations: apply sentence-style capitalization
 (#29865)

* u-z integrations: apply sentence-style capitalization

* Update source/_integrations/velux.markdown
---
 source/_integrations/upcloud.markdown           | 2 +-
 source/_integrations/update.markdown            | 2 +-
 source/_integrations/vallox.markdown            | 4 ++--
 source/_integrations/venstar.markdown           | 2 +-
 source/_integrations/vicare.markdown            | 2 +-
 source/_integrations/vodafone_station.markdown  | 2 +-
 source/_integrations/volvooncall.markdown       | 2 +-
 source/_integrations/vultr.markdown             | 2 +-
 source/_integrations/w800rf32.markdown          | 2 +-
 source/_integrations/water_heater.mqtt.markdown | 2 +-
 source/_integrations/wirelesstag.markdown       | 2 +-
 source/_integrations/ws66i.markdown             | 4 ++--
 source/_integrations/yamaha_musiccast.markdown  | 8 ++++----
 source/_integrations/zabbix.markdown            | 2 +-
 source/_integrations/zestimate.markdown         | 2 +-
 source/_integrations/zeversolar.markdown        | 2 +-
 source/_integrations/zoneminder.markdown        | 2 +-
 17 files changed, 22 insertions(+), 22 deletions(-)

diff --git a/source/_integrations/upcloud.markdown b/source/_integrations/upcloud.markdown
index 22475321557..ddfd515c579 100644
--- a/source/_integrations/upcloud.markdown
+++ b/source/_integrations/upcloud.markdown
@@ -30,7 +30,7 @@ Set up your API user credentials in your [UpCloud control panel](https://hub.upc
 
 {% include integrations/config_flow.md %}
 
-## Binary Sensor
+## Binary sensor
 
 A binary sensor entity is set up for all discovered servers.
 
diff --git a/source/_integrations/update.markdown b/source/_integrations/update.markdown
index 5d243ff470d..f5f06681409 100644
--- a/source/_integrations/update.markdown
+++ b/source/_integrations/update.markdown
@@ -49,7 +49,7 @@ information on the update state:
 - `release_summary`: A summary of the release notes for the update available.
 - `release_url`: A link to the full release announcement for the update available.
 
-## Device Classes
+## Device classes
 
 The way these update entities are displayed in the frontend depend on their
 device classes. The following device classes are supported for switches:
diff --git a/source/_integrations/vallox.markdown b/source/_integrations/vallox.markdown
index dfeae5ee1c7..4c5171655da 100644
--- a/source/_integrations/vallox.markdown
+++ b/source/_integrations/vallox.markdown
@@ -34,7 +34,7 @@ The **number** platform allows to control supply air temperatures.
 
 {% include integrations/config_flow.md %}
 
-## Profile Switching
+## Profile switching
 
 For convenient switching of ventilation profiles in the GUI, just click on the `Vallox` fan entity to get a drop-down menu to select from. Alternatively, the service `fan/set_preset_mode` can be used.
 
@@ -45,7 +45,7 @@ The four standard Vallox profiles are supported:
 - `Boost`
 - `Fireplace`
 
-## Fan Services
+## Fan services
 
 ### Service `vallox.set_profile_fan_speed_home`
 
diff --git a/source/_integrations/venstar.markdown b/source/_integrations/venstar.markdown
index 5774e108376..eec570e83ca 100644
--- a/source/_integrations/venstar.markdown
+++ b/source/_integrations/venstar.markdown
@@ -50,7 +50,7 @@ The following values are supported for the preset_mode state attribute:
 
 Note - Please ensure that you update your thermostat to the latest firmware. Initially tested on firmware 5.10 and currently VH6.79.  
 
-### Enabling Local API
+### Enabling local API
 Local API mode needs to be enabled on the thermostat itself. It cannot be enabled using the Venstar mobile apps or Skyport cloud service. Exact steps vary across different [series](https://venstar.com/thermostats/) of thermostats:
 
 - [ColorTouch](https://venstar.com/thermostats/colortouch/)
diff --git a/source/_integrations/vicare.markdown b/source/_integrations/vicare.markdown
index d42265d72e9..10bd84c2df7 100644
--- a/source/_integrations/vicare.markdown
+++ b/source/_integrations/vicare.markdown
@@ -112,7 +112,7 @@ Eco mode reduces the target temperature by 3°C, whereas Comfort mode sets the t
 | `entity_id` | yes | String or list of strings that point at `entity_id`'s of climate devices to control. To target all entities, use `all` keyword instead of entity_id.
 | `preset_mode` | no | New value of preset mode.
 
-## Water Heater
+## Water heater
 
 It is not possible to turn on/off water heating via the Water Heater integration since this would conflict with the operation modes of the heating integration. Therefore the operation mode of that integration is just available as an attribute and cannot be modified.
 
diff --git a/source/_integrations/vodafone_station.markdown b/source/_integrations/vodafone_station.markdown
index 7020d34ab4e..fbd79cc0cf3 100644
--- a/source/_integrations/vodafone_station.markdown
+++ b/source/_integrations/vodafone_station.markdown
@@ -39,7 +39,7 @@ To change the settings, go to {% my integrations title="**Settings** > **Devices
 
 ## Additional info
 
-### Device Tracker
+### Device tracker
 
 **Note**: If you don't want to automatically track newly detected devices, disable the integration system option `Enable new added entities`.
 
diff --git a/source/_integrations/volvooncall.markdown b/source/_integrations/volvooncall.markdown
index 3f80ba1bd83..93e069aa662 100644
--- a/source/_integrations/volvooncall.markdown
+++ b/source/_integrations/volvooncall.markdown
@@ -22,7 +22,7 @@ The `volvooncall` integration offers integration with the [Volvo Cars App](https
 
 {% include integrations/config_flow.md %}
 
-### Available Resources
+### Available resources
 
 The list of currently available resources:
 
diff --git a/source/_integrations/vultr.markdown b/source/_integrations/vultr.markdown
index c0ea0883855..10dd4136521 100644
--- a/source/_integrations/vultr.markdown
+++ b/source/_integrations/vultr.markdown
@@ -187,7 +187,7 @@ name:
   type: string
 {% endconfiguration %}
 
-### Additional Examples
+### Additional examples
 
 Full example that produces `switch.amazing_server`, assuming a subscription that has an ID of `123456` and a label of `Web Server`:
 
diff --git a/source/_integrations/w800rf32.markdown b/source/_integrations/w800rf32.markdown
index d89b3a4de64..35428e018b3 100644
--- a/source/_integrations/w800rf32.markdown
+++ b/source/_integrations/w800rf32.markdown
@@ -33,7 +33,7 @@ device:
   type: string
 {% endconfiguration %}
 
-## Binary Sensor
+## Binary sensor
 
 The `w800rf32` platform supports X10 RF binary sensors such as Palm Pad remotes, key chain remotes, Hawkeye motion detectors, and many, many other X10 RF devices. Some that have specifically been used with this are the KR19A keychain, MS16A motion detector and the RSS18 four button wall mount keypad.
 
diff --git a/source/_integrations/water_heater.mqtt.markdown b/source/_integrations/water_heater.mqtt.markdown
index d68e9a0521f..db9545611b3 100644
--- a/source/_integrations/water_heater.mqtt.markdown
+++ b/source/_integrations/water_heater.mqtt.markdown
@@ -265,7 +265,7 @@ value_template:
 
 If a property works in *optimistic mode* (when the corresponding state topic is not set), Home Assistant will assume that any state changes published to the command topics did work and change the internal state of the entity immediately after publishing to the command topic. If it does not work in optimistic mode, the internal state of the entity is only updated when the requested update is confirmed by the device through the state topic. You can enforce optimistic mode by setting the `optimistic` option to `true`. When set, the internal state will always be updated, even when a state topic is defined.
 
-## Using Templates
+## Using templates
 
 For all `*_state_topic`s, a template can be specified that will be used to render the incoming payloads on these topics. Also, a default template that applies to all state topics can be specified as `value_template`. This can be useful if you received payloads are e.g., in JSON format. Since in JSON, a quoted string (e.g., `"foo"`) is just a string, this can also be used for unquoting.
 
diff --git a/source/_integrations/wirelesstag.markdown b/source/_integrations/wirelesstag.markdown
index dae45b50606..0fbcb6471a6 100644
--- a/source/_integrations/wirelesstag.markdown
+++ b/source/_integrations/wirelesstag.markdown
@@ -48,7 +48,7 @@ password:
   type: string
 {% endconfiguration %}
 
-## Binary Sensor
+## Binary sensor
 
 To enable the binary sensor platform for your tags, set up with your [wirelesstag.net](https://wirelesstag.net/) account. Add the following to your `configuration.yaml` file:
 
diff --git a/source/_integrations/ws66i.markdown b/source/_integrations/ws66i.markdown
index 7974e329f19..f7cd5f72db5 100644
--- a/source/_integrations/ws66i.markdown
+++ b/source/_integrations/ws66i.markdown
@@ -19,7 +19,7 @@ The Soundavo WS66i 6-Zone Amplifier integration allows you to control the [Sound
 
 {% include integrations/config_flow.md %}
 
-## Configuration Notes
+## Configuration notes
 
 Enter the IP Address of the WS66i amplifier when prompted to connect to the device and hit submit. It will detect the number of connected amplifiers and present each zone as an entity.
 
@@ -29,6 +29,6 @@ Enter the IP Address of the WS66i amplifier when prompted to connect to the devi
 
 Once detected, you can add them to an area.
 
-## Source Management
+## Source management
 
 You can configure source names by hitting the **CONFIGURE** button in the integration card.
diff --git a/source/_integrations/yamaha_musiccast.markdown b/source/_integrations/yamaha_musiccast.markdown
index 4e584020741..d0454ecf09b 100644
--- a/source/_integrations/yamaha_musiccast.markdown
+++ b/source/_integrations/yamaha_musiccast.markdown
@@ -32,7 +32,7 @@ The Yamaha MusicCast integration implements the grouping services. There are som
 - It is not possible to let mediaplayer entities of the same device (e.g., different zones) be in distinct groups.
 - If a non-main zone is the master of a group, it is not possible to let other mediaplayers of the same device join this group.
 
-## Play Media functionality
+## Play media functionality
 
 The MusicCast integration supports the Home Assistant media browser for all streaming services, your device supports. For services such as Deezer, you have to log in using the official MusicCast app. In addition, local HTTP URLs can be played back using this service. This includes the Home Assistant text-to-speech services.
 
@@ -66,7 +66,7 @@ data:
 
 Depending on the features supported by the device, several entities will be added for every MusicCast Device. Some of the entities are related to the MusicCast device and some are related to a zone of the device. All device and main zone related entities will be assigned to the Home Assistant device of the main zone. Entities related to other zones will be assigned to the Home Assistant device of the corresponding zone.
 
-### Number Entities
+### Number entities
 
 The following entities will be added, if they are supported by the MusicCast device:
 - Equalizer (configuration, zone level)
@@ -80,7 +80,7 @@ The following entities will be added, if they are supported by the MusicCast dev
 - DTS Dialogue Control (configuration, zone level)
   - Control the volume of dialogues for DTS:X content
 
-### Select Entities
+### Select entities
 The following entities will be added, if they are supported by the MusicCast device:
 - Dimmer (configuration, device level)
   - Set the display brightness
@@ -99,7 +99,7 @@ The following entities will be added, if they are supported by the MusicCast dev
 - Link Audio Quality (configuration, zone level)
   - Set the audio quality for grouped speakers
 
-### Switch Entities
+### Switch entities
 The following entities will be added, if they are supported by the MusicCast device:
 - Speaker A (configuration, device level)
   - A switch to turn on the speaker set A
diff --git a/source/_integrations/zabbix.markdown b/source/_integrations/zabbix.markdown
index 55b0ac62bbc..8636b28b5ba 100644
--- a/source/_integrations/zabbix.markdown
+++ b/source/_integrations/zabbix.markdown
@@ -112,7 +112,7 @@ zabbix:
       - sensor.time
 ```
 
-## Configure Filter
+## Configure filter
 
 By default, no entity will be excluded. To limit which entities are being published to Zabbix, you can use the `include` and `exclude` parameters.
 
diff --git a/source/_integrations/zestimate.markdown b/source/_integrations/zestimate.markdown
index 493c4ae71c6..345614f771b 100644
--- a/source/_integrations/zestimate.markdown
+++ b/source/_integrations/zestimate.markdown
@@ -43,7 +43,7 @@ zpid:
   type: list
 {% endconfiguration %}
 
-### Additional Attributes
+### Additional attributes
 
 The following additional attributes are also available via the sensor.
 
diff --git a/source/_integrations/zeversolar.markdown b/source/_integrations/zeversolar.markdown
index e738e2bc642..a42a2ea185e 100644
--- a/source/_integrations/zeversolar.markdown
+++ b/source/_integrations/zeversolar.markdown
@@ -26,7 +26,7 @@ get the Zeversolar IP address.
 
 {% include integrations/config_flow.md %}
 
-## Sensor Types
+## Sensor types
 
 When configured, the integration will create two sensors for each configured inverter:
 
diff --git a/source/_integrations/zoneminder.markdown b/source/_integrations/zoneminder.markdown
index a9d2309723b..ae76d815bce 100644
--- a/source/_integrations/zoneminder.markdown
+++ b/source/_integrations/zoneminder.markdown
@@ -105,7 +105,7 @@ action:
     name: Home
 ```
 
-## Binary Sensor
+## Binary sensor
 
 The `zoneminder` binary sensor platform lets you monitor the availability of your [ZoneMinder](https://www.zoneminder.com) install.