[Git][NTPsec/ntpsec][master] Fix typos in rollover doc

[Matt Selsky]

Matt Selsky pushed to branch master at NTPsec / ntpsec


Commits:
45fdb463 by Matt Selsky at 2018-01-04T04:56:43+00:00
Fix typos in rollover doc

Closes Gitlab issue #433

- - - - -


1 changed file:

- docs/rollover.txt


Changes:

=====================================
docs/rollover.txt
=====================================
--- a/docs/rollover.txt
+++ b/docs/rollover.txt
@@ -131,7 +131,7 @@ of GMT (Greenwich Mean Time) without leap seconds.
 On POSIX-compliant Unix systems (which is now effectively all) Unix
 time can be retrieved with nanosecond precision; some older versions
 supported only millisecond precision.  The subseconds counter is not
-involved in any of the rollover or leap-second issues thith the
+involved in any of the rollover or leap-second issues with the
 seconds counter.
 
 The Unix 32-bit rollover may fizzle the way Y2K did, and will if a
@@ -254,7 +254,7 @@ Finally, when you buy a GPS you do not know - and often will not be
 able to discover - how far in the past its hidden pivot date is.  This
 means that time service operators using a GPS as a local Stratum 0
 need to be aware of the possibility that their device could roll over
-at any time (but especially near the zero dats of a GPS era) and be
+at any time (but especially near the zero days of a GPS era) and be
 ready to compensate by dropping in a device with a newer pivot date.
 
 Actionable advice that follows from this: If you don't know the



View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/45fdb463f8848e8d5a213c66a00be4c484b61a9a

---
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/45fdb463f8848e8d5a213c66a00be4c484b61a9a
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/20180104/eb32eb6c/attachment.html>