Merge branch 'master' into fix_wiki_img_links

Author: BartMassey

microbit/src/02-requirements/README.md

@@ -52,7 +52,7 @@ whether a high level crate already exists, like the [`nrf52-hal`], for your deve
 somewhere. You can look through the [Awesome Embedded Rust HAL list] for your microcontroller,
 if you intend to use a different one.
 
-[`nrf52-hal`]: https://docs.rs/nrf52-hal
+[`nrf52-hal`]: https://github.com/nrf-rs/nrf-hal
 [Awesome Embedded Rust HAL list]: https://github.com/rust-embedded/awesome-embedded-rust#hal-implementation-crates
 
 With a different development board, this text would lose most if not all its beginner friendliness

microbit/src/04-meet-your-hardware/microbit-v1.md

@@ -24,7 +24,7 @@ dedicated to explaining the weird chip naming. Here we learn that:
 [QFN48]: https://en.wikipedia.org/wiki/Flat_no-leads_package
 [Nordic Semiconductor]: https://www.nordicsemi.com/
 [product page]: https://www.nordicsemi.com/products/nrf51822
-[product specification]: https://infocenter.nordicsemi.com/pdf/nRF51822_PS_v3.3.pdf
+[product specification]: https://docs.nordicsemi.com/bundle/nRF51822_PS/resource/nRF51822_PS_v3.3.pdf
 
 - The `N51` is the MCU's series, indicating that there are other `nRF51` MCUs
 - The `822` is the part code

microbit/src/04-meet-your-hardware/microbit-v2.md

@@ -24,7 +24,7 @@ dedicated to explaining the weird chip naming. Here we learn that:
 [aQFN73]: https://en.wikipedia.org/wiki/Flat_no-leads_package
 [Nordic Semiconductor]: https://www.nordicsemi.com/
 [product page]: https://www.nordicsemi.com/products/nrf52833
-[product specification]: https://infocenter.nordicsemi.com/pdf/nRF52833_PS_v1.3.pdf
+[product specification]: https://docs.nordicsemi.com/bundle/nRF52833-PS/resource/nRF52833_PS_v1.3.pdf
 
 - The `N52` is the MCU's series, indicating that there are other `nRF52` MCUs
 - The `833` is the part code

microbit/src/05-led-roulette/debug-it.md

@@ -55,7 +55,7 @@ Remote debugging using :1337
 ```
 
 Next what we want to do is get to the main function of our program.
-We will do this by first setting a breakpoint there and the continuing
+We will do this by first setting a breakpoint there and then continuing
 program execution until we hit the breakpoint:
 
 ```