"in which to store the key" sounds clunky, so just getting rid of the "in".

diff --git a/doc/zcrypt.mdwn b/doc/zcrypt.mdwn
index f52ee162102c8ed4fca5d78076f73ccf56a48d70..cb27e717587442e96adfaf244f08c23e908980f6 100644 (file)
--- a/doc/zcrypt.mdwn
+++ b/doc/zcrypt.mdwn
@@ -11,7 +11,7 @@ The main requirement for a `zcrypt`ed zephyr class is to distribute a key to all
     fs sa ~/Public/zcrypt/label/ system:groupname read  # Allow an appropriate user/group to read the key
     tr -d '\000\n' < /dev/urandom | head -c 126 > ~/Public/zcrypt/label/key.zcrypt
 
-The first three lines create a directory to store the key in, and set the permissions properly. You should replace `label` with an appropriate name; you may want to use something besides the class name in order to help keep the class name private. Subbing to the class will disclose traffic patterns and instances used, so you may want to use the traditional "secret class" (keeping the name secret) as a first line of defense, in addition to `zcrypt`.
+The first three lines create a directory to store the key, and set the permissions properly. You should replace `label` with an appropriate name; you may want to use something besides the class name in order to help keep the class name private. Subbing to the class will disclose traffic patterns and instances used, so you may want to use the traditional "secret class" (keeping the name secret) as a first line of defense, in addition to `zcrypt`.
 
 The last line creates the key, which should be a random byte string of at least 126 characters, none of which should be null or newlines.