Fix Lists

Fix indentations
Fix ordered lists. Replace `)` with `.`
Replace `*` with `-` to provide clearer distinction from list beginning with bolded text
Remove blank lines (carriage returns)

Author: santaimpersonator

Firmware/readme.md

@@ -2,8 +2,8 @@
 
 This folder contains the Arduino sketches that make up the firmware that runs on the ESP32. Go [here](https://docs.sparkfun.com/SparkFun_RTK_Everywhere_Firmware/firmware_update/#updating-u-blox-firmware) for more information about the firmware that runs the ZED-F9x Receiver.
 
-* **RTK_Surveyor** - The main firmware for the RTK Surveyor
-* **Test Sketches** - Various sketches used in the making of the main firmware. Used internally to verify different features. Reader beware.
+- **RTK_Surveyor** - The main firmware for the RTK Surveyor
+- **Test Sketches** - Various sketches used in the making of the main firmware. Used internally to verify different features. Reader beware.
 
 ## Compilation Instructions
 

Issue_Template.md

@@ -2,9 +2,9 @@
 Describe your issue here. Additionally, screenshots are easy to paste into github.
 
 ### Your workbench
-* What version of RTK firmware are you running? This can be found when the serial menu is opened (also in the settings.txt file, and in the serial output at power up).
-* What radios are you using: Bluetooth, WiFi, and/or ESP-Now? What app are you using to connect over Bluetooth? Are you transmitting NTRIP back to the device?
-* Are there any additional details that may help us help you?
+- What version of RTK firmware are you running? This can be found when the serial menu is opened (also in the settings.txt file, and in the serial output at power up).
+- What radios are you using: Bluetooth, WiFi, and/or ESP-Now? What app are you using to connect over Bluetooth? Are you transmitting NTRIP back to the device?
+- Are there any additional details that may help us help you?
 
 ### Steps to reproduce
 Tell us how to reproduce this issue. Please post any log files from serial output that may have been generated.

docs/accuracy_verification.md

@@ -31,10 +31,10 @@ This is a replication and confirmation of the procedure done by [RTKLibExplorer
 
 The process goes like this:
 
-* Find a local monument
-* Convert the coordinates
-* Take measurements
-* Calculate differences
+- Find a local monument
+- Convert the coordinates
+- Take measurements
+- Calculate differences
 
 ## Get Used to RTK
 
@@ -98,9 +98,9 @@ My respect for the surveying industry grows daily, but that doesn't mean they ar
 
 The SparkFun example monument is at:
 
-* Latitude: 40 05 14.86880 (NAD83 in 2012)
-* Longitude: -105 09 01.68689 (NAD83 in 2012)
-* Elliptical Height: 1613.737 meters (NAD83 in 2012)
+- Latitude: 40 05 14.86880 (NAD83 in 2012)
+- Longitude: -105 09 01.68689 (NAD83 in 2012)
+- Elliptical Height: 1613.737 meters (NAD83 in 2012)
 
 ### Convert NAD83 to Today
 
@@ -135,15 +135,15 @@ Once we enter all the pertinent data, we receive a nice output showing us our mo
 
 The SparkFun example monument is at:
 
-* Latitude: 40 05 14.88667 (WGS84 in 2022)
-* Longitude: -105 09 01.74023 (WGS84 in 2022)
-* Elliptical Height: 1612.873 meters (WGS84 in 2022)
+- Latitude: 40 05 14.88667 (WGS84 in 2022)
+- Longitude: -105 09 01.74023 (WGS84 in 2022)
+- Elliptical Height: 1612.873 meters (WGS84 in 2022)
 
 And in ECEF (this will be handy in a minute):
 
-* X: -1277423.441 m (ECEF in 2022)
-* Y: -4717810.159 m (ECEF in 2022)
-* Z: 4086459.331 m (ECEF in 2022)
+- X: -1277423.441 m (ECEF in 2022)
+- Y: -4717810.159 m (ECEF in 2022)
+- Z: 4086459.331 m (ECEF in 2022)
 
 ### Convert from HH:MM:SS to Decimal
 
@@ -158,9 +158,9 @@ The NGS coordinates are in the hour/minute/second format (ie, 40 05 14.86880). W
 
 The SparkFun example monument is at:
 
-* Latitude: 40.08746852 (WGS84 in 2022)
-* Longitude: -105.15048340 (WGS84 in 2022)
-* Elliptical Height: 1613.737 meters (WGS84 in 2022)
+- Latitude: 40.08746852 (WGS84 in 2022)
+- Longitude: -105.15048340 (WGS84 in 2022)
+- Elliptical Height: 1613.737 meters (WGS84 in 2022)
 
 These are the coordinates we hope to see using SW Maps once we get out into the field. Write down your monument coordinates so that you have some idea of how close your unit is to the ideal in real-time.
 
@@ -261,11 +261,11 @@ Feel free to look at and make a copy of the [SparkFun example](https://docs.goog
 
 ## How do I get 14mm?!
 
-* Use the best equipment. Our mechanical setup was rickety and cheap. Use a surveyor’s bipod setup, with a bubble level, and a prism pole to accurately level the RTK receiver and measure the distance to the monument.
-* Use an antenna that is NGS calibrated to obtain accurate ARPs. The [SparkFun TOP106 antenna](https://www.sparkfun.com/products/17751) has been calibrated and we are in the process of calibrating the RTK Facet and RTK Facet L-Band.
-* Use an accurate base. A temporary or ‘survey-in’ base will not be accurate. The base needs 24 hours of logging with a [PPP analysis](https://learn.sparkfun.com/tutorials/how-to-build-a-diy-gnss-reference-station/all#gather-raw-gnss-data).
-* Be within 10km of your base. A baseline that is more than 10km will introduce inaccuracies to the RTK fix readings.
-* Correction services are not as accurate as a fixed base. While services such as Skylark and PointPerfect are *convenient*, they use models to estimate the overall isotropic disturbance. A local, fixed base will outperform a correction service.
-* Take an average of points. All the points taken in this example were single snapshots. Average a few seconds' worth of readings.
+- Use the best equipment. Our mechanical setup was rickety and cheap. Use a surveyor’s bipod setup, with a bubble level, and a prism pole to accurately level the RTK receiver and measure the distance to the monument.
+- Use an antenna that is NGS calibrated to obtain accurate ARPs. The [SparkFun TOP106 antenna](https://www.sparkfun.com/products/17751) has been calibrated and we are in the process of calibrating the RTK Facet and RTK Facet L-Band.
+- Use an accurate base. A temporary or ‘survey-in’ base will not be accurate. The base needs 24 hours of logging with a [PPP analysis](https://learn.sparkfun.com/tutorials/how-to-build-a-diy-gnss-reference-station/all#gather-raw-gnss-data).
+- Be within 10km of your base. A baseline that is more than 10km will introduce inaccuracies to the RTK fix readings.
+- Correction services are not as accurate as a fixed base. While services such as Skylark and PointPerfect are *convenient*, they use models to estimate the overall isotropic disturbance. A local, fixed base will outperform a correction service.
+- Take an average of points. All the points taken in this example were single snapshots. Average a few seconds' worth of readings.
 
 This was a lot of fun and a good excuse to get outdoors. We hope you enjoy finding some new points in your world.

docs/configure_with_cli.md

@@ -170,11 +170,11 @@ If the receiver is unable to carry out the action, the following error message i
 
 The following actions shall be implemented.
 
-* APPLY: applies the currently stored settings, rebooting if necessary.
-* SAVE: Saves current settings to NVM
-* EXIT: Exits the command interface
-* REBOOT: Restarts the receiver firmware without applying settings.
-* LIST: List all firmware configuration fields.
+- **`APPLY`**: applies the currently stored settings, rebooting if necessary.
+- **`SAVE`**: Saves current settings to NVM
+- **`EXIT`**: Exits the command interface
+- **`REBOOT`**: Restarts the receiver firmware without applying settings.
+- **`LIST`**: List all firmware configuration fields.
 
 ## LIST Action
 

docs/configure_with_serial.md

@@ -92,21 +92,21 @@ Terminal showing System Status
 
 	> $GNTXT,01,01,05,202447.00,270522,0.380,29,40.090355193,-105.184764700,1560.56,3,0,86*7	1
 
-	* $GNTXT : Start of custom NMEA sentence	
-	* 01 : Number of sentences	
-	* 01 : Sentence number	
-	* 05 : Sentence type ID (5 is for System Status messages)	
-	* 202447.00 : Current hour, minute, second, milliseconds	
-	* 270522 : Current day, month, year	
-	* 0.380 : Current horizontal positional accuracy (m)	
-	* 29 : Satellites in view	
-	* 40.090355193 : Latitude	
-	* -105.184764700 : Longitude	
-	* 1560.56 : Altitude	
-	* 3 : Fix type (0 = no fix, 2 = 2D fix, 3 = 3D fix, 4 = 3D + Dead Reackoning, 5 = Time)	
-	* 0 : Carrier solution (0 = No RTK, 1 = RTK Float, 2 = RTK Fix)
-	* 86 : Battery level (% remaining)
-	* *71 : The completion of the sentence and a [CRC](http://engineeringnotes.blogspot.com/2015/02/generate-crc-for-nmea-strings-arduino.html)
+	- $GNTXT : Start of custom NMEA sentence	
+	- 01 : Number of sentences	
+	- 01 : Sentence number	
+	- 05 : Sentence type ID (5 is for System Status messages)	
+	- 202447.00 : Current hour, minute, second, milliseconds	
+	- 270522 : Current day, month, year	
+	- 0.380 : Current horizontal positional accuracy (m)	
+	- 29 : Satellites in view	
+	- 40.090355193 : Latitude	
+	- -105.184764700 : Longitude	
+	- 1560.56 : Altitude	
+	- 3 : Fix type (0 = no fix, 2 = 2D fix, 3 = 3D fix, 4 = 3D + Dead Reackoning, 5 = Time)	
+	- 0 : Carrier solution (0 = No RTK, 1 = RTK Float, 2 = RTK Fix)
+	- 86 : Battery level (% remaining)
+	- *71 : The completion of the sentence and a [CRC](http://engineeringnotes.blogspot.com/2015/02/generate-crc-for-nmea-strings-arduino.html)
 
 !!! note
 	This is a custom NMEA sentence, can vary in length, and may exceed the [maximum permitted sentence length](https://www.nmea.org/Assets/20160520%20txt%20amendment.pdf) of 61 characters.

docs/configure_with_settings_file.md

@@ -32,15 +32,15 @@ All system configuration can be done by editing the *SFE_[Platform]_Settings_0.t
 
 Keep in mind:
 
-* Not all devices have an SD card slot (ie, RTK Torch) and therefore do not support this configuration method.
-* The settings file contains hundreds of settings.
-* The SD card file "SFE_EVK_Settings_0.txt" is used for Profile 1, SD card file "SFE_EVK_Settings_1.txt" is used for Profile 2, etc.
+- Not all devices have an SD card slot (ie, RTK Torch) and therefore do not support this configuration method.
+- The settings file contains hundreds of settings.
+- The SD card file "SFE_EVK_Settings_0.txt" is used for Profile 1, SD card file "SFE_EVK_Settings_1.txt" is used for Profile 2, etc.
 
 	!!! note
 		The `Settings_0` is for **Profile 1**, `Settings_1` is for **Profile 2**, `Settings_2` is for **Profile 3**...
 
-* When switching to a new profile, the settings file on the SD card with all settings will be created or updated. The internal settings will not be updated until you switch to the profile. Additionally, the file for a particular profile will not be created on the SD card until you switch to that profile.
-* It is not necessary that the settings file on the SD card have all of the settings.
+- When switching to a new profile, the settings file on the SD card with all settings will be created or updated. The internal settings will not be updated until you switch to the profile. Additionally, the file for a particular profile will not be created on the SD card until you switch to that profile.
+- It is not necessary that the settings file on the SD card have all of the settings.
 
 !!! example
 	For example, if you only wanted to set up two wireless networks for **Profile 2**, you could create a file named `SFE_Express_Settings_1.txt` that only contained the following settings:

docs/configure_with_wifi.md

@@ -69,12 +69,12 @@ To get into WiFi configuration follow these steps:
 4. Connect to WiFi network named ‘RTK Config’.
 5. You should be automatically re-directed to the config page but if you are not, open a browser (Chrome is preferred) and type **rtk.local** into the address bar.
 
-<figure markdown>
-![Browser with rtk.local address](./img/WiFi Config/SparkFun RTK WiFi Config - Browser rtk local.png)
-<figcaption markdown>
-Browser with rtk.local
-</figcaption>
-</figure>
+	<figure markdown>
+	![Browser with rtk.local address](./img/WiFi Config/SparkFun RTK WiFi Config - Browser rtk local.png)
+	<figcaption markdown>
+	Browser with rtk.local
+	</figcaption>
+	</figure>
 
 
 ## Connecting to WiFi Network

docs/connecting_bluetooth.md

@@ -53,53 +53,53 @@ Before proceeding, it is recommended to have the mock location provider app alre
 
 To enable **Mock Locations**, *Developer Mode* in Android must be enabled. It is best to google the [most recent procedure for this](https://www.google.com/search?q=how+to+allow+mock+location+on+android) but the following procedure should work:
 
-1) Open Android settings
+1. Open Android settings
 
 	<figure markdown>
 	![alt text](./img/MockLocation/SparkFun RTK Mock Location - Settings.png)
 	<figcaption markdown>
 	</figcaption>
 	</figure>
 
-2) Open *About phone*
+2. Open *About phone*
 
 	<figure markdown>
 	![Build Number box](./img/MockLocation/SparkFun RTK Mock Location - Build Number.png)
 	<figcaption markdown>
 	</figcaption>
 	</figure>
 
-3) Scroll to the bottom and click on *Build number* five or more times. The device will prompt as more taps are required.
+3. Scroll to the bottom and click on *Build number* five or more times. The device will prompt as more taps are required.
 
 Once Developer Mode is enabled:
 
-1) Open Android settings
+1. Open Android settings
 
 	<figure markdown>
 	![alt text](./img/MockLocation/SparkFun RTK Mock Location - Settings.png)
 	<figcaption markdown>
 	</figcaption>
 	</figure>
 
-2) Open *System*
+2. Open *System*
 
 	<figure markdown>
 	![Develop options menu](./img/MockLocation/SparkFun RTK Mock Location - Developer Options.png)
 	<figcaption markdown>
 	</figcaption>
 	</figure>
 
-3) Open *Developer options*
+3. Open *Developer options*
 
 	<figure markdown>
 	![Mock Location button](./img/MockLocation/SparkFun RTK Mock Location - Select Mock Location App.png)
 	<figcaption markdown>
 	</figcaption>
 	</figure>
 
-4) Scroll all the way to the bottom of a very long list of developer options.
+4. Scroll all the way to the bottom of a very long list of developer options.
 
-5) Select the app to use for Mock Location. This is usually [Lefebure](gis_software_android.md/#lefebure) or [GNSS Master](gis_software_android.md/#gnss-master) but can be tailored as needed.
+5. Select the app to use for Mock Location. This is usually [Lefebure](gis_software_android.md/#lefebure) or [GNSS Master](gis_software_android.md/#gnss-master) but can be tailored as needed.
 
 ## Apple iOS
 

docs/correction_sources.md

@@ -22,18 +22,18 @@ To get millimeter accuracy we need to provide the RTK unit with correction value
 
 These companies set up a large number of reference stations that cover entire regions and countries, but charge a monthly fee. They are often easy to use but can be expensive.
 
-* [PointPerfect](https://docs.sparkfun.com/SparkFun_RTK_Everywhere_Firmware/quickstart-torch/#pointperfect-corrections) ($8/month) - US, EU, as well as parts of Australia, Brazil, and South Korea.
+- [PointPerfect](https://docs.sparkfun.com/SparkFun_RTK_Everywhere_Firmware/quickstart-torch/#pointperfect-corrections) ($8/month) - US, EU, as well as parts of Australia, Brazil, and South Korea.
 
 	!!! note
 		 This is an SSR service.
 
-* [Onocoy](https://console.onocoy.com/explorer) ($25/month) - US, EU, Australia, and many other partial areas
-* [PointOneNav](https://app.pointonenav.com/trial?src=sparkfun) ($50/month) - US, EU, Australia, South Korea
-* [Skylark](https://www.swiftnav.com/skylark) ($29 to $69/month) - US, EU, Japan, Australia
-* [SensorCloud RTK](https://rtk.sensorcloud.com/pricing/) ($100/month) partial US, EU
-* [Premium Positioning](https://www.premium-positioning.com) (~$315/month) partial EU
-* [KeyNetGPS](https://www.keypre.com/KeynetGPS) ($375/month) North Eastern US
-* [Hexagon/Leica](https://hxgnsmartnet.com/en-US) ($500/month) - partial US, EU
+- [Onocoy](https://console.onocoy.com/explorer) ($25/month) - US, EU, Australia, and many other partial areas
+- [PointOneNav](https://app.pointonenav.com/trial?src=sparkfun) ($50/month) - US, EU, Australia, South Korea
+- [Skylark](https://www.swiftnav.com/skylark) ($29 to $69/month) - US, EU, Japan, Australia
+- [SensorCloud RTK](https://rtk.sensorcloud.com/pricing/) ($100/month) partial US, EU
+- [Premium Positioning](https://www.premium-positioning.com) (~$315/month) partial EU
+- [KeyNetGPS](https://www.keypre.com/KeynetGPS) ($375/month) North Eastern US
+- [Hexagon/Leica](https://hxgnsmartnet.com/en-US) ($500/month) - partial US, EU
 
 ## Public Reference Stations
 

docs/correction_transport.md

@@ -91,8 +91,8 @@ Compatibility Icons
 
 The RTK EVK has built-in cellular via a u-blox LARA-R6001D. However, the RTK Everywhere firmware does not yet support cellular. Adding it is on our roadmap. Stay tuned for updates! Meanwhile, we do have a stand-alone EVK code example which will connect to PointPerfect localized distribution via cellular:
 
-	* [EVK example 8_5_PointPerfect_MQTT](https://github.com/sparkfun/SparkFun_RTK_EVK/tree/main/Example_Sketches/8_5_PointPerfect_MQTT)
-	* [EVK example 8_6_PointPerfect_MQTT_WiFi_ETH_Cellular](https://github.com/sparkfun/SparkFun_RTK_EVK/tree/main/Example_Sketches/8_6_PointPerfect_MQTT_WiFi_ETH_Cellular)
+- [EVK example 8_5_PointPerfect_MQTT](https://github.com/sparkfun/SparkFun_RTK_EVK/tree/main/Example_Sketches/8_5_PointPerfect_MQTT)
+- [EVK example 8_6_PointPerfect_MQTT_WiFi_ETH_Cellular](https://github.com/sparkfun/SparkFun_RTK_EVK/tree/main/Example_Sketches/8_6_PointPerfect_MQTT_WiFi_ETH_Cellular)
 
 ## L-Band