Fixed more broken URLs

adamgreen · adamgreen · commit e78a7d3acfca · 2018-10-30T20:41:39.000-07:00
After switching to relative URLs, linkchecker still encountered
some broken links. This commit fixes those broken links and now
the only broken links detected are in print.html itself. I will
work on fixing those in a later commit.

I also renamed some URLs from .html extensions to .md extensions
since they get renamed to .html by mdbook and it allows GitHub
renderings of these pages to end up going to the correct place
when you click on the links. They work in VSCode preview as well.
diff --git a/src/03-setup/linux.md b/src/03-setup/linux.md
@@ -115,4 +115,4 @@ If you had any board plugged to your laptop, unplug them and then plug them in a
 
 Now, go to the [next section].
 
-[next section]: /03-setup/verify.html
+[next section]: verify.md
diff --git a/src/03-setup/macos.md b/src/03-setup/macos.md
@@ -15,4 +15,4 @@ Caskroom/tap` first and try again.
 
 That's all! Go to the [next section].
 
-[next section]: /03-setup/verify.html
+[next section]: verify.md
diff --git a/src/03-setup/verify.md b/src/03-setup/verify.md
@@ -29,7 +29,7 @@ crw-rw-rw- 1 root root 189, 20 Sep 13 00:00 /dev/bus/usb/003/004
 The permissions should be `crw-rw-rw-`. If it's not ... then check your [udev
 rules] and try re-loading them with:
 
-[udev rules]: /03-setup/linux.html#udev%20rules
+[udev rules]: linux.md#udev-rules
 
 ``` console
 $ sudo udevadm control --reload-rules
