From: Sebastian Annies <sebastian.annies@googlemail.com>
Date: Mon, 10 Oct 2011 18:10:49 +0000 (+0300)
Subject: corrected formatting
X-Git-Tag: 22.4~32^2~7
X-Git-Url: https://git.mdrn.pl/django-cas-provider.git/commitdiff_plain/36f224f3c3165adcfb0eb862938ea37d3ad1c0d9?ds=inline;hp=6eca12e4fa36ac42df3c071c49717db1db94e644

corrected formatting
---

diff --git a/README.rst b/README.rst
index 9720936..258d685 100644
--- a/README.rst
+++ b/README.rst
@@ -25,12 +25,17 @@ UPDATING FROM PREVIOUS VERSION
 I introduced south for DB schema migration. The schema from any previous version without south is 0001_initial.
 You will get an error:
 
- Running migrations for cas_provider:
-  - Migrating forwards to 0001_initial.
-  > cas_provider:0001_initial
- Traceback (most recent call last):
- ...
- django.db.utils.DatabaseError: relation "cas_provider_serviceticket" already exists
+    ``Running migrations for cas_provider:``
+
+    ``- Migrating forwards to 0001_initial.``
+
+    ``> cas_provider:0001_initial``
+
+    ``Traceback (most recent call last):``
+
+    ``...``
+
+    ``django.db.utils.DatabaseError: relation "cas_provider_serviceticket" already exists``
 
 to circumvent that problem you will need to fake the initial migration: