[Git][NTPsec/ntpsec][master] Typos

[Matt Selsky]

Matt Selsky pushed to branch master at NTPsec / ntpsec


Commits:
399318a1 by Matt Selsky at 2019-08-25T20:41:17Z
Typos

- - - - -


5 changed files:

- NEWS
- devel/README
- devel/tidy
- ntpd/ntp_restrict.c
- ntpd/ntp_wrapdate.c


Changes:

=====================================
NEWS
=====================================
@@ -22,7 +22,7 @@ The neoclock4x driver has been removed, due to the hardware and the
 vendor having utterly vanished from the face of the earth.
 
 The NTS ALPN negotiation sequence has been modified for improved
-interoperability with orther NTS implementations.
+interoperability with other NTS implementations.
 
 NTS key rotation now happens every 24 hours.  It used to rotate
 every hour to enable testing of recovery from stale cookies.


=====================================
devel/README
=====================================
@@ -50,7 +50,7 @@ release.nix::
 	NixOS build recipe.
 
 tidy::
-	Wrapper for clang-tidy, use ut to canicalize code.
+	Wrapper for clang-tidy, use it to canonicalize code.
 
 trace/::
 	Configuration files for the RTEMS trace utility.  These


=====================================
devel/tidy
=====================================
@@ -2,12 +2,12 @@
 #
 # Use clang-tidy to fill in all optional control structure braces.
 #
-# Doesn't do the right thing with trailing braces; you must indent hthese by hand.
+# Doesn't do the right thing with trailing braces; you must indent these by hand.
 # This could be fixed by running clang-format, but this script exists because
 # we're not yet ready for that churn.
 #
 # This sometimes messes up slightly.  It can miss single-statement ifs -
-# that is, nott wrap the body in { } when it should. More seriously, t sometimes
+# that is, not wrap the body in { } when it should. More seriously, it sometimes
 # places generated closing braces in the middle of assignments and return
 # expressions that should precede them.
 #


=====================================
ntpd/ntp_restrict.c
=====================================
@@ -67,7 +67,7 @@ struct restriction_data rstrct = {
    * Parameters of the RES_LIMITED restriction option. We define headway
    * as the idle time between packets. A packet is discarded if the
    * headway is less than the minimum, as well as if the average headway
-   * is less than eight times the increment. 
+   * is less than eight times the increment.
    */
   .ntp_minpkt = NTP_MINPKT,   /* minimum (log 2 s) */
   .ntp_minpoll = NTP_MINPOLL, /* increment (log 2 s) */


=====================================
ntpd/ntp_wrapdate.c
=====================================
@@ -1,7 +1,7 @@
 /*
  * Calendar-oriented stuff -- perhaps a bit hard to grok.
  *
- * Used for interpreting GPS sentences and resolving wrap issies
+ * Used for interpreting GPS sentences and resolving wrap issues
  * around 2-digit years.  Formerly part of refclock_nmea.c,
  * dissected out so it can be used by other drivers.
  */
@@ -45,7 +45,7 @@ wrapdate_init(void)
 	 * This assumes that the build system was roughly in sync with
 	 * the world, and that really synchronising to a time before the
 	 * program was created would be unsafe or insane. If the build
-	 * date cannot be stablished, at least use the start of GPS
+	 * date cannot be established, at least use the start of GPS
 	 * (1980-01-06) as minimum, because GPS can surely NOT
 	 * synchronise beyond it's own big bang. We add a little safety
 	 * margin for the fuzziness of the build date, which is in an
@@ -92,7 +92,7 @@ unfold_day(
 	ntpcal_split rec_ds;
 
 	/*
-	 * basically this is the peridiodic extension of the receive
+	 * basically this is the periodic extension of the receive
 	 * time - 12hrs to the time-of-day with a period of 1 day.
 	 * But we would have to execute this in 64bit arithmetic, and we
 	 * cannot assume we can do this; therefore this is done
@@ -210,10 +210,10 @@ gpsfix_century(
 
 /*
  * -------------------------------------------------------------------
- * And now the final execise: Considering the fact that many (most?)
+ * And now the final exercise: Considering the fact that many (most?)
  * GPS receivers cannot handle a GPS epoch wrap well, we try to
  * compensate for that problem by unwrapping a GPS epoch around the
- * receive stamp. Another execise in periodic unfolding, of course,
+ * receive stamp. Another exercise in periodic unfolding, of course,
  * but with enough points to take care of.
  *
  * Note: The integral part of 'tofs' is intended to handle small(!)
@@ -224,7 +224,7 @@ gpsfix_century(
  */
 l_fp
 eval_gps_time(
-	const char            * clockname,  /* ffor logging */
+	const char            * clockname,      /* for logging */
 	const struct calendar * gpst,           /* GPS time stamp  */
 	const struct timespec * tofs,           /* GPS frac second & offset */
 	const bool            trusted,          /* do we fully trust dates from this GPS? */



View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/399318a1d8b2ba171a6e61b9b9e123231da90087

-- 
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/399318a1d8b2ba171a6e61b9b9e123231da90087
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/20190825/82f19993/attachment-0001.htm>