Skip to content

Commit d4aeec5

Browse files
santaimpersonatorsantaimpersonator
committed
Consolidate <figcaption> elements
Converted multi-line <figcaption> elements into a single-line format
1 parent b056300 commit d4aeec5

File tree

6 files changed

+20
-58
lines changed

6 files changed

+20
-58
lines changed

‎flex_boards/SparkPNT_GNSS_Flex_Module_DAN-F10N/docs/hardware_overview.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -86,9 +86,7 @@
8686
=== "Dimensions"
8787
<article style="text-align: center;" markdown>
8888
[![Board Dimensions](./assets/board_files/dimensions.png){ width="450" }](./assets/board_files/dimensions.png "Click to enlarge")
89-
<figcaption markdown>
90-
Dimensions of the DAN-F10N GNSS Flex module.
91-
</figcaption>
89+
<figcaption markdown>Dimensions of the DAN-F10N GNSS Flex module.</figcaption>
9290
</article>
9391

9492

‎flex_boards/SparkPNT_GNSS_Flex_Module_DAN-F10N/docs/software_overview.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -165,9 +165,7 @@ Before users can connect to the DAN-F10N GNSS Flex module, they will need to spe
165165

166166
<figure markdown>
167167
[![UART Settings in PyGPSClient](./assets/img/hookup_guide/pygpsclient-uart_settings-small.png){ width="400" }](./assets/img/hookup_guide/pygpsclient-uart_settings-small.png "Click to enlarge")
168-
<figcaption markdown>
169-
Specify the settings for the UART port in PyGPSClient.
170-
</figcaption>
168+
<figcaption markdown>Specify the settings for the UART port in PyGPSClient.</figcaption>
171169
</figure>
172170

173171
</div>

‎flex_boards/SparkPNT_GNSS_Flex_Module_LG290P/docs/hardware_overview.md‎

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -83,9 +83,7 @@
8383
=== "Dimensions"
8484
<article style="text-align: center;" markdown>
8585
[![Board Dimensions](./assets/board_files/dimensions.png){ width="450" }](./assets/board_files/dimensions.png "Click to enlarge")
86-
<figcaption markdown>
87-
Dimensions of the LG290P GNSS Flex module.
88-
</figcaption>
86+
<figcaption markdown>Dimensions of the LG290P GNSS Flex module.</figcaption>
8987
</article>
9088

9189

@@ -255,9 +253,7 @@ The LG290P module is a multi-band, multi-constellation GNSS receiver. Below, is
255253

