[Git][NTPsec/ntpsec][master] 2 commits: Typos

[Eric S. Raymond]

Eric S. Raymond pushed to branch master at NTPsec / ntpsec


Commits:
2ff849dc by Matt Selsky at 2016-12-08T05:48:27-05:00
Typos

- - - - -
9e6097e1 by Richard Laager at 2016-12-08T05:49:22-05:00
Fix some typos

- - - - -


3 changed files:

- include/ntp_syscall.h
- ntpclients/ntpmon
- ntpd/refclock_pps.c


Changes:

=====================================
include/ntp_syscall.h
=====================================
--- a/include/ntp_syscall.h
+++ b/include/ntp_syscall.h
@@ -30,7 +30,7 @@ int ntp_gettime(struct ntptimeval *);
 
 /*
  * The units of the maxerror and esterror fields vary by platform.  If
- * STA_NANO is defined, they're in nanoseconds;, otherwise in
+ * STA_NANO is defined, they're in nanoseconds; otherwise in
  * microseconds. Hide the difference by normalizing everything to
  * float seconds.
  */


=====================================
ntpclients/ntpmon
=====================================
--- a/ntpclients/ntpmon
+++ b/ntpclients/ntpmon
@@ -84,7 +84,7 @@ if __name__ == '__main__':
                     except IOError as e:
                         raise Fatal(e.strerror)
                     except IndexError:
-                        raise Fatal("no 'hpoll' variabe in peer response")
+                        raise Fatal("no 'hpoll' variable in peer response")
                     if not variables:
                         continue
                     stdscr.addstr(peer_report.summary(session.rstatus,


=====================================
ntpd/refclock_pps.c
=====================================
--- a/ntpd/refclock_pps.c
+++ b/ntpd/refclock_pps.c
@@ -22,8 +22,8 @@
  * produced by a cesium clock, timing receiver or related equipment. It
  * can be used to remove accumulated jitter over a congested link and
  * retime a server before redistributing the time to clients. It can 
- *also be used as a holdover should all other synchronization sources
- * beconme unreachable.
+ * also be used as a holdover should all other synchronization sources
+ * become unreachable.
  *
  * Before this driver becomes active, the local clock must be set to
  * within +-0.4 s by another means, such as a radio clock or NTP
@@ -49,8 +49,8 @@
  * to hundreds of PPM), it's better to used the kernel support, if
  * available.
  *
- * This deriver is subject to the mitigation rules described in the
- * "mitigation rulse and the prefer peer" page. However, there is an
+ * This driver is subject to the mitigation rules described in the
+ * "mitigation rules and the prefer peer" page. However, there is an
  * important difference. If this driver becomes the PPS driver according
  * to these rules, it is active only if (a) a prefer peer other than
  * this driver is among the survivors or (b) there are no survivors and



View it on GitLab: https://gitlab.com/NTPsec/ntpsec/compare/8dba9cff2bfd8d58a9320fdafbc42c2887df8574...9e6097e110fe9cc845793336a4602a901ed351d5
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ntpsec.org/pipermail/vc/attachments/20161208/3041cadf/attachment.html>