From: daniel watson <ozzloy@each.do>
To: kernelnewbies@kernelnewbies.org
Subject: sanity check typo patch "quired"
Date: Wed, 26 Jun 2024 21:30:45 -0700 [thread overview]
Message-ID: <87cyo3atpa.fsf@trent-reznor> (raw)
here's a patch to fix a typo in the memory management docs. i'm
sending to this mailing list first for a sanity check.
From: Daniel Watson <ozzloy@each.do>
To: Jonathan Corbet <corbet@lwn.net>,linux-doc@vger.kernel.org,linux-kernel@vger.kernel.org
Date: Wed, 26 Jun 2024 21:18:22 -0700
Subject: [PATCH] mm: docs: correct 'quired' to 'queried'
Convert from the word "quired" to the word "queried" which makes more
sense in this context.
Signed-off-by: Daniel Watson <ozzloy@each.do>
---
Documentation/admin-guide/mm/index.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/mm/index.rst b/Documentation/admin-guide/mm/index.rst
index 1f883abf3f00f..8b35795b664be 100644
--- a/Documentation/admin-guide/mm/index.rst
+++ b/Documentation/admin-guide/mm/index.rst
@@ -10,7 +10,7 @@ processes address space and many other cool things.
Linux memory management is a complex system with many configurable
settings. Most of these settings are available via ``/proc``
-filesystem and can be quired and adjusted using ``sysctl``. These APIs
+filesystem and can be queried and adjusted using ``sysctl``. These APIs
are described in Documentation/admin-guide/sysctl/vm.rst and in `man 5 proc`_.
.. _man 5 proc: http://man7.org/linux/man-pages/man5/proc.5.html
--
2.43.0
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2024-06-27 4:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 4:30 daniel watson [this message]
2024-06-29 10:48 ` sanity check typo patch "quired" Ricardo B. Marliere
2024-07-01 15:35 ` daniel watson
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=87cyo3atpa.fsf@trent-reznor \
--to=ozzloy@each.do \
--cc=kernelnewbies@kernelnewbies.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