X-Git-Url: https://git.ralfj.de/web.git/blobdiff_plain/d28a28a2d4cd1c0cc00314282ecb91b913d1cfd9..cb643c4909f1de675491f8714d5812e55c1fb007:/ralf/_posts/2017-08-11-types-as-contracts-evaluation.md

diff --git a/ralf/_posts/2017-08-11-types-as-contracts-evaluation.md b/ralf/_posts/2017-08-11-types-as-contracts-evaluation.md
index 21721c4..edb2a45 100644
--- a/ralf/_posts/2017-08-11-types-as-contracts-evaluation.md
+++ b/ralf/_posts/2017-08-11-types-as-contracts-evaluation.md
@@ -260,7 +260,7 @@ Interestingly, the [discussion](https://internals.rust-lang.org/t/types-as-contr
 After all, we want miri to also detect UB related to e.g. illegal pointer arithmetic.
 These issues are far from settled, and I do have some interesting ideas here that I want so share with you.
 
-Finally, there is of course the discussion around how to handle raw pointers; I already talked in [§3](#22-unsafe-code) about some of the options that could be explored here.
+Finally, there is of course the discussion around how to handle raw pointers; I already talked in [§2.2](#22-unsafe-code) about some of the options that could be explored here.
 
 Unfortunately, today is the last day of my internship, so I will no longer be able to work on all of this full-time like I did the last three months.
 Still, I certainly intend to stay involved. This problem is way too interesting to just let it go :)