X-Git-Url: https://git.ralfj.de/web.git/blobdiff_plain/6903be992ceca828b3117d0ff83d374710d81e68..e57815525168969b10be94812fc3e53745542fcc:/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 08f9bf5..e3ccfd1 100644
--- a/ralf/_posts/2017-08-11-types-as-contracts-evaluation.md
+++ b/ralf/_posts/2017-08-11-types-as-contracts-evaluation.md
@@ -260,12 +260,12 @@ 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 :)
 
-As always, please comment with your thoughts on the topic.
+As always, please [comment](https://internals.rust-lang.org/t/https-www-ralfj-de-blog-2017-08-11-types-as-contracts-evaluation-html/5753) with your thoughts on the topic.
 I am particularly curious about what kind of test cases you are throwing at miri, and how it is doing!
 
-**Update**: I added a proposal for how to fix the `Arc` problem.
+**Update:** I added a proposal for how to fix the `Arc` problem. **/Update**