From: Manoj K M <manojkm24dev@gmail.com>
To: konishi.ryusuke@gmail.com, slava@dubeyko.com, corbet@lwn.net
Cc: skhan@linuxfoundation.org, linux-nilfs@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Manoj K M <manojkm24dev@gmail.com>
Subject: [PATCH] Documentation: fix grammar in description of nilfs2 recovery code
Date: Sat, 25 Jul 2026 10:06:58 +0000 [thread overview]
Message-ID: <20260725100658.1705-1-manojkm24dev@gmail.com> (raw)
Include the word 'at' to make the sentence grammatically correct
inside the description for nilfs2 recovery code. This improves
documentation without changing the original meaning.
Signed-off-by: Manoj K M <manojkm24dev@gmail.com>
---
Documentation/filesystems/nilfs2.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/filesystems/nilfs2.rst b/Documentation/filesystems/nilfs2.rst
index e3a5c8977..a0124d22a 100644
--- a/Documentation/filesystems/nilfs2.rst
+++ b/Documentation/filesystems/nilfs2.rst
@@ -252,7 +252,7 @@ The following figure shows a typical organization of the logs::
To stride over segment boundaries, this sequence of files may be split
into multiple logs. The sequence of logs that should be treated as
logically one log, is delimited with flags marked in the segment
-summary. The recovery code of nilfs2 looks this boundary information
+summary. The recovery code of nilfs2 looks at this boundary information
to ensure atomicity of updates.
The super root block is inserted for every checkpoints. It includes
--
2.53.0
reply other threads:[~2026-07-25 10:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260725100658.1705-1-manojkm24dev@gmail.com \
--to=manojkm24dev@gmail.com \
--cc=corbet@lwn.net \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=slava@dubeyko.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