[clang-tools-extra] r278263 - [Documentation] Highlighting consistency and spelling mistake fix in Clang-tidy readability-else-after-return description.

[Eugene Zelenko via cfe-commits]

Author: eugenezelenko
Date: Wed Aug 10 13:30:14 2016
New Revision: 278263

URL: http://llvm.org/viewvc/llvm-project?rev=278263&view=rev
Log:
[Documentation] Highlighting consistency and spelling mistake fix in Clang-tidy readability-else-after-return description.

Modified:
    clang-tools-extra/trunk/docs/clang-tidy/checks/readability-else-after-return.rst

Modified: clang-tools-extra/trunk/docs/clang-tidy/checks/readability-else-after-return.rst
URL: http://llvm.org/viewvc/llvm-project/clang-tools-extra/trunk/docs/clang-tidy/checks/readability-else-after-return.rst?rev=278263&r1=278262&r2=278263&view=diff
==============================================================================
--- clang-tools-extra/trunk/docs/clang-tidy/checks/readability-else-after-return.rst (original)
+++ clang-tools-extra/trunk/docs/clang-tidy/checks/readability-else-after-return.rst Wed Aug 10 13:30:14 2016
@@ -6,8 +6,8 @@ readability-else-after-return
 `LLVM Coding Standards <http://llvm.org/docs/CodingStandards.html>`_ advises to
 reduce indentation where possible and where it makes understanding code easier.
 Early exit is one of the suggested enforcements of that. Please do not use
-`else` or `else if` after something that interrupts control flow - like
-`return`, `break`, `continue`, `throw`.
+``else`` or ``else if`` after something that interrupts control flow - like
+``return``, ``break``, ``continue``, ``throw``.
 
 The following piece of code illustrates how the check works. This piece of code:
 
@@ -60,5 +60,5 @@ Would be transformed into:
     }
 
 
-This checks helps to enforce this `Coding Standars recommendation
+This checks helps to enforce this `Coding Standards recommendation
 <http://llvm.org/docs/CodingStandards.html#don-t-use-else-after-a-return>`_.