From 312dd49c0bf8204ddd2bdf8802e4e2e338929db2 Mon Sep 17 00:00:00 2001 From: Wouter J Date: Mon, 8 Oct 2012 10:13:16 +0300 Subject: [PATCH] Fixed typo in documentation/overview There shouldn't be any empty line after a commentfile, this is slipped in while proofreading. --- contributing/documentation/overview.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributing/documentation/overview.rst b/contributing/documentation/overview.rst index a24e13a34df..1eb1818e1a1 100644 --- a/contributing/documentation/overview.rst +++ b/contributing/documentation/overview.rst @@ -87,7 +87,7 @@ look and feel familiar, you should follow these rules: If we fold several lines: the description of the fold can be placed after the ``...`` If we fold only part of a line: the description can be placed before the line; * If useful, a ``codeblock`` should begin with a comment containing the filename - of the file in the code block. Place a blank line after this comment, + of the file in the code block. Don't place a blank line after this comment, unless the next line is also a comment; * You should put a ``$`` in front of every bash line; * We prefer the ``::`` shorthand over ``.. code-block:: php`` to begin a PHP