[Git][NTPsec/ntpsec][master] 2 commits: minor typos in rollover.html

[Gary E. Miller]

Gary E. Miller pushed to branch master at NTPsec / ntpsec


Commits:
9f5698e9 by Paul Theodoropoulos at 2018-08-07T21:10:39Z
minor typos in rollover.html

- - - - -
163297a4 by Paul Theodoropoulos at 2018-08-07T21:13:03Z
minor typos in ntpspeak.txt

- - - - -


2 changed files:

- docs/ntpspeak.txt
- docs/rollover.txt


Changes:

=====================================
docs/ntpspeak.txt
=====================================
@@ -114,9 +114,9 @@
    interface.
 
 [[GPS pivot date]] GPS pivot date::
-   The GPS pivot date is specific fixed arbitrary time.  It is stored in
+   The GPS pivot date is a specific fixed arbitrary time.  It is stored in
    the firmware of a GPS receiver, and is probably the date that firmware
-   was released.  For reasons, a GPS receiver will start reporting
+   was released.  For this reason, a GPS receiver will start reporting
    incorrect time 512 weeks (9.8 years) or 1024 weeks (19.6 years) after
    it's pivot date.  There is generally no way to determine what a given
    GPS receiver's pivot date is, or to determine that it has failed in


=====================================
docs/rollover.txt
=====================================
@@ -231,10 +231,10 @@ ability to change the base date, the device will ship incorrect
 reports forever afterwards.  A few refclocks, like the HP-GPS line,
 have that ability; most do not.
 
-This where careless, low-budget design begins to matter. GPS vendors
+This is where careless, low-budget design begins to matter. GPS vendors
 do not document even the fact that they use base or pivot dates, let
 alone what the base and pivot dates for their devices are. As of 2017,
-NTP's developers no not know of any devices for which you can even
+NTP's developers do not know of any devices for which you can even
 query these parameters, let alone set them.  The best you can generally
 do (and on only some devices) is get the firmware release date; from this,
 you can assume that you will get non-timewarped reports for 1024 weeks



View it on GitLab: https://gitlab.com/NTPsec/ntpsec/compare/18766cb66c94fdea272683ef515fb36c172a8378...163297a45427542f514d6043bba124e83762f37f

-- 
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/compare/18766cb66c94fdea272683ef515fb36c172a8378...163297a45427542f514d6043bba124e83762f37f
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/20180807/fa63bd43/attachment.html>