aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRussell Harmon <[email protected]>2023-06-04 22:08:50 -0700
committerMike Snitzer <[email protected]>2023-06-22 18:39:50 -0400
commitc3ba5aa6f789097364398ad38fe541841bade17d (patch)
tree388702e241aedfa1683b527e6bf928ed401171e4
parent25c9a4ab4d73d251886e6b317181cfc433e011f9 (diff)
Documentation: dm-integrity: Fix minor grammatical error.
"where dm-integrity uses bitmap" becomes "where dm-integrity uses a bitmap" Signed-off-by: Russell Harmon <[email protected]> Reviewed-by: Bagas Sanjaya <[email protected]> Signed-off-by: Mike Snitzer <[email protected]>
-rw-r--r--Documentation/admin-guide/device-mapper/dm-integrity.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/admin-guide/device-mapper/dm-integrity.rst b/Documentation/admin-guide/device-mapper/dm-integrity.rst
index 8db172efa272..b2a698e955a3 100644
--- a/Documentation/admin-guide/device-mapper/dm-integrity.rst
+++ b/Documentation/admin-guide/device-mapper/dm-integrity.rst
@@ -25,7 +25,7 @@ mode it calculates and verifies the integrity tag internally. In this
mode, the dm-integrity target can be used to detect silent data
corruption on the disk or in the I/O path.
-There's an alternate mode of operation where dm-integrity uses bitmap
+There's an alternate mode of operation where dm-integrity uses a bitmap
instead of a journal. If a bit in the bitmap is 1, the corresponding
region's data and integrity tags are not synchronized - if the machine
crashes, the unsynchronized regions will be recalculated. The bitmap mode