Add header, reorder headlines

diff --git a/README.asciidoc b/README.asciidoc
index c546a2de5d6d98a91ab7b03b3c4d8986135502a9..3668e4b66e15dbc2b4fea961994cb844d2c142f9 100644 (file)
--- a/README.asciidoc
+++ b/README.asciidoc
@@ -1,5 +1,11 @@
+pwstore documentation
+=====================
+Peter Palfrader, Alexander Wirt
+v0.1 July 2011
+
+
 introduction
-============
+------------
 
 The pws tool allows you to store passwords (or anything else, really) in
 a set of encrypted files.  Each file can be encrypted to a different set
@@ -7,7 +13,8 @@ of users.  pws helps you with the bookkeeping of which keys to encrypt
 each file to and provides a convinient wrapper to edit protected files.
 
 initialization
-==============
+--------------
+
 First you need a file where your users and group are defined in.  This
 file is named .users.  Lines consist of assignments of the form
  <username> = <keyfingerprint>
@@ -56,14 +63,14 @@ might have.  A patch to remove this limitation would be nice.
 
 
 adding a new file
-=================
+-----------------
 
 -----------------------------
 # pws ed -n file
 -----------------------------
 
 editing files
-=============
+-------------
 
 Every file needs a header like:
 
@@ -74,7 +81,7 @@ access: @all
 You can edit the encrypted file with the pws tool: +pwd ed file+.
 
 updating the keyring
-====================
+--------------------
 
 If available as .keyring pws instructs GnuPG to use this keyring in
 addition to the user's default keyrings.  This allows sharing of the