Skip to contentSkip to conversation

Documentation: fix grammar in description of nilfs2 recovery code

PATCH Applied Manoj K M 3 participants 3 messages Jul 25 – Jul 28

Subsystems (2)
lore
Share & tools
lore

Manoj K M

author
#0 lore raw

PATCH 1/1 Documentation: fix grammar in description of nilfs2 recovery code

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.

---
 Documentation/filesystems/nilfs2.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/filesystems/nilfs2.rst +1 -1
index e3a5c8977..a0124d22a 100644
@@ -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
Signature · 1 line
2.53.0
maintainer Acked-by on v1 1/1
#1 lore raw
Quoted 24 lines · Manoj K M

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.

---
 Documentation/filesystems/nilfs2.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/filesystems/nilfs2.rst +1 -2
index e3a5c8977..a0124d22a 100644
@@ -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
--
Quoted 2 lines

2.53.0

Thank you for the fix!

Viacheslav, could you please pick this up directly into your tree?

Thanks,
Ryusuke Konishi

maintainer Applied
#2 lore raw
Quoted 37 lines · Ryusuke Konishi
Quoted 28 lines · Manoj K M

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.

---
 Documentation/filesystems/nilfs2.rst | 2 +-

 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/filesystems/nilfs2.rst +0 -0
index e3a5c8977..a0124d22a 100644
@@ -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.

Quoted 5 lines

 The super root block is inserted for every checkpoints.  It includes
--
2.53.0

Thank you for the fix!

Quoted 4 lines

Viacheslav, could you please pick this up directly into your tree?

Applied.

Thanks,
Slava.