[llvm] 7aa982a - [LoopTerminology][NFC] Fix formatting typo

[Stefanos Baziotis via llvm-commits]

Author: Stefanos Baziotis
Date: 2020-09-23T22:53:05+03:00
New Revision: 7aa982a57ce0dbf8fdbd276004615ddcf729c906

URL: https://github.com/llvm/llvm-project/commit/7aa982a57ce0dbf8fdbd276004615ddcf729c906
DIFF: https://github.com/llvm/llvm-project/commit/7aa982a57ce0dbf8fdbd276004615ddcf729c906.diff

LOG: [LoopTerminology][NFC] Fix formatting typo

Added: 
    

Modified: 
    llvm/docs/LoopTerminology.rst

Removed: 
    


################################################################################
diff  --git a/llvm/docs/LoopTerminology.rst b/llvm/docs/LoopTerminology.rst
index fc461986cb5b..0870ab9fcac1 100644
--- a/llvm/docs/LoopTerminology.rst
+++ b/llvm/docs/LoopTerminology.rst
@@ -291,7 +291,7 @@ In general, it's easier to use SCEV in loops that are in LCSSA form.
 The evolution of a scalar (loop-variant) expression that
 SCEV can analyze is, by definition, relative to a loop.
 An expression is represented in LLVM by an
-`llvm::Instruction <https://llvm.org/doxygen/classllvm_1_1Instruction.html>`.
+`llvm::Instruction <https://llvm.org/doxygen/classllvm_1_1Instruction.html>`_.
 If the expression is inside two (or more) loops (which can only
 happen if the loops are nested, like in the example above) and you want
 to get an analysis of its evolution (from SCEV),