Fix typos

documentation/asciidoc/accessories/ai-camera/getting-started.adoc

@@ -87,7 +87,7 @@ You can configure the `imx500_object_detection` stage in many ways.
 
 For example, `max_detections` defines the maximum number of objects that the pipeline will detect at any given time. `threshold` defines the minimum confidence value required for the pipeline to consider any input as an object.
 
-The raw inference output data of this network can be quite noisy, so this stage also preforms some temporal filtering and applies hysteresis. To disable this filtering, remove the `temporal_filter` config block.
+The raw inference output data of this network can be quite noisy, so this stage also performs some temporal filtering and applies hysteresis. To disable this filtering, remove the `temporal_filter` config block.
 
 ==== Pose estimation
 

documentation/asciidoc/accessories/camera/synchronous_cameras.adoc

@@ -42,7 +42,7 @@ When using the CAM0 port on a Raspberry Pi 5, CM4 or CM5, append `,cam0` to that
 
 Alternatively, if you wish to swap the cameras' roles at runtime (and they are not both connected to the same Raspberry Pi), omit `,sync-source` or `,sync-sink` above. Instead you can set a module parameter before starting each camera:
 
-For the Raspbery Pi with the source camera:
+For the Raspberry Pi with the source camera:
 [source,console]
 ----
 $ echo 1 | sudo tee /sys/module/imx477/parameters/trigger_mode

documentation/asciidoc/computers/compute-module/cm-peri-sw-guide.adoc

@@ -219,7 +219,7 @@ dtoverlay=enc28j60
 
 Reboot with `sudo reboot`.
 
-If you now run `ifconfig` you should see an aditional `eth<n>` entry for the ENC28J60 NIC. You should also have Ethernet connectivity. Run the following command to test your connectivity:
+If you now run `ifconfig` you should see an additional `eth<n>` entry for the ENC28J60 NIC. You should also have Ethernet connectivity. Run the following command to test your connectivity:
 
 [source,console]
 ----

documentation/asciidoc/computers/config_txt/conditional.adoc

@@ -147,7 +147,7 @@ Syntax:
 ==== `boot_arg1`
 Raspberry Pi 5 and newer devices only.
 
-The `boot_arg1` variable is a 32-bit user defined value which is stored in a reset-safe register allowing parameters to be passed accross a reboot.
+The `boot_arg1` variable is a 32-bit user defined value which is stored in a reset-safe register allowing parameters to be passed across a reboot.
 
 Setting `boot_arg1` to 42 via `config.txt`:
 [source,ini]
@@ -215,7 +215,7 @@ The value of `boot_count` when the OS was started can be read via xref:configura
 ==== `boot_partition`
 The `boot_partition` variable can be used to select alternate OS files (e.g. `cmdline.txt`) to be loaded, depending on which partition `config.txt` was loaded from after processing xref:config_txt.adoc#autoboot-txt[autoboot.txt]. This is intended for use with an `A/B` boot-system with `autoboot.txt` where it is desirable to be able to have identical files installed to the boot partition for both the `A` and `B` images.
 
-The value of the `boot_partition` can be different to the requested `partition` variable if it was overriden by setting `boot_partition` in xref:config_txt.adoc#autoboot-txt[autoboot.txt] or if the specified partion was not bootable and xref:raspberry-pi.adoc#PARTITION_WALK[PARTITION_WALK] was enabled in the EEPROM config.
+The value of the `boot_partition` can be different to the requested `partition` variable if it was overridden by setting `boot_partition` in xref:config_txt.adoc#autoboot-txt[autoboot.txt] or if the specified partition was not bootable and xref:raspberry-pi.adoc#PARTITION_WALK[PARTITION_WALK] was enabled in the EEPROM config.
 
 Example `config.txt` - select the matching root filesystem for the `A/B` boot file-system:
 [source,ini]

documentation/asciidoc/computers/processors/bcm2712.adoc

@@ -27,7 +27,7 @@ In aggregate, the new features present in BCM2712 deliver a performance uplift o
 
 === Vulnerabilities and mitigations
 
-The Cortex-A76 CPU used in the BCM2712 SoC has known vulnerabilites that are all mitigated in Raspberry Pi OS.
+The Cortex-A76 CPU used in the BCM2712 SoC has known vulnerabilities that are all mitigated in Raspberry Pi OS.
 
 To determine the full list of vulnerabilities and the mitigations, you can use the following command line which will list all those in place.
 
@@ -38,6 +38,6 @@ Vulnerability Spectre v1:             Mitigation; __user pointer sanitization
 Vulnerability Spectre v2:             Mitigation; CSV2, BHB
 ```
 
-WARNING: The list above was correct as of April 2025 but may have been superceded. You should use `lscpu` on your Raspberry Pi to get up to date information. This is especially important when using a third-party operating system, as these may not include all the latest mitigations in their Linux kernel builds. The Arm processors used by Raspberry Pi Ltd do not use microcode, so all mitigations are at the kernel level.
+WARNING: The list above was correct as of April 2025 but may have been superseded. You should use `lscpu` on your Raspberry Pi to get up to date information. This is especially important when using a third-party operating system, as these may not include all the latest mitigations in their Linux kernel builds. The Arm processors used by Raspberry Pi Ltd do not use microcode, so all mitigations are at the kernel level.
 
 The vulnerability information reported by `lscpu` is based on the currently executing kernel's detection scheme. It may not accurately reflect the true vulnerability status of the hardware, especially if the OS lacks recent kernel updates. Further vulnerability information on the CPU vendor advisories can be obtained from https://developer.arm.com/Arm%20Security%20Center/Speculative%20Processor%20Vulnerability referencing the Vendor ID and Model name reported by `lscpu`.

documentation/asciidoc/computers/raspberry-pi/eeprom-bootloader.adoc

@@ -544,7 +544,7 @@ Max length: 32 characters
 The `PARTITION` option may be used to specify the boot partition number, if it has not explicitly been set by the `reboot` command (e.g. `sudo reboot N`) or by `boot_partition=N` in `autoboot.txt`.
 This could be used to boot from a rescue partition if the user presses a button.
 
-The latest firmware also allows high partition numbers (> 31) to be overriden. This allows a custom setup of the system hardware watchdog to trigger a reboot with a special high partition number (e.g. 62) which can be detected by the bootloader (using a conditional filter) and remapped to a recovery partition.
+The latest firmware also allows high partition numbers (> 31) to be overridden. This allows a custom setup of the system hardware watchdog to trigger a reboot with a special high partition number (e.g. 62) which can be detected by the bootloader (using a conditional filter) and remapped to a recovery partition.
 
 Example:
 [source,ini]

documentation/asciidoc/computers/raspberry-pi/power-supplies.adoc

@@ -140,7 +140,7 @@ The following table describes the amount of power (in amps) drawn by different R
 
 NOTE: These measurements used a standard Raspberry Pi OS image (current as of 26 Feb 2016, or June 2019 for the Raspberry Pi 4), at room temperature, with the Raspberry Pi connected to a HDMI monitor, USB keyboard, and USB mouse. The Raspberry Pi 3 Model B was connected to a wireless LAN access point, the Raspberry Pi 4 was connected to Ethernet. All these power measurements are approximate and do not take into account power consumption from additional USB devices; power consumption can easily exceed these measurements if multiple additional USB devices or a HAT are connected to the Raspberry Pi.
 
-[.whitepaper, title="Extra PMIC features on Raspberry Pi 4, Raspbery Pi 5 and Compute Module 4", subtitle="", link=https://pip.raspberrypi.com/documents/RP-004340-WP-Extra-PMIC-features-on-Raspberry-Pi-4-and-Compute-Module-4.pdf]
+[.whitepaper, title="Extra PMIC features on Raspberry Pi 4, Raspberry Pi 5 and Compute Module 4", subtitle="", link=https://pip.raspberrypi.com/documents/RP-004340-WP-Extra-PMIC-features-on-Raspberry-Pi-4-and-Compute-Module-4.pdf]
 ****
 A number of different PMIC devices have been used on Raspberry Pi 4, Raspberry Pi 5 and CM4. All the PMICs provide extra functionality alongside that of voltage supply. This document describes how to access these features in software.
 ****

documentation/asciidoc/computers/raspberry-pi/revision-codes.adoc

@@ -371,7 +371,7 @@ NOQuuuWuFMMMCCCCPPPPTTTTTTTTRRRR
 
 NOTE: This list is not exhaustive - there may be codes in use that are not in this table. Please see the next section for best practices on using revision codes to identify boards.
 
-// This table is now sorted by Type (from table above), then Revision, then RAM, and finally Code. This is the most likley order-of-manufacture, which means we'll normally just add new revision-codes to the very bottom of the table, without having to worry about re-ordering entries.
+// This table is now sorted by Type (from table above), then Revision, then RAM, and finally Code. This is the most likely order-of-manufacture, which means we'll normally just add new revision-codes to the very bottom of the table, without having to worry about re-ordering entries.
 
 |===
 | Code | Model | Revision | RAM | Manufacturer

scripts/postprocess_doxygen_xml.py

@@ -166,6 +166,6 @@ def postprocess_doxygen_xml(xml_path):
 if __name__ == '__main__':
     xml_path = sys.argv[1]
     file_path = os.path.realpath(__file__)
-    # splitting thse subs into two parts to make testing easier
+    # splitting these subs into two parts to make testing easier
     # xml_path = re.sub(r'/documentation-toolchain/.*?$', "/"+xml_path, re.sub(r'/lib/', "/", file_path))
     postprocess_doxygen_xml(xml_path)