minor changes to README

.gitignore

@@ -67,6 +67,7 @@ local.properties
 # Byte-compiled / optimized / DLL files
 __pycache__/
 *.py[cod]
+.pypirc
 
 # C extensions
 *.so

README.rst

@@ -1,6 +1,6 @@
-=======================
-Django-CMS Reversion2**
-=======================
+=====================
+Django-CMS Reversion2
+=====================
 
 
 **Django-CMS Reversion2** is a plugin for **Django CMS** which aims to provide a revision system
@@ -9,12 +9,12 @@ Django-CMS Reversion2**
 Documentation
 =============
 
-Please feel free to contribute and help us to improve **Django-CMS Reversion2****.
+Please feel free to contribute and help us to improve **Django-CMS Reversion2**.
 
 Features
 --------
 
-These are the core features of **Django-CMS Layouter**:
+These are the core features of **Django-CMS Reversion2**:
 
 * Based on **django-reversion**
 * Revisions for page drafts in given language
@@ -30,8 +30,10 @@ No software is perfect, everyone's code sucks. Feel free to suggest, criticize a
 **Proper Frontend/CMS-Admin Integration** - Currently, we unregister django-cms' default PageAdmin and register our own
 PageAdmin. The overriding of PageAdmin appears necessary as it provides the only hook into Plugins being moved.
 
-**Parametrised Plugin-Registration** - AS of now, all CMSPlugin subclasses are registered with django-reversion without
+**Parametrised Plugin-Registration** - As of now, all CMSPlugin subclasses are registered with django-reversion without
 additional parameters ('follows', etc.). That means, model instances referred to via foreign key relation by a Plugin
 are currently not versioned and therefore not reverted. Such instances must still exist when reverting. Plugins having
 reverse foreign key relations (as is the case in many-to-many relations) are handled particularly badly. The delteion of
 the Plugin entails the deletion of the related model instance/m2m model instance.
+
+**Permission System** -