256254
<figure markdown>
257255
[![GNSS frequency bands](https://www.tallysman.com/app/uploads/2021/07/Tallysman-GNSS-Frequencies-v8.0_Chart-1-1024x425.png){ width="800" style="background-color:white"}](https://www.tallysman.com/app/uploads/2021/07/Tallysman-GNSS-Frequencies-v8.0_Chart-1-1024x425.png "Click to enlarge")
258-
<figcaption markdown>
259-
Frequency bands of the global navigation satellite systems. (Source: [Tallysman](https://www.tallysman.com/gnss-constellations-radio-frequencies-and-signals/))
260-
</figcaption>
256+
<figcaption markdown>Frequency bands of the global navigation satellite systems. (Source: [Tallysman](https://www.tallysman.com/gnss-constellations-radio-frequencies-and-signals/))</figcaption>
261257
</figure>
262258

263259

@@ -342,7 +338,7 @@ Frequency bands of the global navigation satellite systems. (Source: [Tallysman]
342338

343339
<div markdown>
344340

345-
The accuracy of the position reported from the LG290P GNSS module, can be improved based upon the correction method being employed. Currently, [RTK](https://en.wikipedia.org/wiki/ Real-time_kinematic_positioning "Real-Time Kinematic") corrections provide the highest level of accuracy; however, users should be aware of certain limitations of the system:
341+
The accuracy of the position reported from the LG290P GNSS module, can be improved based upon the correction method being employed. Currently, [RTK](https://en.wikipedia.org/wiki/Real-time_kinematic_positioning "Real-Time Kinematic") corrections provide the highest level of accuracy; however, users should be aware of certain limitations of the system:
346342

347343
- RTK technique requires real-time correction data from a reference station or network of base stations.
348344
- RTK corrections usually come from RTCM messages that are signal specific *(i.e. an RTK network may only provide corrections for specific signals; only `E5b` and not `E5a`)*.
@@ -485,9 +481,7 @@ Below, are the features that are available from the LG290P GNSS receiver.
485481

486482
<figure markdown>
487483
[![NMEA data structure](./assets/img/hookup_guide/nmea_protocol.png){ width="600" }](./assets/img/hookup_guide/nmea_protocol.png "Click to enlarge")
488-
<figcaption markdown>
489-
The data structure of Quectel messages for the `NMEA` protocol.
490-
</figcaption>
484+
<figcaption markdown>The data structure of Quectel messages for the `NMEA` protocol.</figcaption>
491485
</figure>
492486

493487

‎flex_boards/SparkPNT_GNSS_Flex_Module_LG290P/docs/software_overview.md‎

Lines changed: 8 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -22,9 +22,7 @@ In order to connect to the LG290P properly, users will need USB-to-Serial conver
2222

2323
<figure markdown>
2424
[![Configure UART Settings](./assets/img/hookup_guide/qgnss-uart_settings-button.png){ width="400" }](./assets/img/hookup_guide/qgnss-uart_settings-button.png "Click to enlarge")
25-
<figcaption markdown>
26-
Click the <kbd>:material-cog:</kbd> button to configure the UART settings.
27-
</figcaption>
25+
<figcaption markdown>Click the <kbd>:material-cog:</kbd> button to configure the UART settings.</figcaption>
2826
</figure>
2927

3028

@@ -42,9 +40,7 @@ Before users can connect to the LG290P GNSS Flex module, they will need to speci
4240

4341
<figure markdown>
4442
[![UART Settings in QGNSS](./assets/img/hookup_guide/qgnss-uart_settings.png){ width="400" }](./assets/img/hookup_guide/qgnss-uart_settings.png "Click to enlarge")
45-
<figcaption markdown>
46-
Specify the settings for the UART port in QGNSS.
47-
</figcaption>
43+
<figcaption markdown>Specify the settings for the UART port in QGNSS.</figcaption>
4844
</figure>
4945

5046
</div>
@@ -75,9 +71,7 @@ By default, the UART ports are configured to transmit and receive `NMEA 0183` an
7571

7672
<figure markdown>
7773
[![NMEA data structure](./assets/img/hookup_guide/nmea_protocol.png){ width="600" }](./assets/img/hookup_guide/nmea_protocol.png "Click to enlarge")
78-
<figcaption markdown>
79-
The data structure of Quectel messages for the `NMEA` protocol.
80-
</figcaption>
74+
<figcaption markdown>The data structure of Quectel messages for the `NMEA` protocol.</figcaption>
8175
</figure>
8276

8377

@@ -97,9 +91,7 @@ In the QGNSS software, users can click on the ++"Advance"++ button, at the botto
9791

9892
<figure markdown>
9993
[![NMEA message setting](./assets/img/hookup_guide/qgnss-message_settings.png){ width="600" }](./assets/img/hookup_guide/qgnss-message_settings.png "Click to enlarge")
100-
<figcaption markdown>
101-
The settings for the messages transmitted from the QConsole.
102-
</figcaption>
94+
<figcaption markdown>The settings for the messages transmitted from the QConsole.</figcaption>
10395
</figure>
10496

10597

@@ -109,9 +101,7 @@ The settings for the messages transmitted from the QConsole.
109101

110102
<figure markdown>
111103
[![QConsole Toolbar](./assets/img/hookup_guide/qgnss-toolbar.gif){ width="400" }](./assets/img/hookup_guide/qgnss-toolbar.gif "Click to enlarge")
112-
<figcaption markdown>
113-
++"Right-click"++ on the mouse and select the `Show Tool` option, inside the QConsole.
114-
</figcaption>
104+
<figcaption markdown> ++"Right-click"++ on the mouse and select the `Show Tool` option, inside the QConsole.</figcaption>
115105
</figure>
116106

117107

@@ -129,9 +119,7 @@ The settings for the messages transmitted from the QConsole.
129119

130120
<figure markdown>
131121
[![PQTM demo](./assets/img/hookup_guide/qgnss-pqtm_message.png){ width="400" }](./assets/img/hookup_guide/qgnss-pqtm_message.png "Click to enlarge")
132-
<figcaption markdown>
133-
Example of utilizing the Quectel PQTM messages in the QConsole.
134-
</figcaption>
122+
<figcaption markdown>Example of utilizing the Quectel PQTM messages in the QConsole.</figcaption>
135123
</figure>
136124

137125

@@ -184,9 +172,7 @@ Before users can connect to the LG290P GNSS Flex module, they will need to speci
184172

185173
<figure markdown>
186174
[![UART Settings in PyGPSClient](./assets/img/hookup_guide/pygpsclient-uart_settings-small.png){ width="400" }](./assets/img/hookup_guide/pygpsclient-uart_settings-small.png "Click to enlarge")
187-
<figcaption markdown>
188-
Specify the settings for the UART port in QGNSS.
189-
</figcaption>
175+
<figcaption markdown>Specify the settings for the UART port in QGNSS.</figcaption>
190176
</figure>
191177

192178
</div>
@@ -220,9 +206,7 @@ The [SparkFun LG290P Quadband RTK GNSS Arduino Library](https://github.com/spark
220206

221207
<figure markdown>
222208
[![Library listed in the library manager of the Arduino IDE](./assets/img/hookup_guide/arduino_library.png "Click to enlarge"){ width="400" }](./assets/img/hookup_guide/arduino_library.png)
223-
<figcaption markdown>
224-
SparkFun LG290P Quadband RTK GNSS Arduino Library in the library manager of the Arduino IDE.
225-
</figcaption>
209+
<figcaption markdown>SparkFun LG290P Quadband RTK GNSS Arduino Library in the library manager of the Arduino IDE.</figcaption>
226210
</figure>
227211

228212
</div>

‎flex_boards/SparkPNT_GNSS_Flex_Module_mosaic-X5/docs/gnss_signals.md‎

Lines changed: 5 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -124,9 +124,7 @@ Below, are instructions to configure the mosaic-X5 module to track any of the su
124124

125125
<figure markdown>
126126
[![Enable use of unhealthy satellites](./assets/img/hookup_guide/gnss_signals/health_masks-off.png){ width="400" }](./assets/img/hookup_guide/gnss_signals/health_masks-off.png "Click to enlarge")
127-
<figcaption markdown>
128-
Enabling the tracking and PVT use of satellites (and their signals), which would be considered "unhealthy".
129-
</figcaption>
127+
<figcaption markdown>Enabling the tracking and PVT use of satellites (and their signals), which would be considered "unhealthy".</figcaption>
130128
</figure>
131129

132130
!!! tip
@@ -157,9 +155,7 @@ Through the web interface, users will need to access the advanced settings of th
157155

158156
<figure markdown>
159157
[![Enable signal tracking](./assets/img/hookup_guide/gnss_signals/signal_tracking-all.png)](./assets/img/hookup_guide/gnss_signals/signal_tracking-all.png "Click to enlarge")
160-
<figcaption markdown>
161-
Enabling the tracking of all the signals from all the GNSS constellations.
162-
</figcaption>
158+
<figcaption markdown>Enabling the tracking of all the signals from all the GNSS constellations.</figcaption>
163159
</figure>
164160

165161

@@ -171,9 +167,7 @@ Through the web interface, users will need to access the advanced settings of th
171167

172168
<figure markdown>
173169
[![Enable signal utilization](./assets/img/hookup_guide/gnss_signals/signal_usage-all.png)](./assets/img/hookup_guide/gnss_signals/satellite_usage-all.png "Click to enlarge")
174-
<figcaption markdown>
175-
Enabling the utilization of all the GNSS signals for PVT computations and navigational data outputs.
176-
</figcaption>
170+
<figcaption markdown>Enabling the utilization of all the GNSS signals for PVT computations and navigational data outputs.</figcaption>
177171
</figure>
178172

179173
</article>
@@ -218,9 +212,7 @@ Through the web interface, users will need to access the advanced settings of th
218212

219213
<figure markdown>
220214
[![Enable satellite tracking](./assets/img/hookup_guide/gnss_signals/satellite_tracking-all.png)](./assets/img/hookup_guide/gnss_signals/satellite_tracking-all.png "Click to enlarge")
221-
<figcaption markdown>
222-
Enabling the tracking of all satellites from every GNSS constellations.
223-
</figcaption>
215+
<figcaption markdown>Enabling the tracking of all satellites from every GNSS constellations.</figcaption>
224216
</figure>
225217

226218

@@ -232,9 +224,7 @@ Through the web interface, users will need to access the advanced settings of th
232224

233225
<figure markdown>
234226
[![Enable satellite usage](./assets/img/hookup_guide/gnss_signals/satellite_usage-all.png)](./assets/img/hookup_guide/gnss_signals/satellite_usage-all_expanded.png "Click to enlarge")
235-
<figcaption markdown>
236-
Enabling the utilization of all the satellites from every GNSS constellation.
237-
</figcaption>
227+
<figcaption markdown>Enabling the utilization of all the satellites from every GNSS constellation.</figcaption>
238228
</figure>
239229

240230
</div>

‎flex_boards/SparkPNT_GNSS_Flex_Module_mosaic-X5/docs/hardware_overview.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -300,9 +300,7 @@
300300
=== "Dimensions"
301301
<article style="text-align: center;" markdown>
302302
[![Board Dimensions](./assets/board_files/dimensions.png){ width="450" }](./assets/board_files/dimensions.png "Click to enlarge")
303-
<figcaption markdown>
304-
Dimensions of the mosaic-X5 GNSS Flex module.
305-
</figcaption>
303+
<figcaption markdown>Dimensions of the mosaic-X5 GNSS Flex module.</figcaption>
306304
</article>
307305

308306

0 commit comments

Comments
 (0)