@@ -104,7 +104,7 @@ Info : stm32f3x.cpu: hardware has 6 breakpoints, 4 watchpoints
 
 (If you don't ... then check the [general troubleshooting] instructions.)
 
-[general troubleshooting]: /appendix/1-general-troubleshooting/README.html
+[general troubleshooting]: ../appendix/1-general-troubleshooting/index.html
 
 `openocd` will block the terminal. That's fine.
 
diff --git a/src/03-setup/windows.md b/src/03-setup/windows.md
@@ -47,4 +47,4 @@ instructions and make sure you install the right (32-bit or 64-bit) version of t
 
 That's all! Go to the [next section].
 
-[next section]: /03-setup/verify.html
+[next section]: verify.md
diff --git a/src/05-led-roulette/debug-it.md b/src/05-led-roulette/debug-it.md
@@ -39,7 +39,7 @@ mode, on the GDB shell enter the following command:
 > **NOTE** Apologies Windows users. The GDB shipped with the GNU ARM Embedded Toolchain doesn't
 > support this TUI mode `:-(`.
 
-![GDB session](/assets/gdb-layout-src.png "GDB TUI")
+![GDB session](../assets/gdb-layout-src.png "GDB TUI")
 
 At any point you can leave the TUI mode using the following command:
 
@@ -118,7 +118,7 @@ source code view later by issuing the `layout src` command again.
 (gdb) layout asm
 ```
 
-![GDB session](/assets/gdb-layout-asm.png "GDB disassemble")
+![GDB session](../assets/gdb-layout-asm.png "GDB disassemble")
 
 If you are not using the TUI mode, you can use the `disassemble /m` command to disassemble the
 program around the line you are currently at.
diff --git a/src/05-led-roulette/flash-it.md b/src/05-led-roulette/flash-it.md
@@ -29,7 +29,7 @@ $ openocd \
 > **NOTE** Older revisions of the board need to pass slightly different arguments to
 > `openocd`. Review [this section] for the details.
 
-[this section]: /03-setup/verify.html#First%20OpenOCD%20connection
+[this section]: ../03-setup/verify.md#first-openocd-connection
 
 The program will block; leave that terminal open.
 
diff --git a/src/06-hello-world/README.md b/src/06-hello-world/README.md
@@ -46,7 +46,7 @@ To retrieve the original string, OpenOCD's output file will have to be parsed. W
 
 You should have already installed the `itmdump` program during the [installation chapter].
 
-[installation chapter]: /03-setup/README.html#itmdump
+[installation chapter]: ../03-setup/index.html#itmdump
 
 In a new terminal, run this command inside the `/tmp` directory, if you are using a *nix OS, or from
 within the `%TEMP%` directory, if you are running Windows. This should be the same directory from
diff --git a/src/10-serial-communication/README.md b/src/10-serial-communication/README.md
@@ -47,5 +47,5 @@ will see the microcontroller as a virtual serial device.
 Now, let's get familiar with the serial module and the serial communication tools that your OS
 offers. Pick a route:
 
-- [*nix](/10-serial-communication/nix-tooling.html)
-- [Windows](/10-serial-communication/windows-tooling.html)
+- [*nix](nix-tooling.md)
+- [Windows](windows-tooling.md)
diff --git a/src/12-bluetooth-setup/README.md b/src/12-bluetooth-setup/README.md
@@ -33,4 +33,4 @@ is 1234.
 
 Linux users will have to follow (some of) [these instructions].
 
-[these instructions]: /12-bluetooth-setup/linux.html
+[these instructions]: linux.md
diff --git a/src/12-bluetooth-setup/linux.md b/src/12-bluetooth-setup/linux.md
@@ -3,7 +3,7 @@
 If you have a graphical Bluetooth manager, you can use that to pair your laptop to the Bluetooth
 module and skip most of these steps. You'll probably still have to [this step] though.
 
-[this step]: /12-bluetooth-setup/linux.html#rfcomm%20device
+[this step]: #rfcomm-device
 
 ## Power up
 
diff --git a/src/13-serial-over-bluetooth/README.md b/src/13-serial-over-bluetooth/README.md
@@ -22,4 +22,4 @@ Recommended steps to wire this up:
 And that's it! You should be able to run all the programs you wrote in [section 11] without
 modification! Just make sure you open the right serial device / COM port.
 
-[section 11]: /11-usart/README.html
+[section 11]: ../11-usart/index.html
diff --git a/src/README.md b/src/README.md
@@ -70,7 +70,7 @@ includes the list of [Frequently Asked Questions].
 
 <p align="center">
 <a href="http://integer32.com/">
-<img style="width: 50%" title="integer 32" src="/assets/integer32.svg">
+<img style="width: 50%" title="integer 32" src="assets/integer32.svg">
 </a>
 </p>
 
diff --git a/src/appendix/1-general-troubleshooting/README.md b/src/appendix/1-general-troubleshooting/README.md
@@ -27,8 +27,8 @@ in procedure 'ocd_bouncer'
 - Windows: You are probably missing the ST-LINK USB driver. Installation
   instructions [here].
 
-[these instructions]: /03-setup/linux.html#udev%20rules
-[here]: /03-setup/windows.html#ST-LINK%20USB%20driver
+[these instructions]: ../../03-setup/linux.md#udev-rules
+[here]: ../../03-setup/windows.md#st-link-usb-driver
 
 ### can't connect to OpenOCD - "Polling again in X00ms"
 

Original file line number	Diff line number	Diff line change
`@@ -115,4 +115,4 @@ If you had any board plugged to your laptop, unplug them and then plug them in a`
`115`	`115`
`116`	`116`	`Now, go to the [next section].`
`117`	`117`
`118`		`-[next section]: /03-setup/verify.html`
	`118`	`+[next section]: verify.md`
Original file line number	Diff line number	Diff line change
@@ -15,4 +15,4 @@ Caskroom/tap` first and try again.
`15`	`15`
`16`	`16`	`That's all! Go to the [next section].`
`17`	`17`
`18`		`-[next section]: /03-setup/verify.html`
	`18`	`+[next section]: verify.md`
Original file line number	Diff line number	Diff line change
`@@ -47,4 +47,4 @@ instructions and make sure you install the right (32-bit or 64-bit) version of t`
`47`	`47`
`48`	`48`	`That's all! Go to the [next section].`
`49`	`49`
`50`		`-[next section]: /03-setup/verify.html`
	`50`	`+[next section]: verify.md`
Original file line number	Diff line number	Diff line change
`@@ -33,4 +33,4 @@ is 1234.`
`33`	`33`
`34`	`34`	`Linux users will have to follow (some of) [these instructions].`
`35`	`35`
`36`		`-[these instructions]: /12-bluetooth-setup/linux.html`
	`36`	`+[these instructions]: linux.md`