it's Meshtastic 🤦🏻‍♂️

docs/development/device/http-api.mdx

@@ -19,12 +19,12 @@ This is a mini-spec on a HTTP API which can be used by browser based clients to
 ## Request headers
 
 - `Content-Type: application/x-protobuf`
-  - Indicates protobuf content (Meshtatic protobufs)
+  - Indicates protobuf content (Meshtastic protobufs)
 
 ## Response headers
 
 - `Content-Type: application/x-protobuf`
-  - Indicates protobuf content (Meshtatic protobufs)
+  - Indicates protobuf content (Meshtastic protobufs)
 - `X-Protobuf-Schema: <URI to the .proto schema file>`
   - Not required but recommended for documentation/reflection purposes
 

docs/hardware/devices/chatter/index.mdx

@@ -14,7 +14,7 @@ Chatter V2.0 sports:
  - an i2c port to easily connect a GPS
  - a different routing
  
-Both versions are fully supported by Meshastic with the same firmware. 
+Both versions are fully supported by Meshtastic with the same firmware. 
 
 The Meshtastic firmware works with the stock hardware, however, the LLCC68 LoRa chip cripples the RF capability of the device. As is, the Chatter can only communicate on the Medium-Slow channel. 
 Switching the chip with the pin-compatible and more capable Heltec RA62 (as mentioned in this Github issue https://github.com/meshtastic/firmware/issues/2896) unlock the full potential of the device.

docs/hardware/devices/linux-native-hardware/linux-native-hardware.mdx

@@ -204,7 +204,7 @@ This will give you a detailed view of the service status and any potential error
 
 By following these steps, you set up a systemd service for meshtasticd that will start automatically at boot and restart if it crashes. You can manage it using the standard systemctl commands (start, stop, restart, status, etc.).
 
-#### View Logs of Mesthastic
+#### View Logs of Meshtastic
 To view the log output of the meshtasticd service, use the below command to read them out of the system journal.
 
 ```shell