Simplify structure, update Readme

.gitignore

@@ -1 +0,0 @@
-.gitcrypt/pass

README.md

@@ -2,27 +2,32 @@
 
 *Store files encrypted, have them decrypted only in the working directory.*
 
-Simply clone this repository to create an encrypted repository.
+Simply clone this repository to create an encrypted one.
 
 OpenSSL is needed.
 
+Tested in Linux and Git for Windows 2.6.
+
 Thanks for [Woody Gilk's tutorial](https://gist.github.com/shadowhand/873637)
 which served as a starting point.
 
 # Installation
 
-1. **Before using GitCrypt the first time, register the filters:**
+1. Before using GitCrypt the first time, register the filters:
 
 		git config --global filter.gitcrypt.smudge .gitcrypt/dec
 		git config --global filter.gitcrypt.clean .gitcrypt/enc
 		git config --global diff.gitcrypt.textconv .gitcrypt/diff
 
-	If this step is omitted, files get added unencrypted silently.
+	**If this step is omitted, files get added unencrypted silently.**
 	However, it is not needed, if GitCrypt has been used before.
 
 2. Imagine a repository password.
 It is either expected in the environment variable `$GITCRYPT_PASS`,
-or in the file `.gitcrypt/pass` (which is ignored by Git).
+or in the file `.git/pass` (which is ignored by Git).
+
+	**Hint:** You can enter the password safely by using the command:
+	`read -s GITCRYPT_PASS`
 
 3. After that, generate a salt:
 
@@ -67,3 +72,11 @@ Why do errors like the following occur when cloning the repository:
 
 	The errors can be ignored.
 
+*  **Question:**
+Why another version besides [git-encrypt](https://github.com/shadowhand/git-encrypt)
+and [git-crypt](https://github.com/AGWA/git-crypt)?
+
+	**Answer:**
+	First and foremost for me to learn something.
+	But as an admirer of the [KISS principle](https://en.wikipedia.org/wiki/KISS_principle),
+	I felt that it should be even easier and less code.