From 8889e5ea5bd8a2f55ee41c9b3d94afef177ce0a9 Mon Sep 17 00:00:00 2001 From: Sam Gleske Date: Fri, 25 Jul 2014 00:00:17 -0400 Subject: [PATCH] doc: encfs spelling and grammar corrections Conflicts: encfs/encfs.pod --- encfs/encfs.pod | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/encfs/encfs.pod b/encfs/encfs.pod index 70a8b7f..5e883d6 100644 --- a/encfs/encfs.pod +++ b/encfs/encfs.pod @@ -283,8 +283,8 @@ to decode filenames if desired. B is not a true filesystem. It does not deal with any of the actual storage or maintenance of files. It simply translates requests (encrypting or decrypting as necessary) and passes the requests through to the underlying -host filesystem. Therefor any limitations of the host filesystem will likely -be inherited by B (or possibly be further limited). +host filesystem. Therefore any limitations of the host filesystem will be +inherited by B (or possibly be further limited). One such limitation is filename length. If your underlying filesystem limits you to N characters in a filename, then B will limit you to approximately @@ -341,7 +341,7 @@ function. The number of iterations in the keying function is selected based on wall clock time to generate the key. In standard mode, a target time of 0.5 seconds is used, and in paranoia mode a target of 3.0 seconds is used. -On a 1.6Ghz AMD 64 system, it rougly 64k iterations of the key derivation +On a 1.6Ghz AMD 64 system, roughly 64k iterations of the key derivation function can be handled in half a second. The exact number of iterations to use is stored in the configuration file, as it is needed to remount the filesystem.