From: Samanta Navarro <ferivoz@riseup.net>
To: linux-man@vger.kernel.org
Cc: alx.manpages@gmail.com, mtk.manpages@gmail.com
Subject: [patch] futex.2, mount_setattr.2, proc.5, netlink.7, tcp.7: tfix
Date: Sat, 13 Nov 2021 11:58:08 +0000 [thread overview]
Message-ID: <20211113115808.zzvid3gla4r33kc4@localhost> (raw)
Typos found with codespell.
Signed-off-by: Samanta Navarro <ferivoz@riseup.net>
---
man2/futex.2 | 2 +-
man2/mount_setattr.2 | 2 +-
man5/proc.5 | 4 ++--
man7/netlink.7 | 2 +-
man7/tcp.7 | 2 +-
5 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/man2/futex.2 b/man2/futex.2
index 1dd77ac..7210030 100644
--- a/man2/futex.2
+++ b/man2/futex.2
@@ -1137,7 +1137,7 @@ except that the clock against which
is measured is selectable.
By default, the (absolute) timeout specified in
.I timeout
-is measured againt the
+is measured against the
.B CLOCK_MONOTONIC
clock, but if the
.B FUTEX_CLOCK_REALTIME
diff --git a/man2/mount_setattr.2 b/man2/mount_setattr.2
index 77233f5..ca56256 100644
--- a/man2/mount_setattr.2
+++ b/man2/mount_setattr.2
@@ -986,7 +986,7 @@ main(int argc, char *argv[])
.\" because. Because making assumptions about the current working directory
.\" of the calling process is just too easy to get wrong; especially when
.\" pivot_root() or chroot() are in play.
-.\" My absolut preference (joke intended) is to open a well-known starting
+.\" My absolute preference (joke intended) is to open a well-known starting
.\" point with an absolute path to get a dirfd and then scope all future
.\" operations beneath that dirfd. This already works with old-style
.\" openat() and _very_ cautious programming but openat2() and its
diff --git a/man5/proc.5 b/man5/proc.5
index c668462..3f16dcd 100644
--- a/man5/proc.5
+++ b/man5/proc.5
@@ -3068,7 +3068,7 @@ Further information about the zones can be found in
.IR /proc/zoneinfo .
.TP
.I /proc/bus
-Contains subdirectories for installed busses.
+Contains subdirectories for installed buses.
.TP
.I /proc/bus/pccard
Subdirectory for PCMCIA devices when
@@ -3079,7 +3079,7 @@ is set at kernel compilation time.
.TP
.I /proc/bus/pci
Contains various bus subdirectories and pseudo-files containing
-information about PCI busses, installed devices, and device
+information about PCI buses, installed devices, and device
drivers.
Some of these files are not ASCII.
.TP
diff --git a/man7/netlink.7 b/man7/netlink.7
index 6b04fea..2991ec7 100644
--- a/man7/netlink.7
+++ b/man7/netlink.7
@@ -191,7 +191,7 @@ structure,
.B NLMSG_DONE
message terminates a multipart message.
Error messages get the
-original request appened, unless the user requests to cap the
+original request appended, unless the user requests to cap the
error message, and get extra error data if requested.
.PP
.in +4n
diff --git a/man7/tcp.7 b/man7/tcp.7
index 0a7c61a..8a871fc 100644
--- a/man7/tcp.7
+++ b/man7/tcp.7
@@ -1161,7 +1161,7 @@ This option takes an
as an argument.
When the value is greater than 0,
it specifies the maximum amount of time in milliseconds that transmitted
-data may remain unacknowledged, or bufferred data may remain untransmitted
+data may remain unacknowledged, or buffered data may remain untransmitted
(due to zero window size) before TCP will forcibly close the
corresponding connection and return
.B ETIMEDOUT
--
2.33.1
next reply other threads:[~2021-11-13 12:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 11:58 Samanta Navarro [this message]
2021-11-13 12:41 ` [patch] futex.2, mount_setattr.2, proc.5, netlink.7, tcp.7: tfix G. Branden Robinson
2021-11-22 17:12 ` Alejandro Colomar (man-pages)
2021-11-22 17:14 ` Alejandro Colomar (man-pages)
2021-11-24 11:59 ` Samanta Navarro
2021-11-29 12:17 ` Alejandro Colomar (man-pages)
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=20211113115808.zzvid3gla4r33kc4@localhost \
--to=ferivoz@riseup.net \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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