summaryrefslogtreecommitdiffstats
path: root/llvm/docs/tutorial/OCamlLangImpl6.rst
diff options
context:
space:
mode:
Diffstat (limited to 'llvm/docs/tutorial/OCamlLangImpl6.rst')
-rw-r--r--llvm/docs/tutorial/OCamlLangImpl6.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/llvm/docs/tutorial/OCamlLangImpl6.rst b/llvm/docs/tutorial/OCamlLangImpl6.rst
index 36bffa8e969..a3ae11fd7e5 100644
--- a/llvm/docs/tutorial/OCamlLangImpl6.rst
+++ b/llvm/docs/tutorial/OCamlLangImpl6.rst
@@ -24,7 +24,7 @@ is good or bad. In this tutorial we'll assume that it is okay to use
this as a way to show some interesting parsing techniques.
At the end of this tutorial, we'll run through an example Kaleidoscope
-application that `renders the Mandelbrot set <#example>`_. This gives an
+application that `renders the Mandelbrot set <#kicking-the-tires>`_. This gives an
example of what you can build with Kaleidoscope and its feature set.
User-defined Operators: the Idea
@@ -108,7 +108,7 @@ keywords:
| "unary" -> [< 'Token.Unary; stream >]
This just adds lexer support for the unary and binary keywords, like we
-did in `previous chapters <OCamlLangImpl5.html#iflexer>`_. One nice
+did in `previous chapters <OCamlLangImpl5.html#lexer-extensions-for-if-then-else>`_. One nice
thing about our current AST, is that we represent binary operators with
full generalisation by using their ASCII code as the opcode. For our
extended operators, we'll use this same representation, so we don't need
OpenPOWER on IntegriCloud