From: Sascha Wildner <saw@online.de>
Date: Thu, 9 Dec 2010 04:09:03 +0000 (+0100)
Subject: swapcache.8: Fix typos.
X-Git-Url: https://gitweb.dragonflybsd.org/~alexh/dragonfly.git/commitdiff_plain/b979d6351b902f1ab46bff59ed4a33e803925bd7

swapcache.8: Fix typos.
---

diff --git a/share/man/man8/swapcache.8 b/share/man/man8/swapcache.8
index a129210c62..a0827b3d48 100644
--- a/share/man/man8/swapcache.8
+++ b/share/man/man8/swapcache.8
@@ -431,7 +431,7 @@ to its factory-fresh condition (sans wear already present).
 SSDs have wear leveling algorithms which are responsible for trying
 to even out the erase/write cycles across all flash cells in the
 storage.  The better a job the SSD can do the longer the SSD will
-remain useable.
+remain usable.
 .Pp
 The more unused storage there is from the SSDs point of view the
 easier a time the SSD has running its wear leveling algorithms.
@@ -470,7 +470,7 @@ Operating systems can also help maintain the SSDs performance by utilizing
 larger blocks.
 Write-combining results in a net-reduction
 of write-amplification effects but due to having to de-combine later and
-other fragmentory effects it isn't 100%.
+other fragmentary effects it isn't 100%.
 From testing with Intel devices write-amplification can be well controlled
 in the 2x-4x range with the OS doing 16K writes, verses a worst-case
 8x write-amplification with 16K blocks, 32x with 4K blocks, and a truly