Commit fe4c56c9 authored by Sanjeev's avatar Sanjeev Committed by Jonathan Corbet

Doc: Typos in documentation

No semantic changes.  The next patch in this series will
do the actual changes to sync with NTP current
best practices
Signed-off-by: default avatarSanjeev Gupta <ghane0@gmail.com>
Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
parent e1235e18
...@@ -63,7 +63,7 @@ for instance) is a PPS source too, and if not they should provide the ...@@ -63,7 +63,7 @@ for instance) is a PPS source too, and if not they should provide the
possibility to open another device as PPS source. possibility to open another device as PPS source.
In LinuxPPS the PPS sources are simply char devices usually mapped In LinuxPPS the PPS sources are simply char devices usually mapped
into files /dev/pps0, /dev/pps1, etc.. into files /dev/pps0, /dev/pps1, etc.
PPS with USB to serial devices PPS with USB to serial devices
...@@ -71,7 +71,7 @@ PPS with USB to serial devices ...@@ -71,7 +71,7 @@ PPS with USB to serial devices
It is possible to grab the PPS from an USB to serial device. However, It is possible to grab the PPS from an USB to serial device. However,
you should take into account the latencies and jitter introduced by you should take into account the latencies and jitter introduced by
the USB stack. Users has reported clock instability around +-1ms when the USB stack. Users have reported clock instability around +-1ms when
synchronized with PPS through USB. This isn't suited for time server synchronized with PPS through USB. This isn't suited for time server
synchronization. synchronization.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment