[llvm] 3f3bda1 - [LoopTerminology] Minor fixes in loop rotation

[Stefanos Baziotis via llvm-commits]

Author: Stefanos Baziotis
Date: 2020-03-17T06:34:02+02:00
New Revision: 3f3bda1c372fe5aa662c8aa1477433440db74c4a

URL: https://github.com/llvm/llvm-project/commit/3f3bda1c372fe5aa662c8aa1477433440db74c4a
DIFF: https://github.com/llvm/llvm-project/commit/3f3bda1c372fe5aa662c8aa1477433440db74c4a.diff

LOG: [LoopTerminology] Minor fixes in loop rotation

Added: 
    

Modified: 
    llvm/docs/LoopTerminology.rst

Removed: 
    


################################################################################
diff  --git a/llvm/docs/LoopTerminology.rst b/llvm/docs/LoopTerminology.rst
index b3822e638d4c..ef0593419a46 100644
--- a/llvm/docs/LoopTerminology.rst
+++ b/llvm/docs/LoopTerminology.rst
@@ -220,7 +220,7 @@ It's important to understand the effect of loop rotation
 at the LLVM IR level. We follow with the previous examples
 in LLVM IR while also providing a graphical representation
 of the control-flow graphs (CFG). You can get the same graphical
-results by utilizing the `view-cfg <passes-view-cfg>` pass.
+results by utilizing the :ref:`view-cfg <passes-view-cfg>` pass.
 
 The initial **for** loop could be translated to:
 
@@ -277,7 +277,7 @@ it (by hand) to a do-while style loop.
 .. image:: ./loop-terminology-rotated-loop.png
   :width: 400 px
 
-Note a two things:
+Note two things:
 
 * The condition check was moved to the "bottom" of the loop, i.e.
   the latch. This is something that LoopRotate does by copying the header
@@ -320,7 +320,7 @@ This is how LoopRotate transforms this loop:
 
 The result is a little bit more complicated than we may expect
 because LoopRotate ensures that the loop is in
-`Loop Simplify Form <loop-terminology-loop-simplify>`
+:ref:`Loop Simplify Form <loop-terminology-loop-simplify>`
 after rotation.
 In this case, it inserted the %loop.preheader basic block so
 that the loop has a preheader and it introduced the %loop.exit