Format with prettier

docs/about/concepts/clients.md

@@ -3,6 +3,7 @@ id: clients
 title: Clients
 sidebar_label: Clients
 ---
+
 ## Overview
 
 ## Available Clients

docs/about/concepts/overview.md

@@ -3,4 +3,5 @@ id: overview
 title: Meshtastic Concepts
 sidebar_label: Concepts Overview
 ---
+
 ## Overview

docs/about/overview.md

@@ -4,6 +4,7 @@ title: About Meshtastic
 sidebar_label: About Meshtastic
 slug: /about
 ---
+
 :::info
 This section is new and is still being developed. If you'd like to contribute, please do!
 :::
@@ -25,6 +26,7 @@ When a receiving radio captures a packet, it checks to see if it has heard that
 For each message a radio rebroadcasts, it marks the "hop limit" down by one. When a radio receives a packet with a hop limit of zero, it will not rebroadcast the message.
 
 ## Who develops Meshtastic
+
 <!--- FIXME add Github organization list/contributor list --->
 
 Meshtastic is an open source project available on GitHub. Our generous volunteers donate their personal time to write and maintain this codebase. If you would like to contribute see our [GitHub](https://github.com/meshtastic), join our [Discord server](https://discord.com/invite/UQJ5QuM7vq), and read up on our [forum](https://meshtastic.discourse.group).

docs/developers/android/mapbox.md

@@ -12,9 +12,9 @@ In order to compile a new version of Meshtastic that can use MapBox you will nee
 
 This is fairly simple to do.
 
-* Create an account at MapBox
+- Create an account at MapBox
-* Copy the public token associated with that account to the clipboard
+- Copy the public token associated with that account to the clipboard
-* Paste that into the file "…/src/main/res/values/mapbox-token.xml"
+- Paste that into the file "…/src/main/res/values/mapbox-token.xml"
 
 ## Examples of what can be achieved with MapBox
 

docs/developers/device/device-api.md

@@ -112,7 +112,7 @@ SoftwareUpdateService UUID cb0b9a0b-a84c-4c0d-bdbb-442e3144ee30
 Characteristics
 
 | UUID                                 | properties  | description                                                                                                    |
-| ------------------------------------ | ----------- | ----------------------------------------------------------------------------------------------------------------- |
+| ------------------------------------ | ----------- | -------------------------------------------------------------------------------------------------------------- |
 | e74dd9c0-a301-4a6f-95a1-f0e1dbea8e1e | write,read  | total image size, 32 bit, write this first, then read back to see if it was acceptable (0 mean not accepted)   |
 | e272ebac-d463-4b98-bc84-5cc1a39ee517 | write       | data, variable sized, recommended 512 bytes, write one for each block of file                                  |
 | 4826129c-c22a-43a3-b066-ce8f0d5bacc6 | write       | crc32, write last - writing this will complete the OTA operation, now you can read result                      |

docs/developers/device/port-numbers.md

@@ -9,7 +9,7 @@ For any new apps that run on the device or via sister apps on phones/PCs they sh
 If you are making a new app using meshtastic, please send in a pull request to add your 'portnum' to this master table. PortNums should be assigned in the following range:
 
 | Portnum | Usage                                                                                                                  |
-| --- | --- |
+| ------- | ---------------------------------------------------------------------------------------------------------------------- |
 | 0-63    | Core Meshtastic use, do not use for third party apps                                                                   |
 | 64-127  | Registered 3rd party apps, send in a pull request that adds a new entry to portnums.proto to register your application |
 | 256-511 | Use one of these portnums for your private applications that you do not want to register publicly                      |

docs/developers/device/radio-settings.md

@@ -60,7 +60,7 @@ Considerations:
 We have six predefined channels. These are the most common settings and have been proven to work well:
 
 | Channel setting     | Alt Channel Name | Data-rate           | SF / Symbols | Coding Rate | Bandwidth | Link Budget |
-| :------------------------- | :--------------- | :------------------- | :----------- | :---------- | :-------- | :---------- |
+| :------------------ | :--------------- | :------------------ | :----------- | :---------- | :-------- | :---------- |
 | Short Range / Fast  | Short Fast       | 18.89 kbps          | 7 / 128      | 4/5         | 500       | 134dB       |
 | Short Range / Slow  | Short Slow       | 4.69 kbps           | 7 / 128      | 4/5         | 125       | 140dB       |
 | Medium Range / Fast | Medium Fast      | 1.2 kbps            | 10 / 1024    | 4/6         | 250       | 146dB       |
@@ -83,7 +83,7 @@ After applying the settings, you will need to restart the device. After your dev
 Some example settings:
 
 | Data-rate  | SF / Symbols | Coding Rate | Bandwidth | Link Budget | Note                                                                     |
-| :--------- | :----------- | :---------- | :-------- | :---------- | :---------------------------------------------------------------------- |
+| :--------- | :----------- | :---------- | :-------- | :---------- | :----------------------------------------------------------------------- |
 | 37.50 kbps | 6 / 64       | 4/5         | 500       | 129dB       | Fastest possible speed                                                   |
 | 3.125 kbps | 8 / 256      | 4/5         | 125       | 143dB       |                                                                          |
 | 1.953 kbps | 8 / 256      | 4/8         | 125       | 143dB       |                                                                          |

docs/developers/maintaining-documentation/docusaurus.md

@@ -3,8 +3,11 @@ id: docusaurus
 title: Docusaurus
 sidebar_label: Docusaurus
 ---
+
 ## Overview
+
 Meshtastic's documentation is set up using [Docusaurus](https://docusaurus.io). It is highly encouraged to look at [their documentation](https://docusaurus.io/docs) when looking for a solution to a problem with our docs. They most likely have thought of the use case you've discovered.
 
 ## Known Issues
+
 - Admonitions within a `TabItem` component need to be completely unindented to show up correctly.

docs/developers/maintaining-documentation/github.md

@@ -3,9 +3,12 @@ id: github
 title: GitHub
 sidebar_label: GitHub
 ---
+
 ## Overview
+
 All of Meshtastic's code and documentation is hosted on GitHub. If you would like to contribute to the project, having a GitHub account is an important step to doing so.
 
 ## Set up GitHub account
+
 - Go to [github.com](https://github.com)
 - Click `Sign Up`

docs/developers/maintaining-documentation/overview.md

@@ -3,9 +3,11 @@ id: overview
 title: Maintaining Documentation
 sidebar_label: Maintaining Documentation
 ---
+
 Meshtastic documentation is an important ingredient to the overall project. We want users to hit the ground running with the information they need right at their finger tips. This section will discuss the documentation software stack, file organization, and style guides.
 
 ## Software Stack
+
 All of our documentation resides on GitHub. Instructions for setting up your GitHub account are located [here](github).
 
 Our documentation is powered by [Docusaurus](https://docusaurus.io) — a documentation platform built on React that utilizes markdown files. Because markdown files are easy to edit, most content changes should be fairly simple. Instructions for setting up your instance of Docusaurus are located [here](docusaurus).
@@ -13,8 +15,9 @@ Our documentation is powered by [Docusaurus](https://docusaurus.io) — a docume
 Another component that we use is [Vercel](https://vercel.com) — a platform for frontend frameworks and static sites. Instructions for setting up your instance of Vercel are located [here](vercel).
 
 ## Documentation Organization
+
 |         Section          |            File Path             |                                                                                                          Description                                                                                                          |
-| :-----: | :-------: | :---------: |
+| :----------------------: | :------------------------------: | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
 |     About Meshtastic     |           `docs/about`           |                                                                                           High level explanation of of Meshtastic.                                                                                            |
 |   Meshtastic Software    |         `docs/software`          |                                                                            Current bulk of documentation running through each Meshtastic project.                                                                             |
 |     Getting Started      |      `docs/getting-started`      |                                                                            Instructions on how to get the Meshtastic firmware onto a users device.                                                                            |
@@ -30,20 +33,27 @@ Another component that we use is [Vercel](https://vercel.com) — a platform for
 Assuming you have the [prerequisites installed](serve-docs-locally#prerequisites), running a local instance of Docusaurus takes three steps:
 
 1. Fork/Clone the [meshtastic/Meshtastic](https://github.com/meshtastic/Meshtastic) repository and navigate to the root directory of the project.
+
 ```bash title="Clone the project"
 git clone https://github.com/meshtastic/Meshtastic.git
 ```
+
 ```bash title="Clone fork of the project"
 git clone https://github.com/[username]/Meshtastic.git
 ```
+
 ```bash title="Change Directory"
 cd ~/Meshtastic
 ```
+
 2. Install Dependencies
+
 ```bash title="Install dependencies using Yarn"
 yarn install
 ```
+
 3. Run Docusaurus
+
 ```bash title="Run node.js server"
 yarn start
 ```
@@ -54,4 +64,5 @@ Before submitting a pull request, it's helpful to run the following command to e
 ```bash title="Build Project"
 yarn build
 ```
+
 :::

docs/developers/maintaining-documentation/serve-docs-locally.md

@@ -3,16 +3,20 @@ id: serve-docs-locally
 title: Setting up Local Documentation
 sidebar_label: Serve Docs Locally
 ---
+
 :::note
 Some things won't display properly like logos or protobufs, this is not cause for concern.
 :::
+
 ## Prerequisites
+
 In order to set up your local environment, you will need to install:
 
 - [Node & Node package manager (NPM)](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm)
 - [Yarn package manager](https://yarnpkg.com/getting-started/install)
 
 ## Getting Started
+
 ### Fork the Meshtastic Repository
 
 Log into Github and create a fork of the [meshtastic/Meshtastic](https://github.com/meshtastic/Meshtastic) repository.
@@ -28,16 +32,19 @@ git clone https://github.com/username/Meshtastic.git
 ```
 
 ### Change directory to Local copy
+
 ```bash title="Change Directory"
 cd ~/Meshtastic
 ```
 
 ### Install Dependencies
+
 ```bash title="Install dependencies using Yarn"
 yarn install
 ```
 
 ### Run Development Server
+
 ```bash title="Run node.js server"
 yarn start
 ```
@@ -48,4 +55,5 @@ Before submitting a pull request, it's helpful to run the following command to e
 ```bash title="Build Project"
 yarn build
 ```
+
 :::

docs/developers/maintaining-documentation/style-guides/settings.md

@@ -3,21 +3,25 @@ id: style-guide-settings
 title: Style Guide - Settings Pages
 sidebar_label: Settings Pages
 ---
+
 ## Overview
+
 Setting pages should focus solely on settings and configuring the device. Hardware is often a related topic, however these pages should not attempt to explain attaching hardware. Mention that hardware is required and link to the appropriate page(s).
 
 ## Layout
 
 ### Overview
+
 This section should describe the group of settings and what they do for the device.
 
 ### Settings
+
 This section starts with an alphabetized table of settings, available values, and default values.
 
 Available values should be listed with tick marks `` surrounding the value.
 
 | Value Type |           Example           |
-| :--------: | :-----: |
+| :--------: | :-------------------------: |
 |  Boolean   |       `true`, `false`       |
 |    List    | `apple`, `banana`, `orange` |
 |   Range    |          `0`-`100`          |
@@ -25,19 +29,24 @@ Available values should be listed with tick marks `` surrounding the value.
 After the table each setting is described in brief detail. If the available options for a setting need additional explanation, a table should be used to describe each available option.
 
 ### Details
+
 If additional details are needed, this optional section can explain that. These would include prerequisites, links to hardware guides, etc.
 
 ### Examples
+
 This optional section can have examples of configurations needed where multiple settings are required to be set up for a specific use case.
 
 ## Example Template
+
 ```markdown title="Template for Settings Pages"
 ---
 id: unique-id
 title: Title for Page
 sidebar_label: Label for Sidebar
 ---
+
 <!--- Allows client-specific tabs to be used --->
+
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
@@ -48,22 +57,27 @@ import TabItem from '@theme/TabItem';
 ## Settings
 
 <!--- Table of settings in alphabetical order --->
+
 |         Setting         |      Acceptable Values      | Default |
-| :-----: | :---------------: | :-----: |
+| :---------------------: | :-------------------------: | :-----: |
 | my_setting_with_options | `apple`, `banana`, `orange` | `apple` |
 
 <!--- H3 for each setting above (alphabetized) --->
+
 ### my_setting_with_options
+
 <!--- description for what the setting does --->
 
 <!--- if the setting has many options, insert a table describing what those variables do --->
+
 |  Value   |          Description           |
-| :---: | :---------: |
+| :------: | :----------------------------: |
 | `apple`  | Description of apple (default) |
 | `banana` |     Description of banana      |
 | `orange` |     Description of orange      |
 
 <!--- Client tabs that were imported above --->
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -88,8 +102,10 @@ import TabItem from '@theme/TabItem';
 </Tabs>
 
 ## Details
+
 <!--- Additional details about the settings IF NEEDED otherwise delete this h2 header --->
 
 ## Examples
+
 <!--- Meant for examples where multiple settings are configured at the same time (WiFi type/SSID/password in a single command). If not needed, delete this h2 header --->
 ```

docs/developers/maintaining-documentation/vercel.md

@@ -3,7 +3,9 @@ id: vercel
 title: Vercel
 sidebar_label: Vercel
 ---
+
 ## Overview
+
 Setting up a Vercel account is an optional step that can help you view your changes to the documentation in a server environment just like the actual docs. This can be helpful to include when submitting a pull request so that developers can review your changes and visually check that things look correct.
 
 ## Set up Vercel account

docs/faq/antenna.md

@@ -3,4 +3,5 @@ id: antenna
 title: FAQs - Antenna
 sidebar_label: Antenna
 ---
+
 ## Overview

docs/faq/channel.md

@@ -3,6 +3,7 @@ id: channel
 title: FAQs - Channel
 sidebar_label: Channel
 ---
+
 ## Overview
 
 ### What is a Meshtastic Channel?

docs/faq/client-android.md

@@ -3,6 +3,7 @@ id: client-android
 title: FAQs - Android
 sidebar_label: Android
 ---
+
 ## Overview
 
 ### What versions of Android does the Meshtastic Android App require?

docs/faq/client-python-cli.md

@@ -3,6 +3,7 @@ id: client-python-cli
 title: FAQs - CLI
 sidebar_label: CLI
 ---
+
 ## Overview
 
 ### How do I find out more about installing (and using) Meshtastic via command line?

docs/faq/client-web.md

@@ -3,6 +3,7 @@ id: client-web
 title: FAQs - Web
 sidebar_label: Web
 ---
+
 ## Overview
 
 ### How do I access the network from my web browser?

docs/faq/mesh.md

@@ -3,4 +3,5 @@ id: mesh
 title: FAQs - Mesh
 sidebar_label: Mesh
 ---
+
 ## Overview

docs/faq/mqtt.md

@@ -3,4 +3,5 @@ id: mqtt
 title: FAQs - MQTT
 sidebar_label: MQTT
 ---
+
 ## Overview

docs/faq/wifi.md

@@ -3,6 +3,7 @@ id: wifi
 title: FAQs - WiFi
 sidebar_label: WiFi
 ---
+
 ## Overview
 
 ### How do I turn on the WiFI radio?

docs/getting-started/clients.md

@@ -3,7 +3,8 @@ id: clients
 title: Meshtastic Clients
 sidebar_label: Meshtastic Clients
 ---
-import { DownloadCard } from '/src/pages/downloads/_components/DownloadCard.tsx'
+
+import { DownloadCard } from '/src/pages/downloads/\_components/DownloadCard.tsx'
 
 ## Overview
 
@@ -20,14 +21,17 @@ To install/upgrade Meshtastic-python manually, see below:
 ```bash title="Install Meshtastic-python (includes CLI)"
 pip install meshtastic
 ```
+
 ```bash title="Upgrade Meshtastic-python (includes CLI)"
 pip install --upgrade meshtastic
 ```
+
 :::note
 Some installations of python may require you to substitute 'pip3' for the 'pip' command.
 :::
 
 ### Mobile Client Downloads
+
 <ul
   style={{
     position: "relative",

docs/getting-started/first-steps.md

@@ -3,6 +3,7 @@ id: first-steps
 title: First Steps
 sidebar_label: First Steps
 ---
+
 ## Overview
 
 Congratulations! Your node should now be running Meshtastic and hopefully you've paired to a client on your mobile device, desktop, or browser.

docs/getting-started/flashing-firmware.md

@@ -3,6 +3,7 @@ id: flashing-firmware
 title: Firmware Flashing Prerequisites
 sidebar_label: Prerequisites
 ---
+
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
@@ -146,7 +147,6 @@ With the latest versions of MacOS, the USB Serial driver is built-in. Do _NOT_ d
 
 :::
 
-
   </TabItem>
   <TabItem value="windows">
 

docs/getting-started/getting_started.md

@@ -4,6 +4,7 @@ title: Getting Started
 sidebar_label: Getting Started
 slug: /getting-started
 ---
+
 import Link from '@docusaurus/Link';
 
 ## What is Meshtastic?

docs/getting-started/meshtastic-flasher.md

@@ -4,6 +4,7 @@ title: Using Meshtastic Flasher
 sidebar_label: Using Meshtastic Flasher
 pagination_next: getting-started/clients
 ---
+
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
@@ -56,6 +57,7 @@ Navigate to `Device Manager > Ports (COM & LPT)`. You should see something like
 </Tabs>
 
 ### Install using `pip`
+
 <Tabs
 groupId="operating-system"
 defaultValue="linux"
@@ -138,9 +140,9 @@ The Meshtastic Flasher will flash the latest firmware to esp32 and nrf52 devices
 
 There are three steps:
 
-* Click the "GET VERSIONS" button to get the versions available (from GitHub).
+- Click the "GET VERSIONS" button to get the versions available (from GitHub).
-* Click the "DETECT DEVICE" button to determine the port and device variant connected.
+- Click the "DETECT DEVICE" button to determine the port and device variant connected.
-* Click the "FLASH" button to flash the version selected, using the port selected to the device.
+- Click the "FLASH" button to flash the version selected, using the port selected to the device.
 
 ## Issues?
 
@@ -152,6 +154,6 @@ The code can be found at the [Meshtastic-gui-installer repo](https://github.com/
 
 The following are known limitations:
 
-* Raspberry Pi is not available, since it is arm-based and there are no pre-built libraries for [PySide](https://wiki.qt.io/Qt_for_Python)
+- Raspberry Pi is not available, since it is arm-based and there are no pre-built libraries for [PySide](https://wiki.qt.io/Qt_for_Python)
-* Ubuntu 20.04 is the version used for testing, it may work with other versions
+- Ubuntu 20.04 is the version used for testing, it may work with other versions
-* see [README](https://github.com/meshtastic/Meshtastic-gui-installer/blob/master/README.md) for more details
+- see [README](https://github.com/meshtastic/Meshtastic-gui-installer/blob/master/README.md) for more details

docs/hardware/antenna/aerials.md

@@ -10,6 +10,7 @@ The stock aerials provided bundled with the t-Beam and other boards are a 'mixed
 Matching an aerial to the transceiver frequency is important, as is choosing an appropriate design.
 
 The aerial's design will affect:
+
 - proportion of the signal which leaves the aerial (efficiency),
 - directions in which it's transmitted,
 - whether it will be affected by horizontal or vertical polarization,
@@ -41,6 +42,6 @@ While the LoRa devices we are using for Meshtastic are relatively low power radi
 
 ## Terminology / references
 
-You could do a lot worse than reading the [Wikipedia entry for Antenna](https://en.wikipedia.org/wiki/Antenna_(radio)), along with the [Wikipedia entry for LoRa](https://en.wikipedia.org/wiki/LoRa).
+You could do a lot worse than reading the [Wikipedia entry for Antenna](<https://en.wikipedia.org/wiki/Antenna_(radio)>), along with the [Wikipedia entry for LoRa](https://en.wikipedia.org/wiki/LoRa).
 
 Instead of listing the terms, let us recommend this superb [tutorial](https://www.youtube.com/watch?v=J3PBL9oLPX8) by Andreas Spiess (the 'guy with the Swiss accent').

docs/hardware/antenna/non-aerial.md

@@ -6,6 +6,7 @@ slug: /hardware/non-aerial
 ---
 
 Unless you're using your devices in a vacuum, with clear line of sight between aerials the following will have an effect:
+
 - Weather (temperature, humidity, and air pressure),
 - Transmission power, bandwidth, spreading factor, and other associated channel factors,
 - Number of nodes within reach of the mesh (affects retries consequent duty cycle hit),
@@ -17,6 +18,7 @@ Unless you're using your devices in a vacuum, with clear line of sight between a
 ### Environmental factors
 
 For a bit of light reading on environmental research:
+
 - [RF attenuation in vegetation](https://web.archive.org/web/20201216041455/https://www.itu.int/dms_pubrec/itu-r/rec/p/R-REC-P.833-9-201609-I!!PDF-E.pdf) (yes really); if you wander through the woods wondering how your RF is bouncing off leaves dependent on their variety, and wind speed … well you do, now.
 - [RF attenuation with various building materials](https://www.ofcom.org.uk/__data/assets/pdf_file/0016/84022/building_materials_and_propagation.pdf).
 - This one by ITU again is very detailed in its [analysis of the drivers of attenuation](https://web.archive.org/web/20211005174833/https://www.itu.int/dms_pubrec/itu-r/rec/p/R-REC-P.2040-1-201507-I!!PDF-E.pdf) (I wasn’t aware that all EMF radiation exhibits reflection / transmission characteristics akin to light hitting a material boundary. So, depending on the angle of incidence, material and the EMF wavelength, it will be reflected and / or transmitted through).

docs/hardware/overview.md

@@ -19,6 +19,7 @@ The following ESP32 devices are supported:
 
 :::caution
 Supported but not encouraged:
+
 - Lilygo TTGO T-Beam - version 0.7 -- Very old, no power management chip, difficulty with GPS module and is freqeuntly confused with other devices.
   :::
 

docs/hardware/supported/lora.md

@@ -21,7 +21,6 @@ sidebar_label: LILYGO® Lora
 
 [<img alt="LILYGO® TTGO Lora V1" src="/img/hardware/lora-v1.png" style={{zoom:'25%'}} />](/img/hardware/lora-v1.png)
 
-
 ## Lora V1.3
 
 - ESP32 - Wifi & Bluetooth
@@ -59,7 +58,6 @@ sidebar_label: LILYGO® Lora
 
 [<img alt="LILYGO® TTGO Lora V2" src="/img/hardware/lora-v2.0.png" style={{zoom:'25%'}} />](/img/hardware/lora-v2.0.png)
 
-
 ## Lora V2.1-1.6
 
 - ESP32 - Wifi & Bluetooth

docs/hardware/supported/tbeam.md

@@ -24,7 +24,6 @@ sidebar_label: LILYGO® T-Beam
 
 [<img alt="LILYGO® TTGO T-Beam Meshtastic" src="/img/hardware/t-beam-meshtastic.png" style={{zoom:'25%'}} />](/img/hardware/t-beam-meshtastic.png)
 
-
 ## T-Beam - v0.7
 
 :::note
@@ -50,7 +49,6 @@ This is an earlier version of the T-Beam board, and due to changes in the design
 [<img alt="LILYGO TTGO T-Beam v0.7" src="/img/hardware/t-beam-v0.7.png" style={{zoom:'25%'}} />](/img/hardware/t-beam-v0.7.png)
 [<img alt="LILYGO TTGO T-Beam v0.7 pinmap" src="/img/hardware/t-beam_v0.7_pinmap.jpeg" style={{zoom:'25%'}} />](/img/hardware/t-beam_v0.7_pinmap.jpeg)
 
-
 ## T-Beam - V1.1
 
 - ESP32 - Wifi & Bluetooth
@@ -71,7 +69,6 @@ This is an earlier version of the T-Beam board, and due to changes in the design
 [<img alt="LILYGO® TTGO T-Beam v1.1" src="/img/hardware/t-beam-v1.1.png" style={{zoom:'35%'}} />](/img/hardware/t-beam-v1.1.png)
 [<img alt="LILYGO® TTGO T-Beam v1.1 pinmap" src="/img/hardware/t-beam_v1.1_pinmap.webp" style={{zoom:'35%'}} />](/img/hardware/t-beam_v1.1_pinmap.webp)
 
-
 ## T-Beam - M8N
 
 - ESP32 - Wifi & Bluetooth

docs/legal/licensing.md

@@ -3,6 +3,7 @@ id: licensing
 title: Licensing & Commercial Projects Usage
 sidebar_label: Licensing
 ---
+
 You are hereby granted a two-year non-exclusive license to use the Meshtastic® logo and trademark on your product/project. No fee is required for this usage, though if you wish keeping $1/unit set-aside so that it can eventually fund [meshtastic.org](https://meshtastic.org) it would be appreciated.
 
 We only ask that you include a line in your support text that states:

docs/legal/overview.md

@@ -4,12 +4,13 @@ title: Legal
 sidebar_label: Legal
 slug: /legal
 ---
+
 ## Disclaimers
 
 This project is still pretty young but moving at a pretty good pace. Not all features are fully implemented in the current alpha builds.
 
-* We don't make these devices and they haven't been tested by UL or the FCC. If you use them, you are experimenting and we can't promise they won't burn your house down ;-)
+- We don't make these devices and they haven't been tested by UL or the FCC. If you use them, you are experimenting and we can't promise they won't burn your house down ;-)
-* The encryption implementation is good but see this list of [caveats](/docs/developers/device/encryption#summary-of-strengthsweaknesses-of-our-current-implementation) to determine risks you might face.
+- The encryption implementation is good but see this list of [caveats](/docs/developers/device/encryption#summary-of-strengthsweaknesses-of-our-current-implementation) to determine risks you might face.
 
 ## Legal FAQ
 

docs/legal/trademark.md

@@ -3,4 +3,5 @@ id: trademark
 title: Trademark Rules & Brand Guidelines
 sidebar_label: Trademark
 ---
+
 Meshtastic® is a registered trademark of Geeksville Industries LLC. Meshtastic software components are released under various licenses, see GitHub for details. No warranty is provided - use at your own risk.

docs/settings/channel-advanced.md

@@ -3,6 +3,7 @@ id: channel-advanced
 title: Channel Settings - Advanced
 sidebar_label: Channel
 ---
+
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
@@ -17,7 +18,7 @@ Most users should not need to change these settings. The default [modem_config](
 ## Settings
 
 |     Setting      |                                         Acceptable Values                                          |            Default            |
-| :-----: | :---------------: | :-----: |
+| :--------------: | :------------------------------------------------------------------------------------------------: | :---------------------------: |
 |    bandwidth     |                `10.4`, `15.6`, `20.8`, `31.25`, `41.7`, `62.5`, `125`, `250`, `500`                |             `125`             |
 |   channel_num    |                                         Depends on Region                                          | Region Channel Number Default |
 |   coding_rate    |                                         `5`, `6`, `7`, `8`                                         |              `5`              |
@@ -276,6 +277,7 @@ Ensure that you are not exceeding your country's regulations.
 ```bash title="Set Default"
 meshtastic --ch-set tx_power 0 --ch-index 0
 ```
+
 ```bash title="Set to 2dBM"
 meshtastic --ch-set tx_power 2 --ch-index 0
 ```

docs/settings/gps.md

@@ -3,6 +3,7 @@ id: gps
 title: GPS Settings
 sidebar_label: GPS
 ---
+
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
@@ -17,7 +18,7 @@ GPS is provided by either the device or your paired phone. More than likely, you
 ## Settings
 
 |         Setting          |                                                                       Acceptable Values                                                                       |     Default     |
-| :-----: | :---------------: | :-----: |
+| :----------------------: | :-----------------------------------------------------------------------------------------------------------------------------------------------------------: | :-------------: |
 |      fixed_position      |                                                                        `true`, `false`                                                                        |     `false`     |
 |      gps_accept_2d       |                                                                        `true`, `false`                                                                        |     `false`     |
 |     gps_attempt_time     |                                                                      `integer` (seconds)                                                                      | `0` (see note)  |
@@ -43,6 +44,7 @@ If you wish to disable any GPS features, see below for more information.
 If set, this node is at a fixed position. The device will generate GPS updates at the regular `gps_update_interval`, but use whatever the last lat/lon/alt it saved for the node. The lat/lon/alt can be set by an internal GPS or with the help of the mobile device's GPS.
 
 #### Set/Unset Fixed Position
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -57,15 +59,19 @@ If set, this node is at a fixed position. The device will generate GPS updates a
 ```bash title="Set Fixed Position - Current Location"
 meshtastic --set fixed_position true
 ```
+
 :::note
 The device will continue to acquire GPS coordinates according to the `gps_update_interval`, but will use the last saved coordinates as its fixed point.
 :::
+
 ```bash title="Set Fixed Position - User Defined"
 meshtastic --setlat 37.8651 --setlon -119.5383
 ```
+
 ```bash title="Unset Fixed Position"
 meshtastic --set fixed_position false
 ```
+
 :::note
 It may take some time to see that the change has taken effect. The GPS location is updated according to the value specified on `gps_update_interval` and the mesh will be notified of the new position in relation to the `position_broadcast_secs` value.
 :::
@@ -98,6 +104,7 @@ Configuring this setting is not yet available for the selected platform. If this
 Determines whether the device should accept 2D GPS fixes. By default, only 3D fixes are accepted (during a 2D fix, altitude values are unreliable and will be excluded).
 
 #### Enable/Disable 2D GPS Fixes
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -112,6 +119,7 @@ Determines whether the device should accept 2D GPS fixes. By default, only 3D fi
 ```bash title="Enable 2D GPS Fixes"
 meshtastic --set gps_accept_2d true
 ```
+
 ```bash title="Disable 2D GPS Fixes"
 meshtastic --set gps_accept_2d false
 ```
@@ -145,6 +153,7 @@ Configuring this setting is not yet available for the selected platform. If this
 Determines the amount of time that a GPS fix should be allowed to take. The default is every 30 seconds. If you increase this value, it will allow the device that amount of time in seconds to acquire coordinates. If the device is unable to get a fix, it will turn off until the next interval. GPS coordinates are updated every [`gps_update_interval`](#gps_update_interval) seconds.
 
 #### Change GPS attempt time frequency
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -159,6 +168,7 @@ Determines the amount of time that a GPS fix should be allowed to take. The defa
 ```bash title="Set GPS attempt time to default (30 seconds)"
 meshtastic --set gps_attempt_time 0
 ```
+
 ```bash title="Set GPS attempt time to 45 seconds"
 meshtastic --set gps_attempt_time 45
 ```
@@ -192,7 +202,7 @@ Configuring this setting is not yet available for the selected platform. If this
 Determines how the GPS coordinates are displayed on the OLED screen.
 
 |     Value     |                                                                                                          Description                                                                                                           |
-| :---: | :---------: |
+| :-----------: | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
 | GpsFormatDec  |                                                                    GPS coordinates are displayed in the normal decimal degrees format: DD.DDDDDD DDD.DDDDDD                                                                    |
 | GpsFormatDMS  |                                 GPS coordinates are displayed in the degrees minutes seconds format: DD°MM'SS"C DDD°MM'SS"C, where C is the compass point representing the locations quadrant                                  |
 | GpsFormatUTM  |                                       GPS coordinates are displayed in Universal Transverse Mercator format: ZZB EEEEEE NNNNNNN, where Z is zone, B is band, E is easting, N is northing                                       |
@@ -201,6 +211,7 @@ Determines how the GPS coordinates are displayed on the OLED screen.
 | GpsFormatOSGR | GPS coordinates are displayed in Ordnance Survey Grid Reference (the National Grid System of the UK). Format: AB EEEEE NNNNN, where A is the east 100k square, B is the north 100k square, E is the easting, N is the northing |
 
 #### Specify GPS Screen Display
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -245,6 +256,7 @@ Configuring this setting is not yet available for the selected platform. If this
 Determines GPS maximum DOP accepted (dilution of precision) Set a rejection threshold for GPS readings based on their precision, relative to the GPS rated accuracy (which is typically ~3m) Solutions above this value will be treated as retryable errors! Useful range is between 1 - 64 (3m - <~200m) By default (if zero), accept all GPS readings
 
 #### Change maximum GPS dilution of precision
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -259,9 +271,11 @@ Determines GPS maximum DOP accepted (dilution of precision) Set a rejection thre
 ```bash title="Set GPS max DOP to default (accept all GPS readings)"
 meshtastic --set gps_max_dop 0
 ```
+
 ```bash title="Set GPS max DOP to 3m"
 meshtastic --set gps_max_dop 1
 ```
+
 ```bash title="Set GPS max DOP to < ~200m"
 meshtastic --set gps_max_dop 64
 ```
@@ -291,6 +305,7 @@ Configuring this setting is not yet available for the selected platform. If this
 </Tabs>
 
 #### Specify GPS Screen Display
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -339,7 +354,7 @@ This is independent of how our location is shared with other devices. For that s
 :::
 
 |        Value        |                                                                                                                                                               Description                                                                                                                                                               |
-| :---: | :---------: |
+| :-----------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
 |     GpsOpUnset      |                                                                                                                                            **Default**: operates the same as `GpsOpMobile`.                                                                                                                                             |
 | ~~GpsOpStationary~~ | Note: This mode was removed, because it is identical go `GpsOpMobile` with a `gps_update_interval` of once per day This node is mostly stationary, we should try to get location only once per day, Once we have that position we should turn the GPS to sleep mode This is the recommended configuration for stationary 'router' nodes |
 |     GpsOpMobile     |                                                                                                                     This node is mobile and we should get GPS position at a rate governed by `gps_update_interval`                                                                                                                      |
@@ -347,6 +362,7 @@ This is independent of how our location is shared with other devices. For that s
 |    GpsOpDisabled    |                                                                                                                         GPS is always turned off - this mode is not recommended - use `GpsOpTimeOnly` instead.                                                                                                                          |
 
 #### Enable/Disable GPS
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -361,9 +377,11 @@ This is independent of how our location is shared with other devices. For that s
 ```bash title="Set GPS to default settings"
 meshtastic --set gps_operation GpsOpUnset
 ```
+
 ```bash title="Set GPS to only be used for time"
 meshtastic --set gps_operation GpsOpTimeOnly
 ```
+
 ```bash title="Disable GPS Completely"
 meshtastic --set gps_operation GpsOpDisabled
 ```
@@ -401,6 +419,7 @@ Configuring this setting is not yet available for the selected platform. If this
 Determines how often should the device should attempt to acquire a GPS position (in seconds). The length of time the device is allowed to attempt to acquire GPS coordinates each interval is set using [`gps_attempt_time`](#gps_attempt_time). The default is every 30 seconds.
 
 #### Specify GPS update interval
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -415,6 +434,7 @@ Determines how often should the device should attempt to acquire a GPS position
 ```bash title="Set GPS update interval to default settings (every 30 seconds)"
 meshtastic --set gps_update_interval 0
 ```
+
 ```bash title="Set GPS update interval to every 45 seconds"
 meshtastic --set gps_update_interval 45
 ```
@@ -448,12 +468,13 @@ Configuring this setting is not yet available for the selected platform. If this
 Determines whether location is shared with other nodes. See more details.
 
 |    Value    |                                                               Description                                                                |
-| :---: | :---------: |
+| :---------: | :--------------------------------------------------------------------------------------------------------------------------------------: |
 |  LocUnset   |                                              **Default**: operates the same as `LocEnabled`                                              |
 | LocEnabled  |                                   The device is sharing its location (or the paired phone's location)                                    |
 | LocDisabled | The device is not sharing its location (if the unit has a GPS it will default to only get time - i.e. [`GpsOpTimeOnly`](#gps_operation)) |
 
 #### Disable Location Sharing
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -504,6 +525,7 @@ How often our position is sent to the mesh (but only if it has changed significa
 The GPS updates will be sent out every `position_broadcast_secs`, with either the actual GPS location, or an empty location if no GPS fix was achieved. This defaults to broadcast every 15 minutes.
 
 #### Specify GPS position broadcast frequency
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -518,6 +540,7 @@ The GPS updates will be sent out every `position_broadcast_secs`, with either th
 ```bash title="Set GPS update interval to default settings (every 15 minutes)"
 meshtastic --set position_broadcast_secs 0
 ```
+
 ```bash title="Set GPS update interval to every 60 seconds"
 meshtastic --set position_broadcast_secs 60
 ```
@@ -559,7 +582,7 @@ As an example, if you configure your radio to use **Long Range / Fast**, if you
 The table below is a summary computed values from the algorithm.
 
 |      Long Name      | Update every x-seconds | Update distance traveled (meters) |
-| :---: | :---------: | :---------: |
+| :-----------------: | :--------------------: | :-------------------------------: |
 |  Long Range / Slow  |           88           |                150                |
 |  Long Range / Fast  |           61           |                144                |
 | Medium Range / Slow |           30           |                41                 |
@@ -572,6 +595,7 @@ A person walking in a straight line will take about 90 seconds to travel 150 met
 :::
 
 #### Enable/Disable Smart Position Broadcast
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -586,6 +610,7 @@ A person walking in a straight line will take about 90 seconds to travel 150 met
 ```bash title="Enable smart position broadcast"
 meshtastic --set position_broadcast_smart true
 ```
+
 ```bash title="Disable smart position broadcast"
 meshtastic --set position_broadcast_smart false
 ```
@@ -619,19 +644,20 @@ Configuring this setting is not yet available for the selected platform. If this
 Bit field of boolean configuration options for POSITION messages (bitwise OR of PositionFlags)
 
 |     Value     |                         Description                         |
-| :---: | :---------: |
+| :-----------: | :---------------------------------------------------------: | ---- |
 | POS_UNDEFINED |                  Required for compilation                   |
 | POS_ALTITUDE  |          Include an altitude value (if available)           |
 |  POS_ALT_MSL  |                    Altitude value is MSL                    |
 |  POS_GEO_SEP  |                 Include geoidal separation                  |
 |    POS_DOP    |   Include the DOP value ; PDOP used by default, see below   |
-| POS_HVDOP | If POS_DOP set, send separate HDOP / VDOP values instead of | PDOP
+|   POS_HVDOP   | If POS_DOP set, send separate HDOP / VDOP values instead of | PDOP |
 |  POS_BATTERY  |                    Include battery level                    |
 | POS_SATINVIEW |           Include number of "satellites in view"            |
 |  POS_SEQ_NOS  |      Include a sequence number incremented per packet       |
 | POS_TIMESTAMP |      Include positional timestamp (from GPS solution)       |
 
 #### Set/Unset Position Flags
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -650,6 +676,7 @@ Include each flag desired from the table above separated by a single space.
 ```bash title="Set Position Flags"
 meshtastic --pos-fields POS_ALTITUDE POS_ALT_MSL
 ```
+
 ```bash title="Unset Position Flags"
 meshtastic --pos-fields POS_UNDEFINED
 ```

docs/settings/ham.md

@@ -3,6 +3,7 @@ id: ham
 title: Licensed (HAM) Operation
 sidebar_label: Licensed (HAM) Operation
 ---
+
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
@@ -19,7 +20,7 @@ This written US only, may or may not be applicable elsewhere.
 Meshtastic can be used by both unlicensed people and licensed operators. If you use Meshtastic with your ham radio license, there are additional privileges and restrictions to consider.
 
 |                           Privileges                            |                         Restrictions                          |
-|:----------:|:------------:|
+| :-------------------------------------------------------------: | :-----------------------------------------------------------: |
 | <ul><li>Additional Power</li><li>Higher gain antennas</li></ul> | <ul><li>Unencrypted</li><li>Identified with your ID</li></ul> |
 
 ## Settings
@@ -37,6 +38,7 @@ By changing these settings, you are self certifying that you are licensed to ope
 :::
 
 #### Set HAM ID
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -81,7 +83,7 @@ Configuring this setting is not yet available for the selected platform. If this
 Toggling `set-ham` changes your device settings in the following ways.
 
 |         Setting          | `set-ham` Default |              Normal Default               |
-| :-----: | :-----------------: | :------------: |
+| :----------------------: | :---------------: | :---------------------------------------: |
 | `is_licensed` (Protobuf) |      `true`       |                  `false`                  |
 |  `long_name` (Protobuf)  |       `id`        |               User Defined                |
 |     `psk` (Protobuf)     |       `""`        | See [Channel Settings - psk](channel#psk) |

docs/settings/misc.md

@@ -3,18 +3,16 @@ id: misc
 title: Miscellaneous Settings
 sidebar_label: Miscellaneous
 ---
+
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-
 ## Overview
 
-
-
 ## Settings
 
 |          Setting          |           Acceptable Values            | Default |
-| :-----: | :---------------: | :-----: |
+| :-----------------------: | :------------------------------------: | :-----: |
 | auto_screen_carousel_secs |          `integer` (seconds)           |   `0`   |
 |     debug_log_enabled     |            `true`, `false`             | `false` |
 |       factory_reset       |            `true`, `false`             | `false` |
@@ -22,7 +20,6 @@ import TabItem from '@theme/TabItem';
 |         hop_limit         |                `0`-`7`                 |   `0`   |
 |      serial_disabled      |            `true`, `false`             | `false` |
 
-
 ### auto_screen_carousel_secs
 
 Automatically toggles to the next page on the screen like a carousel, based the specified interval in seconds. Potentially useful for devices without user buttons.
@@ -43,6 +40,7 @@ Automatically toggles to the next page on the screen like a carousel, based the
 ```bash title="Set auto_screen_carousel_secs to default"
 meshtastic --set auto_screen_carousel_secs 0
 ```
+
 ```bash title="Set auto_screen_carousel_secs to 120 seconds"
 meshtastic --set auto_screen_carousel_secs 120
 ```
@@ -91,6 +89,7 @@ By default we turn off logging as soon as an API client connects (to keep shared
 ```bash title="Enable debug log"
 meshtastic --set debug_log_enabled true
 ```
+
 ```bash title="Disable debug log"
 meshtastic --set debug_log_enabled false
 ```
@@ -184,6 +183,7 @@ If true, radio should not try to be smart about what packets to queue to the pho
 ```bash title="Enable ignore_incoming"
 meshtastic --set ignore_incoming true
 ```
+
 ```bash title="Disable ignore_incoming"
 meshtastic --set ignore_incoming false
 ```
@@ -232,6 +232,7 @@ If set, this will disable the SerialConsole by not initializing the StreamAPI.
 ```bash title="Enable serial"
 meshtastic --set serial_disabled false
 ```
+
 ```bash title="Disable serial"
 meshtastic --set serial_disabled true
 ```
@@ -284,6 +285,7 @@ Meshtastic allows a maximum of 7 hops (this is a limit of the protocol). Setting
 ```bash title="Set hop_limit to default (3 hops)"
 meshtastic --set hop_limit 0
 ```
+
 ```bash title="Set hop_limit to max (7 hops)"
 meshtastic --set hop_limit 7
 ```

docs/settings/overview.md

@@ -4,6 +4,7 @@ title: Device Settings
 sidebar_label: Device Settings
 slug: /settings
 ---
+
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
@@ -32,7 +33,9 @@ Whether you're using the upcoming [web interface](software/web/web-app-software)
 ## Examples
 
 At the bottom of each setting page, examples will be available displaying how to adjust settings using the various platforms available to interface with your device. The examples will look like this:
+
 ### Introducing Examples
+
 <Tabs
 groupId="settings"
 defaultValue="cli"

docs/settings/power.md

@@ -16,7 +16,7 @@ For a description and more information on what exactly all of these mean, please
 ## Settings
 
 |            Setting             |                                                                        Acceptable Values                                                                        |  Default  |
-| :-----: | :---------------: | :-----: |
+| :----------------------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------: | :-------: |
 |         charge_current         | `MAUnset`, `MA100`, `MA190`, `MA280`, `MA360`, `MA450`, `MA550`, `MA630`, `MA700`, `MA780`, `MA880`, `MA960`, `MA1000`, `MA1080`, `MA1160`, `MA1240`, `MA1320`: | `MAUnset` |
 |       is_always_powered        |                                                                         `true`, `false`                                                                         |  `false`  |
 |          is_low_power          |                                                                         `true`, `false`                                                                         |  `false`  |
@@ -65,6 +65,7 @@ Sets the current of the battery charger.
 ```bash title="Unset charge current"
 meshtastic --set  charge_current MAUnset
 ```
+
 ```bash title="Set charge current"
 meshtastic --set  charge_current MA100
 ```
@@ -98,6 +99,7 @@ Configuring this setting is not yet available for the selected platform. If this
 Circumvents the logic block for determining whether the device is powered or not. Useful for devices with finicky ADC issues on the battery sense pins.
 
 #### Enable/Disable is_always_powered
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -112,6 +114,7 @@ Circumvents the logic block for determining whether the device is powered or not
 ```bash title="Enable is_always_powered"
 meshtastic --set is_always_powered true
 ```
+
 ```bash title="Disable is_always_powered"
 meshtastic --set is_always_powered false
 ```
@@ -149,6 +152,7 @@ You do **not** need to set this if you've set `is_router` (it is implied in that
 :::
 
 #### Enable/Disable is_low_power
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -163,6 +167,7 @@ You do **not** need to set this if you've set `is_router` (it is implied in that
 ```bash title="Enable is_low_power"
 meshtastic --set is_low_power true
 ```
+
 ```bash title="Disable is_low_power"
 meshtastic --set is_low_power false
 ```
@@ -195,8 +200,8 @@ Configuring this setting is not yet available for the selected platform. If this
 
 Are we operating as a router. Changes behavior in the following ways: The device will only sleep for critically low battery level (i.e. always tries to stay alive for the mesh) In the future routing decisions will preferentially route packets through nodes with this attribute (because assumed good line of sight).
 
-
 #### Enable/Disable is_router
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -211,6 +216,7 @@ Are we operating as a router. Changes behavior in the following ways: The device
 ```bash title="Enable is_router"
 meshtastic --set is_router true
 ```
+
 ```bash title="Disable is_router"
 meshtastic --set is_router false
 ```
@@ -244,6 +250,7 @@ Configuring this setting is not yet available for the selected platform. If this
 Power management state machine option. See the [power page](/docs/software/other/power) for details. 0 for default of 3600.
 
 #### Configure ls_secs
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -258,6 +265,7 @@ Power management state machine option. See the [power page](/docs/software/other
 ```bash title="Set ls_secs to default (1 hour/3600 seconds)"
 meshtastic --set ls_secs 0
 ```
+
 ```bash title="Set ls_secs to 120 seconds"
 meshtastic --set ls_secs 120
 ```
@@ -291,6 +299,7 @@ Configuring this setting is not yet available for the selected platform. If this
 Power management state machine option. See the [power page](/docs/software/other/power) for details. 0 for default of two hours, use the MAXUINT or 4294967295 to disable.
 
 #### Configure mesh_sds_timeout_secs
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -305,9 +314,11 @@ Power management state machine option. See the [power page](/docs/software/other
 ```bash title="Set mesh_sds_timeout_secs to default (2 hour/7200 seconds)"
 meshtastic --set mesh_sds_timeout_secs 0
 ```
+
 ```bash title="Set mesh_sds_timeout_secs to 120 seconds"
 meshtastic --set mesh_sds_timeout_secs 120
 ```
+
 ```bash title="Disable mesh_sds_timeout_secs (using MAXUINT)"
 meshtastic --set mesh_sds_timeout_secs 4294967295
 ```
@@ -356,6 +367,7 @@ Power management state machine option. See the [power page](/docs/software/other
 ```bash title="Set min_wake_secs to default (10 seconds)"
 meshtastic --set min_wake_secs 0
 ```
+
 ```bash title="Set min_wake_secs to 120 seconds"
 meshtastic --set min_wake_secs 120
 ```
@@ -389,6 +401,7 @@ Configuring this setting is not yet available for the selected platform. If this
 If non-zero, the device will fully power off this many seconds after external power is removed.
 
 #### Enable/Disable on_battery_shutdown_after_secs
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -403,6 +416,7 @@ If non-zero, the device will fully power off this many seconds after external po
 ```bash title="Disable on_battery_shutdown_after_secs"
 meshtastic --set on_battery_shutdown_after_secs 0
 ```
+
 ```bash title="Set device to shutdown after 120 seconds on battery"
 meshtastic --set on_battery_shutdown_after_secs 120
 ```
@@ -436,6 +450,7 @@ Configuring this setting is not yet available for the selected platform. If this
 Power management state machine option. See the [power page](/docs/software/other/power) for details. 0 for default of two hours, use the MAXUINT or 4294967295 to disable.
 
 #### Enable/Disable phone_sds_timeout_sec
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -450,9 +465,11 @@ Power management state machine option. See the [power page](/docs/software/other
 ```bash title="Set phone_sds_timeout_sec to default (2 hours)"
 meshtastic --set phone_sds_timeout_sec 0
 ```
+
 ```bash title="Disable phone_sds_timeout_sec"
 meshtastic --set phone_sds_timeout_sec 4294967295
 ```
+
 ```bash title="Set phone_sds_timeout_sec to 120 seconds"
 meshtastic --set phone_sds_timeout_sec 120
 ```
@@ -501,6 +518,7 @@ Power management state machine option. See the [power page](/docs/software/other
 ```bash title="Set phone_timeout_secs to default (15 minutes)"
 meshtastic --set phone_timeout_secs 0
 ```
+
 ```bash title="Set phone_timeout_secs to 120 seconds"
 meshtastic --set phone_timeout_secs 120
 ```
@@ -549,6 +567,7 @@ Power management state machine option. See the [power page](/docs/software/other
 ```bash title="Set screen_on_secs to default (1 minute)"
 meshtastic --set screen_on_secs 0
 ```
+
 ```bash title="Set screen_on_secs to 120 seconds"
 meshtastic --set screen_on_secs 120
 ```
@@ -597,6 +616,7 @@ Power management state machine option. See the [power page](/docs/software/other
 ```bash title="Set sds_secs to default (1 year)"
 meshtastic --set sds_secs 0
 ```
+
 ```bash title="Set sds_secs to 120 seconds"
 meshtastic --set sds_secs 120
 ```
@@ -645,6 +665,7 @@ This sets how often to send the database of node owner information with other no
 ```bash title="Set send_owner_interval to default (every 4 network pings)"
 meshtastic --set send_owner_interval 0
 ```
+
 ```bash title="Set send_owner_interval to every 10 network pings"
 meshtastic --set send_owner_interval 10
 ```
@@ -680,6 +701,7 @@ For instance the default interval of 4 will send the node owner information for
 Wait number of seconds for Bluetooth - Power management state machine option. See the [power page](/docs/software/other/power) for details. 0 for default of 1 minute.
 
 #### Configure wait_bluetooth_secs
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -694,6 +716,7 @@ Wait number of seconds for Bluetooth - Power management state machine option. Se
 ```bash title="Set wait_bluetooth_secs to default (60 seconds)"
 meshtastic --set wait_bluetooth_secs 0
 ```
+
 ```bash title="Set wait_bluetooth_secs to 120 seconds"
 meshtastic --set wait_bluetooth_secs 120
 ```

docs/settings/router.md

@@ -3,18 +3,16 @@ id: router
 title: Router Settings
 sidebar_label: Router
 ---
+
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-
 ## Overview
 
-
-
 ## Settings
 
 |  Setting  | Acceptable Values | Default |
-| :-----: | :---------------: | :-----: |
+| :-------: | :---------------: | :-----: |
 | is_router |  `true`, `false`  | `false` |
 
 ### is_router
@@ -22,6 +20,7 @@ import TabItem from '@theme/TabItem';
 Are we operating as a router. Changes behavior in the following ways: The device will only sleep for critically low battery level (i.e. always tries to stay alive for the mesh) In the future routing decisions will preferentially route packets through nodes with this attribute (because assumed good line of sight)
 
 #### Enable/Disable router mode
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -36,6 +35,7 @@ Are we operating as a router. Changes behavior in the following ways: The device
 ```bash title="Enable router mode"
 meshtastic --set is_router true
 ```
+
 ```bash title="Disable router mode"
 meshtastic --set is_router false
 ```
@@ -64,13 +64,12 @@ Configuring this setting is not yet available for the selected platform. If this
   </TabItem>
 </Tabs>
 
-
 ## Details
 
 Toggling `is_router` changes your device settings in the following ways.
 
 |          Setting          | `is_router` Default | Normal Default |
-| :-----: | :-----------------: | :------------: |
+| :-----------------------: | :-----------------: | :------------: |
 |   `send_owner_interval`   |          2          |       4        |
 | `position_broadcast_secs` |      12 hours       |   15 minutes   |
 |   `wait_bluetooth_secs`   |          1          |       60       |
@@ -79,5 +78,7 @@ Toggling `is_router` changes your device settings in the following ways.
 |         `ls_secs`         |        1 day        |   5 minutes    |
 
 ### Altered Behaviors
+
 #### Screen Wake
+
 #### Bluetooth

docs/settings/wifi.md

@@ -3,6 +3,7 @@ id: wifi
 title: WiFi Settings
 sidebar_label: WiFi
 ---
+
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
@@ -25,7 +26,7 @@ The first time your device restarts after enabling the WiFi access point, it wil
 ## Settings
 
 |    Setting    | Acceptable Values | Default |
-| :-----: | :---------------: | :-----: |
+| :-----------: | :---------------: | :-----: |
 | wifi_ap_mode  |  `true`, `false`  | `false` |
 | wifi_password |      string       |  `""`   |
 |   wifi_ssid   |      string       |  `""`   |
@@ -39,6 +40,7 @@ The first time your device restarts after enabling the WiFi access point, it wil
 A boolean value that toggles the [Software Access Point](#software-access-point)
 
 #### Enable/Disable Software Access Point
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -53,6 +55,7 @@ A boolean value that toggles the [Software Access Point](#software-access-point)
 ```bash title="Enable SoftAP"
 meshtastic --set wifi_ap_mode true
 ```
+
 ```bash title="Disable SoftAP"
 meshtastic --set wifi_ap_mode false
 ```
@@ -99,6 +102,7 @@ In [SoftAP](#software-access-point) mode, this is the password to access your de
 ```bash title="Set WiFi password"
 meshtastic --set wifi_password mypassword
 ```
+
 ```bash title="Set WiFi password (with spaces)"
 meshtastic --set wifi_password "my password"
 ```
@@ -145,9 +149,11 @@ In [SoftAP](#software-access-point) mode, this is the SSID broadcast to access y
 ```bash title="Set WiFi network"
 meshtastic --set wifi_ssid mynetwork
 ```
+
 ```bash title="Set WiFi network (with spaces)"
 meshtastic --set wifi_ssid "my network"
 ```
+
   </TabItem>
   <TabItem value="android">
 
@@ -194,10 +200,10 @@ You should then be able to connect to the node using either the displayed IP add
 
 You can also enable the SoftAP by following these directions:
 
-* Hold down the user button
+- Hold down the user button
-* Press and release the reset button
+- Press and release the reset button
-* Count to two
+- Count to two
-* Let go of the user button
+- Let go of the user button
 
 This will reboot the device with the SSID set to `meshtasticAdmin` and the password set to `12345678`. Using the Force SoftAP method, once you reboot, the SoftAP will be turned off.
 
@@ -236,6 +242,7 @@ To disable WiFi completely, set `wifi_ap_mode` to `false`, and both `wifi_ssid`
 ## Examples
 
 ### Enable WiFi (as client)
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -253,9 +260,11 @@ To disable WiFi completely, set `wifi_ap_mode` to `false`, and both `wifi_ssid`
 
 :::note
 If your `wifi_ssid` or `wifi_password` contain spaces, be sure to put quotation marks around the whole thing:
+
 ```bash title="Example with spaces"
 meshtastic --set wifi_ssid "my wifi ssid" --set wifi_password "my wifi password"
 ```
+
 :::
 </TabItem>
 <TabItem value="android">
@@ -284,6 +293,7 @@ Configuring this setting is not yet available for the selected platform. If this
 In the above example, the device will join a network with the SSID `mywifissid` and the password `mywifipassword`.
 
 ### Enable WiFi (as SoftAP)
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -301,13 +311,13 @@ In the above example, the device will join a network with the SSID `mywifissid`
 
 :::note
 If your `wifi_ssid` or `wifi_password` contain spaces, be sure to put quotation marks around the whole thing:
+
 ```bash title="Example with spaces"
 meshtastic --set wifi_ssid "my wifi ssid" --set wifi_password "my wifi password"
 ```
+
 :::
 
-
-
   </TabItem>
   <TabItem value="android">
 
@@ -335,6 +345,7 @@ Configuring this setting is not yet available for the selected platform. If this
 In the above example, the device will broadcast a network with the SSID `mywifissid` and the password `mywifipassword`.
 
 ### Disable WiFi Completely
+
 <Tabs
 groupId="settings"
 defaultValue="cli"
@@ -350,7 +361,6 @@ In the above example, the device will broadcast a network with the SSID `mywifis
 meshtastic --set wifi_ap_mode false --set wifi_ssid "" --set wifi_password ""
 ```
 
-
   </TabItem>
   <TabItem value="android">
 

docs/software/community/go.md

@@ -44,5 +44,6 @@ GLOBAL OPTIONS:
    --help, -h              show help (default: false)
    --version, -v           print the version (default: false)
 ```
+
 Further information is available on the project's GitHub [Readme.md](https://github.com/lmatte7/meshtastic-go/blob/main/README.md).
 The latest executables can be downloaded from [GitHub](https://github.com/lmatte7/meshtastic-go/releases/latest).

docs/software/community/overview.md

@@ -7,8 +7,9 @@ sidebar_label: Community apps
 The Meshtastic ecosystem is highly extensible, and a number of community projects have been made to fit different people's needs. If you wish to create your own application or module, please read the information in the developers section, and tell us about your project on the forum.
 
 Current community projects:
- * [Meshtastic module for ATAK](/docs/software/community/community-atak) (Android Team Awareness Kit)
+
- * [PyGUI](/docs/software/community/community-pygui) - Platform independent graphical user interface for Meshtastic devices
+- [Meshtastic module for ATAK](/docs/software/community/community-atak) (Android Team Awareness Kit)
- * [Go CLI](/docs/software/community/community-go) - A command line interface using Go that requires no pre-requisites to be installed
+- [PyGUI](/docs/software/community/community-pygui) - Platform independent graphical user interface for Meshtastic devices
+- [Go CLI](/docs/software/community/community-go) - A command line interface using Go that requires no pre-requisites to be installed
 
 Support for these projects should be sought from their respective authors.

docs/software/device/critical-faults.md

@@ -11,7 +11,7 @@ This table is derived from the [protobufs](/docs/developers/protobufs/api#critic
 :::
 
 | Name                | Number | Description                                                                                                             |
-| ---- | ------ | ----------- |
+| ------------------- | ------ | ----------------------------------------------------------------------------------------------------------------------- |
 | TxWatchdog          | 1      | A software bug was detected while trying to send LoRa                                                                   |
 | SleepEnterWait      | 2      | A software bug was detected on entry to sleep                                                                           |
 | NoRadio             | 3      | No LoRa radio hardware could be found                                                                                   |

docs/software/device/ham.md

@@ -4,6 +4,7 @@ title: Licensed (HAM) Operation
 sidebar_label: Licensed (HAM) Operation
 slug: /software/device/ham
 ---
+
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
@@ -17,13 +18,13 @@ Having a ham radio license grants you addition privilages and restrictions.
 
 # Additional privilages
 
-* Additional power
+- Additional power
-* Higher gain antennas
+- Higher gain antennas
 
 # Restrictions
 
-* Unencrypted
+- Unencrypted
-* Identified with your ID
+- Identified with your ID
 
 # Let's do it!
 

docs/software/device/power.md

@@ -11,26 +11,26 @@ Long battery life is one of the main goals of this project. Based on initial mea
 From lower to higher power consumption.
 
 - Super-Deep-Sleep (SDS) - Everything is off, CPU, radio, Bluetooth, and GPS. It only wakes due to timer or button press. We enter this mode only after no radio comms for a few hours - used to put the device into what is effectively "off" mode.
-  * onEntry: setBluetoothOn(false), call doDeepSleep
+  - onEntry: setBluetoothOn(false), call doDeepSleep
-  * onExit: (standard bootup code, starts in DARK)
+  - onExit: (standard bootup code, starts in DARK)
 - Deep-Sleep (DS) - CPU is off, radio is on, Bluetooth and GPS are off. Note: This mode is never used currently, because it only saves 1.5mA vs Light-Sleep - (Not currently used).
 - Light-Sleep (LS) - CPU is suspended (RAM stays alive), radio is on, Bluetooth is off, and GPS is off. Note: currently GPS is not turned off during light sleep, but there is a TODO item to fix this.
-  * NOTE: On NRF52 platforms (because CPU current draw is so low), light-sleep state is never used.  
+  - NOTE: On NRF52 platforms (because CPU current draw is so low), light-sleep state is never used.
-  * onEntry: setBluetoothOn(false), setGPSPower(false), doLightSleep()
+  - onEntry: setBluetoothOn(false), setGPSPower(false), doLightSleep()
-  * onIdle: (if we wake because our led blink timer has expired) blink the led then go back to sleep until we sleep for ls_secs
+  - onIdle: (if we wake because our led blink timer has expired) blink the led then go back to sleep until we sleep for ls_secs
-  * onExit: setGPSPower(true), start trying to get GPS lock: gps.startLock(), once lock arrives service.sendPosition(BROADCAST)
+  - onExit: setGPSPower(true), start trying to get GPS lock: gps.startLock(), once lock arrives service.sendPosition(BROADCAST)
 - No Bluetooth (NB) - CPU is running, radio is on, GPS is on, Bluetooth is off, and screen is off.
-  * onEntry: setBluetoothOn(false)
+  - onEntry: setBluetoothOn(false)
-  * onExit:
+  - onExit:
 - Running Dark (DARK) - Everything is on except screen.
-  * onEntry: setBluetoothOn(true)
+  - onEntry: setBluetoothOn(true)
-  * onExit:
+  - onExit:
 - Serial API usage (SERIAL) - Screen is on, device doesn't sleep, and Bluetooth is off.
-  * onEntry: setBluetooth off, screen on
+  - onEntry: setBluetooth off, screen on
-  * onExit:
+  - onExit:
 - Full On (ON) - Everything is on, can eventually timeout and transition to a lower power state.
-  * onEntry: setBluetoothOn(true), screen.setOn(true)
+  - onEntry: setBluetoothOn(true), screen.setOn(true)
-  * onExit: screen->setOn(false)
+  - onExit: screen->setOn(false)
 - Has Power (POWER) - Screen is on, device doesn't sleep, Bluetooth on, and will stay in this state as long as we have power.
-  * onEntry: setBluetooth off, screen on
+  - onEntry: setBluetooth off, screen on
-  * onExit:
+  - onExit:

docs/software/ios/development.md

@@ -16,5 +16,5 @@ An alpha MacOS application is available in the beta TestFlight app for MacOS cur
 
 Code from two previous community projects is also available.
 
-* https://github.com/jeksys/Meshtastic-iOS
+- https://github.com/jeksys/Meshtastic-iOS
-* https://github.com/thepoweroftwo/meshtastic-ios
+- https://github.com/thepoweroftwo/meshtastic-ios

docs/software/js/connecting.md

@@ -4,24 +4,21 @@ title: Connecting to a device
 sidebar_label: Connecting
 ---
 
-
-
 ```tsx
-import type React from 'React';
+import type React from "React";
 
-import { IHTTPConnection } from '@meshtastic/meshtasticjs';
+import { IHTTPConnection } from "@meshtastic/meshtasticjs";
 
 export const Connection = (): JSX.Element => {
   const connection = new IHTTPConnection();
 
   const connect = (): void => {
     void connection.connect({
-        address: '10.0.0.10',
+      address: "10.0.0.10",
       fetchInterval: 3000,
     });
-  }
+  };
 
   return <button onClick={connect}>Connect Bluetooth</button>;
 };
-
 ```

docs/software/js/http-api.md

@@ -27,9 +27,13 @@ const connection = client.createHTTPConnection();
 connection.connect("192.168.x.x");
 
 const restartDevice: Promise<void> = connection.restartDevice();
-const getStatistics: Promise<void | Types.WebSPIFFSResponse> = connection.getStatistics();
+const getStatistics: Promise<void | Types.WebSPIFFSResponse> =
-const getNetworks: Promise<void | Types.WebNetworkResponse> = connection.getNetworks();
+  connection.getStatistics();
-const getSPIFFS: Promise<void | Types.WebSPIFFSResponse> = connection.getSPIFFS();
+const getNetworks: Promise<void | Types.WebNetworkResponse> =
-const deleteSPIFFS: Promise<void | Types.WebSPIFFSResponse> = connection.deleteSPIFFS();
+  connection.getNetworks();
+const getSPIFFS: Promise<void | Types.WebSPIFFSResponse> =
+  connection.getSPIFFS();
+const deleteSPIFFS: Promise<void | Types.WebSPIFFSResponse> =
+  connection.deleteSPIFFS();
 const blinkLED: Promise<void | any> = connection.blinkLED();
 ```

docs/software/modules/modules.md

@@ -7,11 +7,13 @@ sidebar_label: Overview
 There are a number of modules that have been integrated into the device firmware. These can be turned on using the Meshtastic python command line program. Please note that these modules require the device to be rebooted once they have been enabled for them to start running.
 
 These modules are currently integrated into the firmware:
-* Range test - Allows automated testing of communication range of nodes
+
-* External notifications - Allows a speaker, LED or other device to indicate when a message has been received
+- Range test - Allows automated testing of communication range of nodes
-* Canned messages - Device can be used without the phone to send a message by choosing a predefined text
+- External notifications - Allows a speaker, LED or other device to indicate when a message has been received
-* Serial - Allows messages to be sent across the mesh by sending strings across a serial port
+- Canned messages - Device can be used without the phone to send a message by choosing a predefined text
+- Serial - Allows messages to be sent across the mesh by sending strings across a serial port
 
 These modules are currently in development:
-* Store and forward - Allows a node to store messages and resend them to nodes that have intermittent connection to the mesh
+
-* Environment measurement - Allows a node to measure it's local environment and report across the mesh
+- Store and forward - Allows a node to store messages and resend them to nodes that have intermittent connection to the mesh
+- Environment measurement - Allows a node to measure it's local environment and report across the mesh

docs/software/other/esp32-arduino-build.md

@@ -16,6 +16,7 @@ sudo pip install --upgrade pip
 git clone https://github.com/meshtastic/esp32-arduino-lib-builder
 cd esp32-arduino-lib-builder
 ```
+
 Install esp-idf (needed if you want to `make menuconfig`, `build.sh` will install it automatically if needed):
 
 ```bash

docs/software/python/standalone.md

@@ -3,6 +3,7 @@ id: python-standalone
 title: Meshtastic-python standalone executable
 sidebar_label: Standalone
 ---
+
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
@@ -10,7 +11,6 @@ There are standalone executable files for Mac, Windows and Ubuntu. A single file
 
 They can be found on the [Releases](https://github.com/meshtastic/Meshtastic-python/releases) page.
 
-
 <Tabs
 groupId="operating-system"
 defaultValue="windows"
@@ -21,15 +21,15 @@ They can be found on the [Releases](https://github.com/meshtastic/Meshtastic-pyt
 ]}>
 <TabItem value="ubuntu">
 
-* Download meshtastic_ubuntu
+- Download meshtastic_ubuntu
 
-* Run the following command to make the file executable and rename it 'meshtastic':
+- Run the following command to make the file executable and rename it 'meshtastic':
 
 ```
 chmod +x meshtastic_ubuntu && mv meshtastic_ubuntu meshtastic
 ```
 
-* To run the cli:
+- To run the cli:
 
 ```
 ./meshtastic
@@ -42,15 +42,15 @@ Copy (or move) this binary somewhere in your path.
 </TabItem>
 <TabItem value="macos">
 
-* Download meshtastic_mac
+- Download meshtastic_mac
 
-* Run the following command to make the file executable and to rename it 'meshtastic':
+- Run the following command to make the file executable and to rename it 'meshtastic':
 
 ```
 chmod +x meshtastic_mac && mv meshtastic_mac meshtastic
 ```
 
-* Try to run it:
+- Try to run it:
 
 ```
 ./meshtastic
@@ -61,9 +61,9 @@ chmod +x meshtastic_mac && mv meshtastic_mac meshtastic
 "meshtastic" can't be opened because Apple cannot check it for malicious software.
 :::
 
-* To fix, go into "System Preferences", "Security & Privacy", "General" tab, and click on the "Allow Anyway" button.
+- To fix, go into "System Preferences", "Security & Privacy", "General" tab, and click on the "Allow Anyway" button.
 
-* Try to run it again:
+- Try to run it again:
 
 ```
 ./meshtastic
@@ -75,7 +75,7 @@ You may get a dialog that says:
 Click "Open".
 :::
 
-* Now when you want to run it, you can simply run:
+- Now when you want to run it, you can simply run:
 
 ```
 ./meshtastic
@@ -88,11 +88,11 @@ Copy (or move) this binary somewhere in your path.
 </TabItem>
 <TabItem value="windows">
 
-* Download meshtastic_windows
+- Download meshtastic_windows
 
-* Rename to meshtastic.exe
+- Rename to meshtastic.exe
 
-* To run, open a windows command prompt, navigate to the location of the executable and run:
+- To run, open a windows command prompt, navigate to the location of the executable and run:
 
 ```
 meshtastic.exe

docs/software/python/using_library.md

@@ -5,6 +5,7 @@ sidebar_label: Using the meshtastic Python library
 ---
 
 An example using Python 3 code to send a message to the mesh, get and set a radio configuration preference:
+
 ```python
 import meshtastic
 import meshtastic.serial_interface
@@ -32,6 +33,7 @@ interface.close()
 ```
 
 Another example using Python 3 code to send a message to the mesh when WiFi is enabled:
+
 ```python
 import time
 import meshtastic
@@ -55,8 +57,8 @@ interface.close()
 
 Note: Be sure to change the IP address in the code above to a valid IP address for your setup.
 
-
 You can get and update settings like this:
+
 ```python
 import meshtastic
 import meshtastic.serial_interface
@@ -71,7 +73,6 @@ ourNode.writeConfig()
 interface.close()
 ```
 
-
 For the rough notes/implementation plan see [TODO](https://github.com/meshtastic/Meshtastic-python/blob/master/TODO.md). See the API for full details of how to use the library.
 
 ## A note to developers of this lib
@@ -79,6 +80,7 @@ For the rough notes/implementation plan see [TODO](https://github.com/meshtastic
 We use the visual-studio-code default python formatting conventions (autopep8). So if you use that IDE you should be able to use "Format Document" and not generate unrelated diffs. If you use some other editor, please don't change formatting on lines you haven't changed.
 
 If you need to build a new release you'll need:
+
 ```bash title="Command"
 apt install pandoc
 sudo pip3 install markdown pandoc webencodings pyparsing twine autopep8

docs/software/web/development.md

@@ -4,7 +4,6 @@ title: Information for developers of the web interface
 sidebar_label: Development
 ---
 
-
 ## Considerations
 
 We have a total of 458,752 bytes (448KB) available on the SPIFFS (Serial Peripheral Interface Flash File System) -- the on-board storage of the ESP32. Of that space, let's not use more than half of that (224KB) in order to leave space for other uses.
@@ -17,9 +16,9 @@ Static files can be placed in the /data folder. All files should be compressed i
 
 As an example, this would mean we will have files such as:
 
-* style.css.gz
+- style.css.gz
-* meshtastic.js.gz
+- meshtastic.js.gz
-* meshtasticlogo.png.gz
+- meshtasticlogo.png.gz
 
 Unless otherwise stated, files in the `/data` folder of the source code will be stored in `/static` on the device.
 
@@ -41,8 +40,8 @@ If a file is uploaded in a .gz format, the .gz extension will be stripped prior
 
 An experimental file system browser with upload and delete capability is available by going to either:
 
-* http://meshtastic.local/static
+- http://meshtastic.local/static
-* https://meshtastic.local/static
+- https://meshtastic.local/static
 
 There are known issues with uploading files with large file sizes.
 

package.json

@@ -8,7 +8,8 @@
     "start": "docusaurus start",
     "build": "docusaurus build",
     "serve": "docusaurus serve",
-    "clear": "docusaurus clear"
+    "clear": "docusaurus clear",
+    "format": "prettier --write 'docs/**/*.md'"
   },
   "dependencies": {
     "@docusaurus/core": "^2.0.0-beta.17",
@@ -37,6 +38,7 @@
     "@tsconfig/docusaurus": "^1.0.4",
     "@types/node": "^17.0.21",
     "@types/w3c-web-serial": "^1.0.2",
+    "prettier": "^2.5.1",
     "typescript": "^4.6.2"
   }
 }

yarn.lock

@@ -5930,6 +5930,11 @@ prepend-http@^2.0.0:
   resolved "https://registry.yarnpkg.com/prepend-http/-/prepend-http-2.0.0.tgz#e92434bfa5ea8c19f41cdfd401d741a3c819d897"
   integrity sha1-6SQ0v6XqjBn0HN/UAddBo8gZ2Jc=
 
+prettier@^2.5.1:
+  version "2.5.1"
+  resolved "https://registry.yarnpkg.com/prettier/-/prettier-2.5.1.tgz#fff75fa9d519c54cf0fce328c1017d94546bc56a"
+  integrity sha512-vBZcPRUR5MZJwoyi3ZoyQlc1rXeEck8KgeC9AwwOn+exuxLxq5toTRDTSaVrXHxelDMHy9zlicw8u66yxoSUFg==
+
 pretty-error@^4.0.0:
   version "4.0.0"
   resolved "https://registry.yarnpkg.com/pretty-error/-/pretty-error-4.0.0.tgz#90a703f46dd7234adb46d0f84823e9d1cb8f10d6"