summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorSanjeev <ghane0@gmail.com>2016-12-24 16:27:30 +0800
committerJonathan Corbet <corbet@lwn.net>2017-01-04 14:39:42 -0700
commitfe4c56c98c1338c0b8b69d08ccf5694bf8e1dcaf (patch)
tree4d29e8590d3c02b190bf2a6c8e6188dd68073126 /Documentation
parente1235e18b502610becb99a1b6971a2afbbe02fa5 (diff)
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>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/pps/pps.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/pps/pps.txt b/Documentation/pps/pps.txt
index a15a1169cbd9..a9f53bba910d 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.