From 4f1d815552cec1ff1b73eb3567d69553cb3c6403 Mon Sep 17 00:00:00 2001
From: keramida <keramida@FreeBSD.org>
Date: Sun, 24 Mar 2002 00:56:38 +0000
Subject: [PATCH] Be a bit more verbose.  "modtime" means nothing.
 "modification time" is a lot better.

MFC after:      3 days
---
 usr.sbin/cron/cron/cron.8 | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/usr.sbin/cron/cron/cron.8 b/usr.sbin/cron/cron/cron.8
index 2361ebf9d2b6..d47735bbc833 100644
--- a/usr.sbin/cron/cron/cron.8
+++ b/usr.sbin/cron/cron/cron.8
@@ -58,18 +58,18 @@ environment variable in the crontab, if such exists).
 .Pp
 Additionally,
 .Nm
-checks each minute to see if its spool directory's modtime (or the modtime
-on
+checks each minute to see if its spool directory's modification time (or
+the modification time on
 .Pa /etc/crontab )
 has changed, and if it has,
 .Nm
-will then examine the modtime on all crontabs and reload those which have
-changed.  Thus
+will then examine the modification time on all crontabs and reload those
+which have changed.  Thus
 .Nm
 need not be restarted whenever a crontab file is modified.  Note that the
 .Xr crontab 1
-command updates the modtime of the spool directory whenever it changes a
-crontab.
+command updates the modification time of the spool directory whenever it
+changes a crontab.
 .Pp
 Available options:
 .Bl -tag -width indent