diff options
| author | Eric S. Raymond <esr@thyrsus.com> | 2015-03-10 08:06:44 -0400 |
|---|---|---|
| committer | Eric S. Raymond <esr@thyrsus.com> | 2015-03-10 08:06:44 -0400 |
| commit | 9b75c8573665113ac7cda15843c3ce5c0ccc8bdd (patch) | |
| tree | 6b0fb5800cafbbf38eb888f1514725f35ac91a96 /www | |
| parent | 4a80b193d5a95ef1d07f1d8341a3a5331f2815e3 (diff) | |
| download | gpsd-9b75c8573665113ac7cda15843c3ce5c0ccc8bdd.tar.gz | |
Minor typo fixes.
Diffstat (limited to 'www')
| -rw-r--r-- | www/time-service-intro.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/www/time-service-intro.txt b/www/time-service-intro.txt index 969dbebd..a30b0cff 100644 --- a/www/time-service-intro.txt +++ b/www/time-service-intro.txt @@ -151,7 +151,7 @@ software timing loops to ever notice. But large changes are possible. Most computers are just NTP clients. They send NTP requests to a set of servers and use it to adjust the local clock. It is generally expected that NTP clients will have an accuracy (that is, maximum -divergence from the master atomic clock) of at most ±100 mSec, +divergence from the master atomic clock) of at most 100ms, possibly less depending upon the quality of your network connection. Some NTP hosts are time *servers*. These are known as "chimers". @@ -238,7 +238,7 @@ in more detail there. | | |NIST/UNSO modem time | 4ms (4000000ns) |Normal accuracy of NTP | ~ 100ms (100000000ns) -|Jitter of in-band GPS time | > 100ns (100000000ns) +|Jitter of in-band GPS time | > 100ms (100000000ns) |============================================================== == Further Reading == |