From: Austin English <austinenglish@gmail.com>
To: util-linux@vger.kernel.org
Cc: Austin English <austinenglish@gmail.com>
Subject: [PATCH 5/6] sys-utils/rtcwake.8.in: fix "maybe be" duplication
Date: Mon, 13 May 2019 13:53:18 -0500 [thread overview]
Message-ID: <20190513185319.28853-5-austinenglish@gmail.com> (raw)
In-Reply-To: <20190513185319.28853-1-austinenglish@gmail.com>
Signed-off-by: Austin English <austinenglish@gmail.com>
---
sys-utils/rtcwake.8.in | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sys-utils/rtcwake.8.in b/sys-utils/rtcwake.8.in
index 167f7f9d1..4f70c39c9 100644
--- a/sys-utils/rtcwake.8.in
+++ b/sys-utils/rtcwake.8.in
@@ -43,10 +43,10 @@ On some systems, this can also be used like \fBnvram-wakeup\fP, waking from stat
like ACPI S4 (suspend to disk). Not all systems have persistent media that are
appropriate for such suspend modes.
.PP
-Note that alarm functionality depends on hardware; not every RTC is able to setup
+Note that alarm functionality depends on hardware; not every RTC is able to setup
an alarm up to 24 hours in the future.
.PP
-The suspend setup maybe be interrupted by active hardware; for example wireless USB
+The suspend setup may be interrupted by active hardware; for example wireless USB
input devices that continue to send events for some fraction of a second after the
return key is pressed.
.B rtcwake
--
2.21.0
next prev parent reply other threads:[~2019-05-13 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 18:53 [PATCH 1/6] lib/colors.c: fix "maybe be" duplication Austin English
2019-05-13 18:53 ` [PATCH 2/6] libmount/src/utils.c: " Austin English
2019-05-13 18:53 ` [PATCH 3/6] misc-utils/lsblk.8: " Austin English
2019-05-13 18:53 ` [PATCH 4/6] sys-utils/mount.8: " Austin English
2019-05-13 18:53 ` Austin English [this message]
2019-05-13 18:53 ` [PATCH 6/6] text-utils/column.1: " Austin English
2019-05-15 11:50 ` [PATCH 1/6] lib/colors.c: " Karel Zak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190513185319.28853-5-austinenglish@gmail.com \
--to=austinenglish@gmail.com \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).