Fix leap year comments. 2000 is a leap year, so code without a century-test

still works until 2100.

2 files changed, 3 insertions, 3 deletions

diff --git a/usr.sbin/xntpd/xntpd/refclock_acts.c b/usr.sbin/xntpd/xntpd/refclock_acts.c
index 39ff433..ad3c33a 100644
--- a/usr.sbin/xntpd/xntpd/refclock_acts.c
+++ b/usr.sbin/xntpd/xntpd/refclock_acts.c
@@ -291,7 +291,7 @@ extern	u_char sys_poll;	/* log2 of system poll interval */
 extern	struct peer *sys_peer;	/* system peer structure pointer */
 
 /*
- * Tables to compute the ddd of year form icky dd/mm timecode. Viva la
+ * Tables to compute the ddd of year from icky dd/mm timecode. Viva la
  * leap.
  */
 static day1tab[] = {31, 28, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31};
@@ -581,7 +581,7 @@ acts_receive(rbufp)
 		(void)write(pp->io.fd, &flag, 1);
 
 	/*
-	 * Yes, I know this code incorrectly thinks that 2000 is a leap
+	 * Yes, I know this code incorrectly thinks that 2100 is a leap
 	 * year. The ACTS timecode format croaks then anyway. Life is
 	 * short. Would only the timecode mavens resist the urge to
 	 * express months of the year and days of the month in favor of
diff --git a/usr.sbin/xntpd/xntpd/refclock_heath.c b/usr.sbin/xntpd/xntpd/refclock_heath.c
index a1b602c..6f2899d 100644
--- a/usr.sbin/xntpd/xntpd/refclock_heath.c
+++ b/usr.sbin/xntpd/xntpd/refclock_heath.c
@@ -297,7 +297,7 @@ heath_receive(rbufp)
 	 * be avoided if the engineers had been required to write a
 	 * device driver before finalizing the timecode format.
 	 *
-	 * Yes, I know this code incorrectly thinks that 2000 is a leap
+	 * Yes, I know this code incorrectly thinks that 2100 is a leap
 	 * year; but, the latest year that can be set by the DIPswitches
 	 * is 1997 anyay. Life is short.
 	 */