aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/filesystems
diff options
context:
space:
mode:
authorShaun Zinck <shaun.zinck@gmail.com>2007-10-19 20:38:36 -0400
committerAdrian Bunk <bunk@kernel.org>2007-10-19 20:38:36 -0400
commit7356337bd2d4416bcaa0158520542dfbd154949c (patch)
tree98e72abfb208cc95cfb261331c973462059657c4 /Documentation/filesystems
parent59dd24d32cb379d8c2b9028dcea4ec951633eaf4 (diff)
documentation/ext3: grammar fixes
Fix some grammar in the explanation of the Journal Block Device layer. Signed-off-by: Shaun Zinck <shaun.zinck@gmail.com> Acked-by: Randy Dunlap <rdunlap@xenotime.net> Signed-off-by: Adrian Bunk <bunk@kernel.org>
Diffstat (limited to 'Documentation/filesystems')
-rw-r--r--Documentation/filesystems/ext3.txt14
1 files changed, 7 insertions, 7 deletions
diff --git a/Documentation/filesystems/ext3.txt b/Documentation/filesystems/ext3.txt
index 4aecc9bdb273..b45f3c1b8b43 100644
--- a/Documentation/filesystems/ext3.txt
+++ b/Documentation/filesystems/ext3.txt
@@ -130,12 +130,12 @@ Device layer.
130 130
131Journaling Block Device layer 131Journaling Block Device layer
132----------------------------- 132-----------------------------
133The Journaling Block Device layer (JBD) isn't ext3 specific. It was design to 133The Journaling Block Device layer (JBD) isn't ext3 specific. It was designed
134add journaling capabilities on a block device. The ext3 filesystem code will 134to add journaling capabilities to a block device. The ext3 filesystem code
135inform the JBD of modifications it is performing (called a transaction). The 135will inform the JBD of modifications it is performing (called a transaction).
136journal supports the transactions start and stop, and in case of crash, the 136The journal supports the transactions start and stop, and in case of a crash,
137journal can replayed the transactions to put the partition back in a 137the journal can replay the transactions to quickly put the partition back into
138consistent state fast. 138a consistent state.
139 139
140Handles represent a single atomic update to a filesystem. JBD can handle an 140Handles represent a single atomic update to a filesystem. JBD can handle an
141external journal on a block device. 141external journal on a block device.
@@ -164,7 +164,7 @@ written to the journal first, and then to its final location.
164In the event of a crash, the journal can be replayed, bringing both data and 164In the event of a crash, the journal can be replayed, bringing both data and
165metadata into a consistent state. This mode is the slowest except when data 165metadata into a consistent state. This mode is the slowest except when data
166needs to be read from and written to disk at the same time where it 166needs to be read from and written to disk at the same time where it
167outperforms all others modes. 167outperforms all other modes.
168 168
169Compatibility 169Compatibility
170------------- 170-------------