Fix possible typos (#420)

Author: dp111

i2c/lcd_1602_i2c/lcd_1602_i2c.c

@@ -13,7 +13,7 @@
 /* Example code to drive a 16x2 LCD panel via a I2C bridge chip (e.g. PCF8574)
 
    NOTE: The panel must be capable of being driven at 3.3v NOT 5v. The Pico
-   GPIO (and therefor I2C) cannot be used at 5v.
+   GPIO (and therefore I2C) cannot be used at 5v.
 
    You will need to use a level shifter on the I2C lines if you want to run the
    board at 5v.

i2c/lis3dh_i2c/lis3dh_i2c.c

@@ -12,7 +12,7 @@
 
 /* Example code to talk to a LIS3DH Mini GPS module.
 
-   This example reads data from all 3 axes of the accelerometer and uses an auxillary ADC to output temperature values.
+   This example reads data from all 3 axes of the accelerometer and uses an auxiliary ADC to output temperature values.
 
    Connections on Raspberry Pi Pico board, other boards may vary.
 
@@ -44,7 +44,7 @@ void lis3dh_init() {
     buf[1] = 0x80;
     i2c_write_blocking(i2c_default, ADDRESS, buf, 2, false);
 
-    // Turn auxillary ADC on
+    // Turn auxiliary ADC on
     buf[0] = TEMP_CFG_REG;
     buf[1] = 0xC0;
     i2c_write_blocking(i2c_default, ADDRESS, buf, 2, false);

i2c/mcp9808_i2c/mcp9808_i2c.c

@@ -17,7 +17,7 @@
    Connections on Raspberry Pi Pico board, other boards may vary.
 
    GPIO PICO_DEFAULT_I2C_SDA_PIN (On Pico this is GP4 (physical pin 6)) -> SDA on MCP9808 board
-   GPIO PICO_DEFAULT_I2C_SCK_PIN (On Pico this is GP5 (physcial pin 7)) -> SCL on MCP9808 board
+   GPIO PICO_DEFAULT_I2C_SCK_PIN (On Pico this is GP5 (physical pin 7)) -> SCL on MCP9808 board
    Vsys (physical pin 39) -> VDD on MCP9808 board
    GND (physical pin 38)  -> GND on MCP9808 board
 

i2c/mma8451_i2c/mma8451_i2c.c

@@ -17,7 +17,7 @@
    Connections on Raspberry Pi Pico board, other boards may vary.
 
    GPIO PICO_DEFAULT_I2C_SDA_PIN (On Pico this is GP4 (physical pin 6)) -> SDA on MMA8451 board
-   GPIO PICO_DEFAULT_I2C_SCK_PIN (On Pico this is GP5 (physcial pin 7)) -> SCL on MMA8451 board
+   GPIO PICO_DEFAULT_I2C_SCK_PIN (On Pico this is GP5 (physical pin 7)) -> SCL on MMA8451 board
    VSYS (physical pin 39) -> VDD on MMA8451 board
    GND (physical pin 38)  -> GND on MMA8451 board
 

i2c/mpu6050_i2c/mpu6050_i2c.c

@@ -17,7 +17,7 @@
    inbuilt FIFO to make it more useful.
 
    NOTE: Ensure the device is capable of being driven at 3.3v NOT 5v. The Pico
-   GPIO (and therefor I2C) cannot be used at 5v.
+   GPIO (and therefore I2C) cannot be used at 5v.
 
    You will need to use a level shifter on the I2C lines if you want to run the
    board at 5v.

i2c/pa1010d_i2c/pa1010d_i2c.c

@@ -73,7 +73,7 @@ void pa1010d_parse_string(char output[], char protocol[]) {
     // Displays GNRMC data
     // Similarly, additional if statements can be used to add more protocols 
     if (strcmp(protocol, "GNRMC") == 0) {
-        printf("Protcol:%s\n", gps_data[0]);
+        printf("Protocol:%s\n", gps_data[0]);
         printf("UTC Time: %s\n", gps_data[1]);
         printf("Status: %s\n", gps_data[2][0] == 'V' ? "Data invalid. GPS fix not found." : "Data Valid");
         printf("Latitude: %s\n", gps_data[3]);

i2c/ssd1306_i2c/ssd1306_font.h

@@ -5,7 +5,7 @@
  */
 
 // Vertical bitmaps, A-Z, 0-9. Each is 8 pixels high and wide
-// Theses are defined vertically to make them quick to copy to FB
+// These are defined vertically to make them quick to copy to FB
 
 static uint8_t font[] = {
 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // Nothing

ide/vscode/README.md

@@ -42,7 +42,7 @@ The example assumes:
 
 3. Copy the `settings.json` file into the `.vscode` folder. This illustrates how to configure the *CMake* plugin so that you debug using *cortex-debug* instead of trying to launch the executable on the host.
 
-Lauching a debug session in the workspace (e.g. with *f5*) should now build the project and if successful upload it to the target, open a debug session and pause at the start of `main()`.
+Launching a debug session in the workspace (e.g. with *f5*) should now build the project and if successful upload it to the target, open a debug session and pause at the start of `main()`.
 
 > VSCode has some background work to do the first time through. If appears to have stalled then leave it alone for at least a minute.
 

pico_w/wifi/access_point/dhcpserver/dhcpserver.c

@@ -283,7 +283,7 @@ static void dhcp_server_process(void *arg, struct udp_pcb *upcb, struct pbuf *p,
 
     opt_write_n(&opt, DHCP_OPT_SERVER_ID, 4, &ip4_addr_get_u32(ip_2_ip4(&d->ip)));
     opt_write_n(&opt, DHCP_OPT_SUBNET_MASK, 4, &ip4_addr_get_u32(ip_2_ip4(&d->nm)));
-    opt_write_n(&opt, DHCP_OPT_ROUTER, 4, &ip4_addr_get_u32(ip_2_ip4(&d->ip))); // aka gateway; can have mulitple addresses
+    opt_write_n(&opt, DHCP_OPT_ROUTER, 4, &ip4_addr_get_u32(ip_2_ip4(&d->ip))); // aka gateway; can have multiple addresses
     opt_write_n(&opt, DHCP_OPT_DNS, 4, &ip4_addr_get_u32(ip_2_ip4(&d->ip))); // this server is the dns
     opt_write_u32(&opt, DHCP_OPT_IP_LEASE_TIME, DEFAULT_LEASE_TIME_S);
     *opt++ = DHCP_OPT_END;

pico_w/wifi/access_point/dnsserver/dnsserver.c

@@ -202,7 +202,7 @@ static void dns_server_process(void *arg, struct udp_pcb *upcb, struct pbuf *p,
 
     dns_hdr->flags = lwip_htons(
                 0x1 << 15 | // QR = response
-                0x1 << 10 | // AA = authoritive
+                0x1 << 10 | // AA = authoritative
                 0x1 << 7);   // RA = authenticated
     dns_hdr->question_count = lwip_htons(1);
     dns_hdr->answer_record_count = lwip_htons(1);

pico_w/wifi/python_test_tcp/python_test_tcp_server.py

@@ -3,7 +3,7 @@
 import random
 import socket
 
-# Set server adress to machines IP
+# Set server address to machines IP
 SERVER_ADDR = "0.0.0.0"
 
 # These constants should match the client

pio/ir_nec/README.adoc

@@ -2,7 +2,7 @@
 
 This example shows how to use the Raspberry Pi Pico (RP2040) to send and receive infra-red frames in the 'NEC' format that is used by many consumer remote control applications.
 
-It performs a loopback test by transmitting IR codes via an IR LED and receiving them on an IR detector. The results are sent to the default serial terminal connnected via UART or USB as configured in the SDK.
+It performs a loopback test by transmitting IR codes via an IR LED and receiving them on an IR detector. The results are sent to the default serial terminal connected via UART or USB as configured in the SDK.
 
 The tasks of encoding and decoding the data are offloaded to the RP2040 PIO state machines. This releases the main processor cores to concentrate on other tasks.
 

pio/ir_nec/nec_receive_library/nec_receive.pio

@@ -12,8 +12,8 @@
 ; The input pin should be connected to an IR detector with an 'active low' output.
 ;
 ; This program expects there to be 10 state machine clock ticks per 'normal' 562.5us burst period
-; in order to permit timely detection of start of a burst. The initailisation function below sets
-; the correct divisor to achive this relative to the system clock.
+; in order to permit timely detection of start of a burst. The initialisation function below sets
+; the correct divisor to achieve this relative to the system clock.
 ;
 ; Within the 'NEC' protocol frames consists of 32 bits sent least-siginificant bit first; so the
 ; Input Shift Register should be configured to shift right and autopush after 32 bits, as in the

pio/ir_nec/nec_transmit_library/nec_transmit.c

@@ -17,7 +17,7 @@
 #include "nec_carrier_control.pio.h"
 
 // Claim an unused state machine on the specified PIO and configure it
-// to transmit NEC IR frames on the specificied GPIO pin.
+// to transmit NEC IR frames on the specified GPIO pin.
 //
 // Returns: on success, the number of the carrier_control state machine
 // otherwise -1

rtc/hello_rtc/hello_rtc.c

@@ -33,7 +33,7 @@ int main() {
     rtc_set_datetime(&t);
 
     // clk_sys is >2000x faster than clk_rtc, so datetime is not updated immediately when rtc_get_datetime() is called.
-    // tbe delay is up to 3 RTC clock cycles (which is 64us with the default clock settings)
+    // The delay is up to 3 RTC clock cycles (which is 64us with the default clock settings)
     sleep_us(64);
 
     // Print the time

spi/mpu9250_spi/mpu9250_spi.c

@@ -18,7 +18,7 @@
    inbuilt FIFO to make it more useful.
 
    NOTE: Ensure the device is capable of being driven at 3.3v NOT 5v. The Pico
-   GPIO (and therefor SPI) cannot be used at 5v.
+   GPIO (and therefore SPI) cannot be used at 5v.
 
    You will need to use a level shifter on the I2C lines if you want to run the
    board at 5v.