summaryrefslogtreecommitdiff
path: root/man4/rtc.4
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2007-06-08 11:56:22 +0000
committerMichael Kerrisk <mtk.manpages@gmail.com>2007-06-08 11:56:22 +0000
commit75b94dc35ca88fc72d0381c72c535180851bf08f (patch)
tree107dfea45855463eaa970ccff1b6074c305ac09a /man4/rtc.4
parentca7b3c180c14583f36bf24c7f31cc8ba342e23d8 (diff)
Change "e.g. " to "e.g., ", or in some cases, "for example, ".
Change "i.e. " to i.e.., ", or in some cases, "that is, ".
Diffstat (limited to 'man4/rtc.4')
-rw-r--r--man4/rtc.44
1 files changed, 2 insertions, 2 deletions
diff --git a/man4/rtc.4 b/man4/rtc.4
index 821d531a..a41e59bd 100644
--- a/man4/rtc.4
+++ b/man4/rtc.4
@@ -81,7 +81,7 @@ or directly with the ioctl requests listed below.
Besides tracking the date and time, many RTCs can also generate
interrupts
.IP *
-on every clock update (i.e. once per second);
+on every clock update (i.e., once per second);
.IP *
at periodic intervals with a frequency that can be set to
any power-of-2 multiple in the range 2 Hz to 8192 Hz;
@@ -310,7 +310,7 @@ An RTC's Epoch has nothing to do with the POSIX Epoch which is only
used for the system clock.
If the year according to the RTC's Epoch and the year register is
-less than 1970 it is assumed to be 100 years later, i.e. between 2000
+less than 1970 it is assumed to be 100 years later, that is, between 2000
and 2069.
Some RTCs support "wildcard" values in alarm fields, to support