Fix remaining dead links

blog/content/first-edition/extra/naked-exceptions/02-better-exception-messages/index.md

@@ -84,7 +84,7 @@ We're using [inline assembly] here to load the value from the `rsp` register int
 - After the third colon, the macro expects so called [clobbers]. We don't change any register values, so we leave it empty too.
 - The last block (after the 4th colon) specifies options. The `intel` option tells the compiler that our code is in Intel assembly syntax (instead of the default AT&T syntax).
 
-[clobbers]: https://doc.rust-lang.org/nightly/book/inline-assembly.html#clobbers
+[clobbers]: https://doc.rust-lang.org/1.10.0/book/inline-assembly.html#clobbers
 
 So the inline assembly loads the stack pointer value to `stack_frame` at the very beginning of our function. Thus we have a pointer to the exception stack frame and are able to pretty-print its `Debug` formatting through the `{:#?}` argument.
 

blog/content/first-edition/extra/naked-exceptions/03-returning-from-exceptions/index.md

@@ -250,7 +250,7 @@ However, there is a major difference between exceptions and function calls: A fu
 [Calling conventions] specify the details of a function call. For example, they specify where function parameters are placed (e.g. in registers or on the stack) and how results are returned. On x86_64 Linux, the following rules apply for C functions (specified in the [System V ABI]):
 
 [Calling conventions]: https://en.wikipedia.org/wiki/Calling_convention
-[System V ABI]: http://refspecs.linuxbase.org/elf/x86-64-abi-0.99.pdf
+[System V ABI]: http://refspecs.linuxbase.org/elf/gabi41.pdf
 
 - the first six integer arguments are passed in registers `rdi`, `rsi`, `rdx`, `rcx`, `r8`, `r9`
 - additional arguments are passed on the stack