Minor Documentation Fixes (#425)

* Update installation.rst

* minor fixes to encryption.rst

instruct user to set `HISTIGNORE` while maintaining their existing `HISTIGNORE`
minor whitespace change

docs/encryption.rst

@@ -30,7 +30,7 @@ A note on security
 
 While jrnl follows best practises, true security is an illusion. Specifically, jrnl will leave traces in your memory and your shell history -- it's meant to keep journals secure in transit, for example when storing it on an `untrusted <http://techcrunch.com/2014/04/09/condoleezza-rice-joins-dropboxs-board/>`_ services such as Dropbox. If you're concerned about security, disable history logging for journal in your ``.bashrc`` ::
 
-    HISTIGNORE="jrnl *"
+    HISTIGNORE="$HISTIGNORE:jrnl *"
 
 If you are using zsh instead of bash, you can get the same behaviour adding this to your ``zshrc`` ::
 

docs/installation.rst

@@ -24,7 +24,7 @@ to install the dependencies for encrypting journals as well.
 
    Installing the encryption library, `pycrypto`, requires a `gcc` compiler. For this reason, jrnl will not install `pycrypto` unless explicitly told so like this. You can `install PyCrypto manually <https://www.dlitz.net/software/pycrypto/>`_ first or install it with ``pip install pycrypto`` if you have a `gcc` compiler.
 
-   Also note that when using zsh, you the correct syntax is ``pip install "jrnl[encrypted]"`` (note the quotes).
+   Also note that when using zsh, the correct syntax is ``pip install "jrnl[encrypted]"`` (note the quotes).
 
 The first time you run ``jrnl`` you will be asked where your journal file should be created and whether you wish to encrypt it.