From fe4c56c98c1338c0b8b69d08ccf5694bf8e1dcaf Mon Sep 17 00:00:00 2001 From: Sanjeev <ghane0@gmail.com> Date: Sat, 24 Dec 2016 16:27:30 +0800 Subject: [PATCH] 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: Sanjeev Gupta <ghane0@gmail.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net> --- Documentation/pps/pps.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/pps/pps.txt b/Documentation/pps/pps.txt index a15a1169cbd94..a9f53bba910d7 100644 --- a/Documentation/pps/pps.txt +++ b/Documentation/pps/pps.txt @@ -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. 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 @@ -71,7 +71,7 @@ PPS with USB to serial devices 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 -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 synchronization. -- GitLab