[Git][NTPsec/ntpsec][master] Spelling/typos

[Matt Selsky]

Matt Selsky pushed to branch master at NTPsec / ntpsec


Commits:
13f66e0d by Matt Selsky at 2017-09-14T12:50:55Z
Spelling/typos

- - - - -


4 changed files:

- docs/rollover.txt
- pylib/agentx.py
- tests/pylib/test_packet.py
- tests/pylib/test_util.py


Changes:

=====================================
docs/rollover.txt
=====================================
--- a/docs/rollover.txt
+++ b/docs/rollover.txt
@@ -88,15 +88,15 @@ distribution.  This problem may persist in post-2000 devices that
 are designed for compatility to use the same reporting protocols,
 such as Spectracom's "Type 2".
 
-There is an internal workaround ti deal with two-digit dates in
-{ntpdman}, but it relies of the sytem clock being at least roughly
+There is an internal workaround to deal with two-digit dates in
+{ntpdman}, but it relies on the system clock being at least roughly
 correct - it won't work (for example) at boot time if the clock
 has been trashed or zeroed due to a failed battery backup, and
 you have no remote check peers yet.
 
 Warnings have been attached to the documentation of NTP clock drivers
 that may have a vulnerability here.  Notably, the NMEA and SHM drivers
-(probaly the two in most common use) do *not* have this problem; the
+(probably the two in most common use) do *not* have this problem; the
 NMEA driver uses a clever calendrical trick to deduce a 4-digit year
 that should work until 2399.
 


=====================================
pylib/agentx.py
=====================================
--- a/pylib/agentx.py
+++ b/pylib/agentx.py
@@ -972,7 +972,7 @@ def encode_pduheader(pduType, instanceRegistration, newIndex,
     return data
 
 
-def decode_pduheader(data):  # Endianess is controlled from the PDU header
+def decode_pduheader(data):  # Endianness is controlled from the PDU header
     lineone, data = slicedata(data, 4)
     version, pduType, flags = struct.unpack(">BBBx", lineone)
     if pduType not in definedPDUTypes:


=====================================
tests/pylib/test_packet.py
=====================================
--- a/tests/pylib/test_packet.py
+++ b/tests/pylib/test_packet.py
@@ -440,7 +440,7 @@ class TestMisc(unittest.TestCase):
                "\x08\x09\x0A\x0B\x0C\x0D\x0E\x0F"
         # Test a single line
         f(data, fp)
-        total = "".join(fp.data)  # easier than 300 million seperate strings
+        total = "".join(fp.data)  # easier than 300 million separate strings
         fp.data = []
         self.assertEqual(total,
                          "00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f "


=====================================
tests/pylib/test_util.py
=====================================
--- a/tests/pylib/test_util.py
+++ b/tests/pylib/test_util.py
@@ -989,7 +989,7 @@ class TestPeerSummary(unittest.TestCase):
         data = {"srchost": "wouldn't"}
         self.assertEqual(m(data), False)
         # Test False, no host
-        data = {"blah": "definately wouldn't"}
+        data = {"blah": "definitely wouldn't"}
         self.assertEqual(m(data), False)
 
     def test_header(self):



View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/13f66e0d3497505f6f61e6187e8978b7cb9a8d17

---
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/13f66e0d3497505f6f61e6187e8978b7cb9a8d17
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/20170914/aad459f8/attachment.html>