Update README

[linuxjm/LDP_man-pages.git] / original / man4 / rtc.4

diff --git a/original/man4/rtc.4 b/original/man4/rtc.4
index fd67262..5a94835 100644 (file)
--- a/original/man4/rtc.4
+++ b/original/man4/rtc.4
@@ -58,7 +58,7 @@ a software clock maintained by the kernel and used to implement
 .BR gettimeofday (2)
 and
 .BR time (2),
-as well as setting timestamps on files, etc.
+as well as setting timestamps on files, and so on.
 The system clock reports seconds and microseconds since a start point,
 defined to be the POSIX Epoch: 1970-01-01 00:00:00 +0000 (UTC).
 (One common implementation counts timer interrupts, once
@@ -307,8 +307,8 @@ it will update a designated RTC periodically every 11 minutes.
 To do so, the kernel has to briefly turn off periodic interrupts;
 this might affect programs using that RTC.
 
-An RTC's Epoch has nothing to do with the POSIX Epoch which is only
-used for the system clock.
+An RTC's Epoch has nothing to do with the POSIX Epoch which is
+used only 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, that is, between 2000
@@ -318,7 +318,7 @@ Some RTCs support "wildcard" values in alarm fields, to support
 scenarios like periodic alarms at fifteen minutes after every hour,
 or on the first day of each month.
 Such usage is nonportable;
-portable user-space code only expects a single alarm interrupt, and
+portable user-space code expects only a single alarm interrupt, and
 will either disable or reinitialize the alarm after receiving it.
 
 Some RTCs support periodic interrupts with periods that are multiples
@@ -341,3 +341,12 @@ capabilities that are not currently exposed by this API.
 
 .I Documentation/rtc.txt
 in the Linux kernel source tree
+.SH COLOPHON
+This page is part of release 3.79 of the Linux
+.I man-pages
+project.
+A description of the project,
+information about reporting bugs,
+and the latest version of this page,
+can be found at
+\%http://www.kernel.org/doc/man\-pages/.