diff options
| author | Sanjeev Gupta <ghane0@gmail.com> | 2015-03-16 02:01:21 +0800 |
|---|---|---|
| committer | Gary E. Miller <gem@rellim.com> | 2015-03-15 12:46:18 -0700 |
| commit | 8da4aa2490c93cb6762bfedca98d511e67a188df (patch) | |
| tree | 0db7bc5c29df4197b518ddaf3c2d8dc2e99e7ade /www | |
| parent | becd8ce06de3c66f617c21fd2ed2c4146c6b345d (diff) | |
| download | gpsd-8da4aa2490c93cb6762bfedca98d511e67a188df.tar.gz | |
Minor changes, units, etc.
No semantic changes
Signed-off-by: Gary E. Miller <gem@rellim.com>
Diffstat (limited to 'www')
| -rw-r--r-- | www/time-service-intro.txt | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/www/time-service-intro.txt b/www/time-service-intro.txt index a834b02a..18f45f4c 100644 --- a/www/time-service-intro.txt +++ b/www/time-service-intro.txt @@ -244,7 +244,7 @@ in more detail there. | | |NIST/UNSO modem time | 4 ms (4000000 ns) |Consumer-grade time radio | 30 ms -|Normal accuracy of NTP | ~ 30 ms (100000000 ns) footnote:[RFC5905 says "a few tens of milliseconds", but asymmetric routing can produce 100mSec jitter] +|Normal accuracy of NTP | ~ 30 ms (100000000 ns) footnote:[RFC5905 says "a few tens of milliseconds", but asymmetric routing can produce 100ms jitter] |Jitter of in-band GPS time | > 100 ms (100000000 ns) |============================================================== @@ -293,4 +293,7 @@ v1.1, 2015-03-11:: Lots of tiny corrections from G+ and the blog. Use the NTP accuracy estimate from RFC 5905. +v1.2, 2015-03-15:: + Clarifying language, proof-reading, and minor corrections. + //end |