From a922418443f7aa754f7eee105fd10238c2ba5e6c Mon Sep 17 00:00:00 2001
From: Flaviu Tamas <tamasflaviu@gmail.com>
Date: Sun, 18 Jan 2015 11:37:23 -0500
Subject: [PATCH] Fix readme formatting

---
 README.asciidoc | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/README.asciidoc b/README.asciidoc
index 94cf2dc6f2..519df2238a 100644
--- a/README.asciidoc
+++ b/README.asciidoc
@@ -51,13 +51,13 @@ passed in order to encourage readable expressions, so `[0-9]+` is equivalent to
  - `<lf>` - newlines are separated by `\n` (UNIX default)
  - `<anycrlf>` - newlines are separated by any of the above
  - `<any>` - newlines are separated by any of the above and Unicode newlines:
-   [quote, , man pcre]
-   ____
-   single characters VT (vertical tab, U+000B), FF (form feed, U+000C), NEL
-   (next line, U+0085), LS (line separator, U+2028), and PS (paragraph
-   separator, U+2029). For the 8-bit library, the last two are recognized
-   only in UTF-8 mode.
-   ____
+[quote, , man pcre]
+____
+single characters VT (vertical tab, U+000B), FF (form feed, U+000C), NEL
+(next line, U+0085), LS (line separator, U+2028), and PS (paragraph
+separator, U+2029). For the 8-bit library, the last two are recognized
+only in UTF-8 mode.
+____
  - `<bsr_anycrlf>` - `\R` matches CR, LF, or CRLF
  - `<bsr_unicode>` - `\R` matches any unicode newline
  - `<js>` - Javascript compatibility