[elpa] 329/352: Add another empty lines before headings

[Stefan Monnier]

monnier pushed a commit to branch master
in repository elpa.

commit 78ce9a96b7925ae46d963698d4f12659c8f29188
Author: Teemu Likonen <address@hidden>
Date:   Thu Apr 18 16:15:21 2013 +0300

    Add another empty lines before headings
---
 README.md |    7 +++++++
 1 files changed, 7 insertions(+), 0 deletions(-)

diff --git a/README.md b/README.md
index 4bad813..7763ca4 100644
--- a/README.md
+++ b/README.md
@@ -21,6 +21,7 @@ standard output can be used. Wcheck mode sends parts of 
buffer's content
 to an external program or an Emacs Lisp function and, based on their
 output, decides if some parts of text should be marked in the buffer.
 
+
 Features
 --------
 
@@ -60,6 +61,7 @@ though. Wcheck mode can be configured to find almost any kind 
of text
 elements from buffer, mark them, and offer any kind of actions for
 marked text.
 
+
 How does it compare to other spell-checkers?
 --------------------------------------------
 
@@ -81,6 +83,7 @@ It has more configuration possibilities than other 
spell-checkers and
 the on-the-fly checker performs very well. It's a true real-time
 checker.
 
+
 Install
 -------
 
@@ -98,6 +101,7 @@ and add the following lines to Emacs's initialization file 
(`~/.emacs`):
     (autoload 'wcheck-jump-backward "wcheck-mode"
       "Move point backward to previous marked text area." t)
 
+
 Configuration and basic usage
 -----------------------------
 
@@ -128,6 +132,7 @@ buffer position. Programmers can use it to perform any kind 
of actions
 for marked text. Function `wcheck-query-language-data` can be used for
 querying effective configuration data for any language.
 
+
 Examples
 --------
 
@@ -307,6 +312,7 @@ Note that detecting all valid email addresses is difficult 
and a much
 more advanced parser is needed for that. Feel free to replace the
 detection function with a better one.
 
+
 The source code repository
 --------------------------
 
@@ -316,6 +322,7 @@ The branch named _master_ is the release branch and it 
should always be
 safe to use. New features and experimental code are developed in other
 branches and possibly merged to _master_ when they are ready.
 
+
 Copyright and license
 ---------------------