From a2ffd2751683f4275d4d1aa5ce37e5a6a1ae21df Mon Sep 17 00:00:00 2001 From: Matt LaPlante Date: Tue, 3 Oct 2006 22:49:15 +0200 Subject: Fix typos in Documentation/: 'F'-'G' This patch fixes typos in various Documentation txts. The patch addresses some words starting with the letters 'F'-'G'. Signed-off-by: Matt LaPlante Signed-off-by: Adrian Bunk --- Documentation/block/barrier.txt | 2 +- Documentation/block/deadline-iosched.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) (limited to 'Documentation/block') diff --git a/Documentation/block/barrier.txt b/Documentation/block/barrier.txt index 761073eae103..de3d88edb7f1 100644 --- a/Documentation/block/barrier.txt +++ b/Documentation/block/barrier.txt @@ -56,7 +56,7 @@ There are four cases, i. No write-back cache. Keeping requests ordered is enough. ii. Write-back cache but no flush operation. There's no way to -gurantee physical-medium commit order. This kind of devices can't to +guarantee physical-medium commit order. This kind of devices can't to I/O barriers. iii. Write-back cache and flush operation but no FUA (forced unit diff --git a/Documentation/block/deadline-iosched.txt b/Documentation/block/deadline-iosched.txt index c918b3a6022d..672c06bcae8b 100644 --- a/Documentation/block/deadline-iosched.txt +++ b/Documentation/block/deadline-iosched.txt @@ -23,7 +23,7 @@ you can do so by typing: read_expire (in ms) ----------- -The goal of the deadline io scheduler is to attempt to guarentee a start +The goal of the deadline io scheduler is to attempt to guarantee a start service time for a request. As we focus mainly on read latencies, this is tunable. When a read request first enters the io scheduler, it is assigned a deadline that is the current time + the read_expire value in units of -- cgit v1.2.3-59-g8ed1b