[Git][NTPsec/ntpsec][master] Reword for clarity, NIST guideline conformance, unit replace...

[Matt Selsky]

Matt Selsky pushed to branch master at NTPsec / ntpsec


Commits:
78817b73 by Paul Theodoropoulos at 2018-10-20T01:51:56Z
Reword for clarity, NIST guideline conformance, unit replace...

baud to bps, as well as minor text fixes/clarifications

- - - - -


1 changed file:

- docs/driver_nmea.txt


Changes:

=====================================
docs/driver_nmea.txt
=====================================
@@ -24,7 +24,7 @@ The driver expects the receiver to be set up to transmit at least one
 supported sentence every second.
 
 The accuracy depends on the receiver used. Inexpensive GPS models are
-available with a claimed PPS signal accuracy of 1 μs or better relative
+available with a claimed PPS signal accuracy of 1 µs or better relative
 to the broadcast signal. However, in most cases the actual accuracy is
 limited by the precision of the timecode and the latencies of the serial
 interface and operating system.
@@ -103,7 +103,7 @@ Specific GPS sentences and bitrates may be selected by setting bits of the \'mod
 |3      |8        |8    |process +$GPZDA+ or +$GPZDG+
 |7      |128      |0x80 |
 Write the sub-second fraction of the receive time stamp to the clockstat
-file for all recognized NMEA sentences. This can be used to get a useful
+file for all recognized NMEA sentences. This can provide a useful
 value for fudge time2
 *Caveat:* This will fill your clockstat file rather fast. Use it only
 temporarily to get the numbers for the NMEA sentence of your choice.
@@ -118,7 +118,7 @@ linespeed of 9600 bps, which results in the first one received and
 recognized in each cycle being used.  If only specific sentences should
 be recognized, then the mode byte must be chosen to enable only the
 selected ones.  Multiple sentences may be selected by adding their mode
-bit values, but of those enabled still only the first received sentence
+bit values, but of those enabled, only the first received sentence
 in a cycle will be used.  Using more than one sentence per cycle is
 impossible, because
 
@@ -130,13 +130,13 @@ and
 * using more than one sentence per cycle overstuffs the internal data
   filters.
 
-The driver uses 9600 bits per second by default, unless
+The driver uses 9600 bps by default, unless
 NTPsec was built in Classic strict-compatibility mode, in which
-case the old default of 4800bps is used. Faster bitrates can be
+case the old default of 4800 bps is used. Faster bitrates can be
 selected using the +baud+ option.
 
 *Caveat:* Using higher line speeds does not necessarily increase the
-precision of the timing device.  9600 baud is useful to accommodate an
+precision of the timing device.  9600 bps is useful to accommodate an
 amount of data that does not fit into a 1-second cycle at 4800 bps;
 some GPSes (especially when emitting skyview sentences) emit more than
 this.  Any device that is exclusively used for time synchronisation
@@ -189,7 +189,7 @@ http://support.ntp.org/bin/view/Support/ConfiguringNMEARefclocks[Configuring
 NMEA Refclocks] might give further useful hints for specific hardware
 devices that exhibit strange or curious behaviour. Note that it
 describes NTP Classic and the old refclock configuration syntax, and
-assumes the old default speed of 4800 baud.
+assumes the old default speed of 4800 bps.
 
 To make a specific setting, select the corresponding decimal values from
 the mode byte table, add them all together and enter the resulting
@@ -197,7 +197,7 @@ decimal value into the clock configuration line.
 
 == Setting up the Garmin GPS-25XL ==
 
-Switch off all output with by sending it the following string.
+Switch off all output by sending it the following string.
 
 -------------------
 "$PGRMO,,2<cr><lf>"
@@ -252,13 +252,13 @@ switched on by sending the following string.
 +ppspath+ 'filename'::
   Overrides the default PPS-device path.
 +baud+ 'number'::
-  Overrides the default baud rate.
+  Overrides the default baud/bps rate.
 
 == Configuration Example ==
 
 ------------------------------------------------------------------------------
-refclock nmea baud 19200	# All sentences from /dev/gps0 at 19200 baud
-refclock nmea path /dev/ttyUSB0	# All sentences from /dev/ttyUSB0 at 9600 baud
+refclock nmea baud 19200	# All sentences from /dev/gps0 at 19200 bps
+refclock nmea path /dev/ttyUSB0	# All sentences from /dev/ttyUSB0 at 9600 bps
 ------------------------------------------------------------------------------
 
 link:refclock.html[Reference Clock Drivers]



View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/78817b731b5a8082e98c4508f8fe8031383ce437

-- 
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/78817b731b5a8082e98c4508f8fe8031383ce437
You're receiving this email because of your account on gitlab.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/vc/attachments/20181020/c0e339a8/attachment-0001.html>