X-Git-Url: https://git.ralfj.de/web.git/blobdiff_plain/e9e7f558e195c0992d8b37bcbaa112b01694cc67..ef943c44bdd6f451b65b49b81f17a5a339aad5ec:/personal/_posts/2017-07-14-undefined-behavior.md?ds=sidebyside

diff --git a/personal/_posts/2017-07-14-undefined-behavior.md b/personal/_posts/2017-07-14-undefined-behavior.md
index 732117a..77e7315 100644
--- a/personal/_posts/2017-07-14-undefined-behavior.md
+++ b/personal/_posts/2017-07-14-undefined-behavior.md
@@ -39,7 +39,7 @@ This could be the end of the game:  No alias information, no way to verify our a
 
 ## Shifting responsibility
 
-However, it turns out that compilers writers consider these optimizations important enough that they came up with an alternative solution:
+However, it turns out that compiler writers consider these optimizations important enough that they came up with an alternative solution:
 Instead of having the compiler verify such assumptions, they declared the programmer responsible.
 
 For example, the C standard says that memory accesses have to happen with the right "effective type":  If data was stored with a `float` pointer, it must not be read with an `int` pointer.
@@ -88,3 +88,5 @@ It is with such considerations in my mind that I have previously written about [
 
 Coming up next on this channel:  During my [internship]({{ site.baseurl }}{% post_url 2017-05-23-internship-starting %}), I am working on such a specification.
 My ideas are concrete enough now that I can write down a draft, which I will share with the world to see what the world thinks about it.
+
+**Uodate:** [Writing down has happened]({{ site.baseurl }}{% post_url 2017-07-17-types-as-contracts %}).