diff --git a/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml
index eedbab38dc..8539f7839f 100644
--- a/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml
@@ -387,22 +387,20 @@ Closing device "echo".
operations, depriving the application of the ability to know the
exact disk contents at any one instant in time.
-
- This makes predictable and reliable crash recovery of on-disk
- data structures (filesystems, databases etc.) impossible. Since
- writes may be delayed, there is no way the kernel can report to
- the application which particular write operation encountered a
- write error, this further compounds the consistency
- problem.
+ This makes predictable and reliable crash recovery of
+ on-disk data structures (filesystems, databases etc.)
+ impossible. Since writes may be delayed, there is no way
+ the kernel can report to the application which particular
+ write operation encountered a write error, this further
+ compounds the consistency problem.
-
- For this reason, no serious applications rely on block devices,
- and in fact, almost all applications which access disks directly
- take great pains to specify that character (or
- raw
) devices should always be used. Because the
- implementation of the aliasing of each disk (partition) to two
- devices with different semantics significantly complicated the
- relevant kernel code &os; dropped support for cached disk
+ For this reason, no serious applications rely on block
+ devices, and in fact, almost all applications which access
+ disks directly take great pains to specify that character
+ (or raw
) devices should always be used. Because
+ the implementation of the aliasing of each disk (partition) to
+ two devices with different semantics significantly complicated
+ the relevant kernel code &os; dropped support for cached disk
devices as part of the modernization of the disk I/O
infrastructure.