diff --git a/source/_integrations/gstreamer.markdown b/source/_integrations/gstreamer.markdown
index 9f66b31fc5c..2001492bda7 100644
--- a/source/_integrations/gstreamer.markdown
+++ b/source/_integrations/gstreamer.markdown
@@ -43,7 +43,7 @@ Only the `music` media type is supported.
 
 And then install the following system dependencies:
 
-Debian/Ubuntu/Rasbian:
+Debian/Ubuntu/Raspberry Pi OS (formerly Raspbian):
 
 ```bash
 sudo apt-get install python3-gst-1.0 \
@@ -52,7 +52,7 @@ sudo apt-get install python3-gst-1.0 \
     gstreamer1.0-tools
 ```
 
-Red Hat/Centos/Fedora:
+Red Hat/CentOS/Fedora:
 
 ```bash
 sudo yum install -y python-gstreamer1 gstreamer1-plugins-good \
diff --git a/source/_integrations/html5.markdown b/source/_integrations/html5.markdown
index e02b3899b1f..c5317a29df3 100644
--- a/source/_integrations/html5.markdown
+++ b/source/_integrations/html5.markdown
@@ -29,7 +29,7 @@ The `html5` platform can only function if all of the following requirements are
 
 - You are using Chrome and/or Firefox on any desktop platform, ChromeOS or Android. Or you added your Home Assistant instance to your home screen on iOS 16.4 or higher.
 - Your Home Assistant instance is accessible from outside your network over HTTPS or can perform an alternative [Domain Name Verification Method](https://support.google.com/webmasters/answer/9008080#domain_name_verification) on the domain used by Home Assistant.
-- If using a proxy, HTTP basic authentication must be off for registering or unregistering for push notifications. It can be re-enabled afterwards.
+- If using a proxy, HTTP basic authentication must be disabled to register or deregister push notifications. It can be re-enabled afterwards.
 - If you don't run Hass.io: `pywebpush` must be installed. `libffi-dev`, `libpython-dev` and `libssl-dev` must be installed prior to `pywebpush` (i.e., `pywebpush` probably won't automatically install).
 - You have configured SSL/TLS for your Home Assistant. It doesn't need to be configured in Home Assistant though, e.g., you can be running NGINX in front of Home Assistant and this will still work. The certificate must be trustworthy (i.e., not self-signed).
 - You are willing to accept the notification permission in your browser.
diff --git a/source/_integrations/hue.markdown b/source/_integrations/hue.markdown
index 0c6924f16b4..ed661f822a8 100644
--- a/source/_integrations/hue.markdown
+++ b/source/_integrations/hue.markdown
@@ -64,7 +64,7 @@ You can use this action for example if you'd like to start/stop Dynamic Mode.
 
 ## Hue remotes and switches
 
-Hue remotes such as the Dimmer Switch are stateless devices, meaning that they do not have a on/off state like regular entities in Home Assistant. Instead, such devices emit the event `hue_event` when a button is pressed. You can test what events come in using the event {% my developer_events title="developer tools in Home Assistant" %} and subscribe to the `hue_event`. Once you know what the event data looks like, you can use this to create automations.
+Hue remotes such as the Dimmer Switch are stateless devices, meaning that they do not have an on/off state like regular entities in Home Assistant. Instead, such devices emit the event `hue_event` when a button is pressed. You can test what events come in using the event {% my developer_events title="developer tools in Home Assistant" %} and subscribe to the `hue_event`. Once you know what the event data looks like, you can use this to create automations.
 
 {% note %}
 At the time of writing, there's a limitation on the Hue API that each device can only send one event per second. This means that button events are rate-limited to 1 per second. This is brought to the attention of Signify and it will hopefully be fixed soon.
diff --git a/source/_integrations/influxdb.markdown b/source/_integrations/influxdb.markdown
index e099e09c796..ac8cfcfb8cc 100644
--- a/source/_integrations/influxdb.markdown
+++ b/source/_integrations/influxdb.markdown
@@ -64,7 +64,7 @@ port:
   default: 8086
 path:
   type: string
-  description: Path to use if your InfuxDB is running behind a reverse proxy.
+  description: Path to use if your InfluxDB is running behind a reverse proxy.
   required: false
 username:
   type: string
@@ -369,7 +369,7 @@ port:
   default: 8086
 path:
   type: string
-  description: Path to use if your InfuxDB is running behind a reverse proxy.
+  description: Path to use if your InfluxDB is running behind a reverse proxy.
   required: false
 username:
   type: string
diff --git a/source/_integrations/islamic_prayer_times.markdown b/source/_integrations/islamic_prayer_times.markdown
index 281b409f590..60d98d36281 100644
--- a/source/_integrations/islamic_prayer_times.markdown
+++ b/source/_integrations/islamic_prayer_times.markdown
@@ -52,7 +52,7 @@ sensors:
 
 ## Configuration
 
-### Prayer calcuation method
+### Prayer calculation method
 
 Default: Islamic Society of North America
 
@@ -72,4 +72,4 @@ Default: Standard (mid sunset to sunrise)
 
 Default: Shafi
 
-Method for adjusting Asr time calcuation, if not specified, it defaults to Shafi.
+Method for adjusting Asr time calculation, if not specified, it defaults to Shafi.
diff --git a/source/_integrations/light.mqtt.markdown b/source/_integrations/light.mqtt.markdown
index c1e2a59eaf0..adc2a7ea6e1 100644
--- a/source/_integrations/light.mqtt.markdown
+++ b/source/_integrations/light.mqtt.markdown
@@ -1237,7 +1237,7 @@ mqtt:
 
 {% endraw %}
 
-### CCT light (brightnes and temperature)
+### CCT light (brightness and temperature)
 
 This example comes from a configuration of Shelly RGBW Bulb working in White mode.
 `max_mireds` and `min_mireds` set color temperature boundaries to 3000K - 6500K. Notice the same limits are applied in `command_on_template`, but in kelvin units this time. It's due to conversion from mired to kelvin which causes exceeding boundary values accepted by the device.