man: document systemd.random-seed=

[thirdparty/systemd.git] / docs / BLOCK_DEVICE_LOCKING.md

diff --git a/docs/BLOCK_DEVICE_LOCKING.md b/docs/BLOCK_DEVICE_LOCKING.md
index 58178ad2f70b07775bd761fe84f2929855189fb4..f122eda417280cf10fa91354a1fc7dcea7622229 100644 (file)
--- a/docs/BLOCK_DEVICE_LOCKING.md
+++ b/docs/BLOCK_DEVICE_LOCKING.md
@@ -1,5 +1,7 @@
 ---
 title: Locking Block Device Access
+category: Interfaces
+layout: default
 ---
 
 # Locking Block Device Access
@@ -34,7 +36,7 @@ formatting tools to safely and easily take exclusive ownership of a block
 device while operating: before starting work on the block device, they should
 take an `LOCK_EX` lock on it. This has two effects: first of all, in case
 `systemd-udevd` is still processing the device the tool will wait for it to
-finish. Second, after the lock is taken, it can be sure that that
+finish. Second, after the lock is taken, it can be sure that
 `systemd-udevd` will refrain from processing the block device, and thus all
 other client applications subscribed to it won't get device notifications from
 potentially half-written data either. After the operation is complete the