Typo fixes

Author: meithecatte

src/sixth-panics.md

@@ -172,7 +172,7 @@ impl<T> LinkedList<T> {
 
 What can panic here? Well, knowing that honestly requires you to be a bit of a Rust expert, but thankfully, I am!
 
-The only places I can see in this code that *possibly* can panic (barring some absolute fuckery where someone recompiles the stdlib with debug_asserts enabled, but this is not something you should ever do) are Box::new (for out-of-memory conditions) and and the len arithmetic. All of that stuff is at the very end or very start of our methods, so yep, we're being nice and safe!
+The only places I can see in this code that *possibly* can panic (barring some absolute fuckery where someone recompiles the stdlib with debug_asserts enabled, but this is not something you should ever do) are `Box::new` (for out-of-memory conditions) and the len arithmetic. All of that stuff is at the very end or very start of our methods, so yep, we're being nice and safe!
 
-...were you surprised by Box::new being able to panic? Panics will get you like that! Try to preserve those invariants so you don't need to worry about it!
+...were you surprised by `Box::new` being able to panic? Panics will get you like that! Try to preserve those invariants so you don't need to worry about it!
 

src/sixth-variance.md

@@ -94,7 +94,7 @@ See it doesn't compile eith-- wait what??? Vec is magic??????
 
 Well, yes. But also, no. The magic was inside us all along, and that magic is ✨*Variance*✨.
 
-Read the [nomicon's chapter on subtyping]([Variance](https://doc.rust-lang.org/nightly/nomicon/subtyping.html) if you want all the gorey details, but basically subtyping *isn't* always safe. In particular it's not safe when mutable references are involved because you can use things like `mem::swap` and suddenly oops dangling pointers!
+Read the [nomicon's chapter on subtyping](https://doc.rust-lang.org/nightly/nomicon/subtyping.html) if you want all the gorey details, but basically subtyping *isn't* always safe. In particular it's not safe when mutable references are involved because you can use things like `mem::swap` and suddenly oops dangling pointers!
 
 Things that are "like mutable references" are *invariant* which means they block subtyping from happening on their generic parameters. So for safety, `&mut T` is invariant over T, and `Cell<T>` is invariant over T because `&Cell<T>` is basically just `&mut T` (because of interior mutability).