[llvm] r333902 - [ReleaseNotes] Formatting fixes.

[Nicola Zaghen via llvm-commits]

Author: nzaghen
Date: Mon Jun  4 07:40:34 2018
New Revision: 333902

URL: http://llvm.org/viewvc/llvm-project?rev=333902&view=rev
Log:
[ReleaseNotes] Formatting fixes.


Modified:
    llvm/trunk/docs/ReleaseNotes.rst

Modified: llvm/trunk/docs/ReleaseNotes.rst
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/ReleaseNotes.rst?rev=333902&r1=333901&r2=333902&view=diff
==============================================================================
--- llvm/trunk/docs/ReleaseNotes.rst (original)
+++ llvm/trunk/docs/ReleaseNotes.rst Mon Jun  4 07:40:34 2018
@@ -88,19 +88,14 @@ Non-comprehensive list of changes in thi
   ``llvm/Config/llvm-config.h``.  If you used this macro, use the compiler-set
   ``_WIN32`` instead which is set exactly when ``LLVM_ON_WIN32`` used to be set.
 
-* The ``DEBUG`` macro has been renamed to ``LLVM_DEBUG``. The interface remains
-  the same.  If you used this macro you need to migrate to the new one, you can
-  do this with the following bash command:
+* The ``DEBUG`` macro has been renamed to ``LLVM_DEBUG``, the interface remains
+  the same.  If you used this macro you need to migrate to the new one.
+  You should also clang-format your code to make it easier to integrate future
+  changes locally.  This can be done with the following bash commands:
 
 .. code-block:: bash
 
     git grep -l 'DEBUG' | xargs perl -pi -e 's/\bDEBUG\s?\(/LLVM_DEBUG(/g'
-
-  Additionally, you can clang-format your code to make it easier to integrate
-  future changes locally.  This can be done with the following bash command:
-
-.. code-block:: bash
-
     git diff -U0 master | ../clang/tools/clang-format/clang-format-diff.py -i -p1 -style LLVM
 
 * Note..