better markup

diff --git a/doc/zcrypt.mdwn b/doc/zcrypt.mdwn
index 405a85b322c3239c3937f26dfd41de088d4c8e5c..beabe059d158909425a6dc498d3ce55d7bbc6942 100644 (file)
--- a/doc/zcrypt.mdwn
+++ b/doc/zcrypt.mdwn
@@ -2,7 +2,7 @@ Zephyr at MIT doesn't support* limiting who can sub to a zephyr class, so if you
 
 `zcrypt` encrypts message bodies, but not the message metadata. In particular, instances are visible to anyone who receives a message (as are senders, times, zsigs, etc., though that's less-frequently an issue).
 
-h2. Creating a `zcrypt`ed zephyr class
+## Creating a `zcrypt`ed zephyr class
 
 The main requirement for a `zcrypt`ed zephyr class is to have a key and distribute it to all the users of the class. Typically, this is done by storing the key in AFS. You can set that up with:
 
@@ -15,7 +15,7 @@ The first three lines create a directory to store the key in, and set the permis
 
 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.
 
-h2. Subbing to a `zcrypt`ed zephyr class
+## Subbing to a `zcrypt`ed zephyr class
 
 This may vary between clients. For traditional zephyr clients, you should sub as usual (in Barnowl, run `:sub classname`).