Fix typos throughout documentation

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: swoboda1337

content/changelog/2023.12.0.md

@@ -36,12 +36,12 @@ duplicate pin definitions. See the [Pin Schema](/guides/configuration-types#pin-
 
 ## Touchscreen internal changes
 
-The touchscreen compoenent code has had a big overhaul which breaks any external components or open PRs for
+The touchscreen component code has had a big overhaul which breaks any external components or open PRs for
 new touchscreens. See {{< pr number="4596" repo="esphome" >}} for details if this affects you.
 
 ## MCP3008 breaking changes
 
-The MCP3008 has has a restructure of the code and at the same time the default update interval has been changed
+The MCP3008 has had a restructure of the code and at the same time the default update interval has been changed
 to 60 seconds, the units, device class and state class default have also been set to sane defaults expected for
 a voltage sensor.
 

content/changelog/2024.12.0.md

@@ -20,7 +20,7 @@ ESPHome has now updated the core ESP32 code to use [ESP-IDF](https://github.com/
 This is a major upgrade and should bring more features, chip support (Most notably the ESP32-C6 that people
 keep raving on about) and in general more stability.
 
-To acommodate this change, ESPHome has moved away from the "official" platformio provided ESP32 platform,
+To accommodate this change, ESPHome has moved away from the "official" platformio provided ESP32 platform,
 and is now using a community fork [pioarduino/platform-espressif32](https://github.com/pioarduino/platform-espressif32)
 as platformio has decided to stop providing ESP-IDF updates to their platform for Espressif chips. As a user,
 you should not notice any difference.

content/components/alarm_control_panel/template.md

@@ -84,7 +84,7 @@ control panel is armed, a fault on this type of zone will cause the alarm to go
 The `instant_always` trigger mode is typically used for tamper inputs. Irrespective of whether the alarm control panel
 is armed, a fault will always cause the alarm to go directly to the `triggered` state.
 
-The `delayed_follower` trigger mode is typically specifed for interior passive infared (PIR) or microwave sensors. One
+The `delayed_follower` trigger mode is typically specified for interior passive infrared (PIR) or microwave sensors. One
 of two things happen when a `delayed_follower` zone is faulted:
 
 1. When the alarm panel is in the armed state, a fault on a zone with `delayed_follower` specified will cause the alarm
@@ -95,7 +95,7 @@ of two things happen when a `delayed_follower` zone is faulted:
 
 The `delayed_follower` trigger mode offers better protection if someone enters a premises via an unprotected window
 or door. If there is a PIR guarding the main hallway, it will cause an instant trigger of the alarm panel as someone
-entered the premises in a unusual manner. Likewise, if someone enters the premises though a door set to the `delayed`
+entered the premises in an unusual manner. Likewise, if someone enters the premises through a door set to the `delayed`
 trigger mode, and then triggers the PIR, the alarm will stay in the `pending` state until either they disarm the alarm,
 or the pending timer expires.
 

content/components/api.md

@@ -104,7 +104,7 @@ api:
 
 - **id** (*Optional*, [ID](/guides/configuration-types#id)): Manually specify the ID used for code generation.
 - **password** (*Optional*, **Deprecated**, string): The password to protect the API Server with. Defaults
-  to no password. It is recommended to use the `encryption` -> `key` above instead of the the `password`.
+  to no password. It is recommended to use the `encryption` -> `key` above instead of the `password`.
 
 - **on_client_connected** (*Optional*, [Action](/automations/actions#all-actions)): An automation to perform when a client
   connects to the API. See [`on_client_connected` Trigger](#api-on_client_connected_trigger).

content/components/climate/pid.md

@@ -258,7 +258,7 @@ To autotune the control parameters:
 
 1. Set an appropriate setpoint (see note above) and turn on the climate controller (Heat, Cool or Auto).
 
-1. Click the *PID Climate Autotune* button and look at the the logs of the device.
+1. Click the *PID Climate Autotune* button and look at the logs of the device.
 
     You should see output like
 
@@ -298,7 +298,7 @@ To autotune the control parameters:
       Please copy these values into your YAML configuration! They will reset on the next reboot.
     ```
 
-    As soon as the the autotune procedure finishes, the climate starts to work with the calculated parameters
+    As soon as the autotune procedure finishes, the climate starts to work with the calculated parameters
     so that expected operation can be immediately verified.
 
     If satisfied, copy the values in `control_parameters` into your configuration:

content/components/cover/template.md

@@ -55,7 +55,7 @@ Possible return values for the optional lambda:
   be performed when the remote requests the cover to be stopped.
 
 - **toggle_action** (*Optional*, [Action](/automations/actions#all-actions)): The action that should
-  be performed when the remote requests to toggle the the cover.
+  be performed when the remote requests to toggle the cover.
 
 - **optimistic** (*Optional*, boolean): Whether to operate in optimistic mode - when in this mode,
   any command sent to the template cover will immediately update the reported state/position and no lambda

content/components/dfrobot_sen0395.md

@@ -140,9 +140,9 @@ switch:
 - **type** (**Required**): One of:
 
   - `presence_via_uart`  : when enabled, the module sends presence information via both the serial connection and
-    GPIO pin; when disabled, presense is indicated only via the GPIO pin.
+    GPIO pin; when disabled, presence is indicated only via the GPIO pin.
 
-  - `sensor_active`  : when enabled, presence detection is reported; when disabled, presense will not be reported.
+  - `sensor_active`  : when enabled, presence detection is reported; when disabled, presence will not be reported.
   - `start_after_boot`  : when enabled, the sensor will start immediately after power-on; when disabled, the sensor
     must be manually started.
 

content/components/display/ili9xxx.md

@@ -146,7 +146,7 @@ Each entry represents a single-byte command followed by zero or more data bytes.
 
 ### CUSTOM model
 
-The `CUSTOM` model selection is provided for otherwise unsupported displays, and requires both `dimensions:` and `init_sequence:` to be specfied. There is no pre-defined init sequence.
+The `CUSTOM` model selection is provided for otherwise unsupported displays, and requires both `dimensions:` and `init_sequence:` to be specified. There is no pre-defined init sequence.
 
 ### Configuration examples
 

content/components/display/mipi_spi.md

@@ -186,7 +186,7 @@ If converting from other code, make sure the length byte, if present, is not cop
 
 ## CUSTOM model
 
-The `CUSTOM` model selection is provided for otherwise unsupported displays, and requires both `dimensions:` and `init_sequence:` to be specfied. There is no pre-defined init sequence.
+The `CUSTOM` model selection is provided for otherwise unsupported displays, and requires both `dimensions:` and `init_sequence:` to be specified. There is no pre-defined init sequence.
 
 ## Using the `transform` options
 

content/components/display/ssd1325.md

@@ -52,7 +52,7 @@ display:
 
 - **dc_pin** (**Required**, [Pin Schema](/guides/configuration-types#pin-schema)): The DC pin.
 - **reset_pin** (*Optional*, [Pin Schema](/guides/configuration-types#pin-schema)): The RESET pin.
-- **cs_pin** (*Optional*, [Pin Schema](/guides/configuration-types#pin-schema)): The pin on the ESP that that the CS line is connected to.
+- **cs_pin** (*Optional*, [Pin Schema](/guides/configuration-types#pin-schema)): The pin on the ESP that the CS line is connected to.
   The CS line can be connected to GND if this is the only device on the SPI bus.
 
 - **lambda** (*Optional*, [lambda](/automations/templates#config-lambda)): The lambda to use for rendering the content on the display.