Commit 7356337b authored by Shaun Zinck's avatar Shaun Zinck Committed by Adrian Bunk

documentation/ext3: grammar fixes

Fix some grammar in the explanation of the Journal Block Device layer.
Signed-off-by: default avatarShaun Zinck <shaun.zinck@gmail.com>
Acked-by: default avatarRandy Dunlap <rdunlap@xenotime.net>
Signed-off-by: default avatarAdrian Bunk <bunk@kernel.org>
parent 59dd24d3
...@@ -130,12 +130,12 @@ Device layer. ...@@ -130,12 +130,12 @@ Device layer.
Journaling Block Device layer Journaling Block Device layer
----------------------------- -----------------------------
The Journaling Block Device layer (JBD) isn't ext3 specific. It was design to The Journaling Block Device layer (JBD) isn't ext3 specific. It was designed
add journaling capabilities on a block device. The ext3 filesystem code will to add journaling capabilities to a block device. The ext3 filesystem code
inform the JBD of modifications it is performing (called a transaction). The will inform the JBD of modifications it is performing (called a transaction).
journal supports the transactions start and stop, and in case of crash, the The journal supports the transactions start and stop, and in case of a crash,
journal can replayed the transactions to put the partition back in a the journal can replay the transactions to quickly put the partition back into
consistent state fast. a consistent state.
Handles represent a single atomic update to a filesystem. JBD can handle an Handles represent a single atomic update to a filesystem. JBD can handle an
external journal on a block device. external journal on a block device.
...@@ -164,7 +164,7 @@ written to the journal first, and then to its final location. ...@@ -164,7 +164,7 @@ written to the journal first, and then to its final location.
In the event of a crash, the journal can be replayed, bringing both data and In the event of a crash, the journal can be replayed, bringing both data and
metadata into a consistent state. This mode is the slowest except when data metadata into a consistent state. This mode is the slowest except when data
needs to be read from and written to disk at the same time where it needs to be read from and written to disk at the same time where it
outperforms all others modes. outperforms all other modes.
Compatibility Compatibility
------------- -------------
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment