Use new book links instead of the old second-edition ones

src/cargo/test.md

@@ -2,7 +2,7 @@
 
 As we know testing is integral to any piece of software! Rust has first-class
 support for unit and integration testing ([see this
-chapter](https://doc.rust-lang.org/book/second-edition/ch11-00-testing.html) in
+chapter](https://doc.rust-lang.org/book/ch11-00-testing.html) in
 TRPL).
 
 From the testing chapters linked above, we see how to write unit tests and

src/error.md

@@ -28,4 +28,4 @@ do that unless it's a test or quick prototype).
 For a more rigorous discussion of error handling, refer to the error
 handling section in the [official book][book].
 
-[book]: https://doc.rust-lang.org/book/second-edition/ch09-00-error-handling.html
+[book]: https://doc.rust-lang.org/book/ch09-00-error-handling.html

src/error/multiple_error_types/boxing_errors.md

@@ -67,6 +67,6 @@ fn main() {
 [Dynamic dispatch][dynamic_dispatch] and [`Error` trait][error]
 
 [box]: https://doc.rust-lang.org/std/boxed/struct.Box.html
-[dynamic_dispatch]: https://doc.rust-lang.org/book/second-edition/ch17-02-trait-objects.html#trait-objects-perform-dynamic-dispatch
+[dynamic_dispatch]: https://doc.rust-lang.org/book/ch17-02-trait-objects.html#trait-objects-perform-dynamic-dispatch
 [error]: https://doc.rust-lang.org/std/error/trait.Error.html
 [from]: https://doc.rust-lang.org/std/convert/trait.From.html

src/scope/lifetime/elision.md

@@ -40,4 +40,4 @@ fn main() {
 
 [elision][elision]
 
-[elision]: https://doc.rust-lang.org/book/second-edition/ch10-03-lifetime-syntax.html#lifetime-elision
+[elision]: https://doc.rust-lang.org/book/ch10-03-lifetime-syntax.html#lifetime-elision

src/std_misc/threads/testcase_mapreduce.md

@@ -143,10 +143,10 @@ defined by a static constant at the beginning of the program.
 [thread]: std_misc/threads.html
 [vectors]: std/vec.html
 [iterators]: trait/iter.html
-[destructuring]: https://doc.rust-lang.org/book/second-edition/ch18-03-pattern-syntax.html#destructuring-to-break-apart-values
+[destructuring]: https://doc.rust-lang.org/book/ch18-03-pattern-syntax.html#destructuring-to-break-apart-values
 [closures]: fn/closures.html
 [move]: scope/move.html
-[move_closure]: https://doc.rust-lang.org/book/second-edition/ch13-01-closures.html#closures-can-capture-their-environment
+[move_closure]: https://doc.rust-lang.org/book/ch13-01-closures.html#closures-can-capture-their-environment
 [turbofish]: https://doc.rust-lang.org/std/iter/trait.Iterator.html#method.collect
 [unwrap]: error/option_unwrap.html
 [enumerate]: https://doc.rust-lang.org/book/loops.html#enumerate

src/testing.md

@@ -22,5 +22,5 @@ Also Rust has support for specifying additional dependencies for tests:
 [doc]: testing/doc_testing.html
 [integration]: testing/integration_testing.html
 [dev-dependencies]: testing/dev_dependencies.html
-[doc-testing]: https://doc.rust-lang.org/book/second-edition/ch11-00-testing.html
+[doc-testing]: https://doc.rust-lang.org/book/ch11-00-testing.html
 [doc-nursery]: https://rust-lang-nursery.github.io/api-guidelines/documentation.html

src/trait/ops.md

@@ -58,4 +58,4 @@ fn main() {
 
 [add]: https://doc.rust-lang.org/core/ops/trait.Add.html
 [ops]: https://doc.rust-lang.org/core/ops/
-[syntax]:https://doc.rust-lang.org/book/second-edition/appendix-02-operators.html
+[syntax]:https://doc.rust-lang.org/book/appendix-02-operators.html

src/unsafe.md

@@ -57,5 +57,5 @@ is of the correct type. If these invariants aren't upheld then the program's
 behaviour is undefined and there is no knowing what will happen.
 
 
-[unsafe]: https://doc.rust-lang.org/book/second-edition/ch19-01-unsafe-rust.html
+[unsafe]: https://doc.rust-lang.org/book/ch19-01-unsafe-rust.html
 [`std::slice::from_raw_parts`]: https://doc.rust-lang.org/std/slice/fn.from_raw_parts.html