Made all hotlinked images local. (#597)

Author: Kestrer

posts/2016-05-16-rust-at-one-year.md

@@ -20,7 +20,7 @@ having fun doing it.
 
 And yesterday, Rust turned one year old.
 
-<img src="http://rustcamp.com/images/after/cupcakes.jpg" height="300px" width="300px">
+<img src="/images/2016-05-16-rust-at-one-year/cupcakes.jpg" height="300px" width="300px">
 
 ### Rust in numbers
 

posts/inside-rust/2019-10-03-Keeping-secure-with-cargo-audit-0.9.md

@@ -27,7 +27,7 @@ Previously, when `cargo-audit` found a vulnerability in a project, it would disp
 
 The latest release prints an inverse dependency tree (ala the excellent [cargo-tree](https://github.com/sfackler/cargo-tree) crate) for each advisory showing how a vulnerable dependency is included in your project:
 
-![cargo audit with dependency tree](https://raw.githubusercontent.com/RustSec/cargo-audit/a840f7b/screenshot.png)
+![cargo audit with dependency tree](/images/inside-rust/2019-10-03-Keeping-secure-with-cargo-audio-0.9/cargo-audit-dependency-tree.png)
 
 In future versions of `cargo-audit` we [hope to add a `cargo audit fix` command](https://github.com/RustSec/cargo-audit/issues/23) ala `npm audit fix` which can either automatically update the necessary dependencies or provide instructions on how to do so. If that feature interests you and you'd like to contribute, [we're looking for help](https://github.com/RustSec/cargo-audit/issues/23)!
 

posts/inside-rust/2020-01-23-Introducing-cargo-audit-fix-and-more.md

@@ -22,7 +22,7 @@ $ cargo install cargo-audit --features=fix
 
 This will perform the same audit process as `cargo audit` initially, and then attempt to apply fixes to your `Cargo.toml`:
 
-![cargo audit fix screenshot](https://raw.githubusercontent.com/RustSec/cargo-audit/c857beb/img/screenshot-fix.png)
+![cargo audit fix screenshot](/images/inside-rust/2020-01-23-Introducing-cargo-audit-fix-and-more/cargo-audit-fix.png)
 
 Under the hood, it uses [cargo-edit](https://github.com/killercup/cargo-edit) (as a library) to perform modifications to your `Cargo.toml` file, using the fixed version requirements listed in the advisory to try to perform an automatic upgrade to a non-vulnerable version of a dependency for each advisory.