Merge pull request #579 from sparkfun/PC_add_mosaic_docs

More tweaks

Author: PaulZC

docs/configure_with_ethernet_over_usb.md

@@ -110,6 +110,8 @@ The mosaic-X5 configurations web page - Expert Console
 
 _Expert Control_ is so powerful, you may wish to use the _Admin / User Administration_ settings to limit access to the X5's configuration. But be careful that you do not prevent the firmware on the ESP32 from accessing the COM ports!
 
+The [mosaic-X5 Firmware Reference Guide](https://docs.sparkfun.com/SparkFun_RTK_Facet_mosaic/assets/component_documentation/mosaic-X5%20Firmware%20v4.14.0%20Reference%20Guide.pdf) provides more details.
+
 ### Streams
 
 On the mosaic-X5, NMEA and SBF binary messages need to be allocated to _Streams_. Each stream can then be directed to one or more "Connector Descriptors (Cd)". Connector descriptors include: COM1-4 (the UART ports), USB1-2 (additional COM ports on USB), DSK1 (the "internal disk"  which is the SD card), etc..

docs/menu_data_logging.md

@@ -70,7 +70,7 @@ The defaults set the logging interval to 30 seconds and the file duration to 24
 
 If you are familiar with our other RTK products, you may be wondering where the "Log Antenna Reference Position from RTCM 1005/1006" has gone. On RTK Facet mosaic, the mosaic-X5 can log the Rover-Base Position in North-East-Up format via the proprietary RBP ($PSSN,RBP) NMEA message. We believe this trumps the position extracted from RTCM 1005/1006 on ZED-F9P platforms.
 
-It is not possible to log RTCM on the mosaic-X5. Only SBF, RINEX and SBF (binary blocks) can be logged.
+It is not possible to log RTCM on the mosaic-X5. Only NMEA, RINEX and SBF (binary blocks) can be logged.
 
 The RTK Everywhere Firmware does not currently provide a way of configuring the logging of additional SBF binary blocks. There are just so many, managing the menu choices alone would be quite a task. However, it is straightforward to define your own SBF Stream and point it at DSK1 for logging. Please see [Custom Configuration](./configure_with_ethernet_over_usb.md#custom-configuration) for more details.