docs (pt2): update getting-started to hardware.inc v5.3.0

Author: hlatourette

src/part2/getting-started.md

@@ -6,7 +6,7 @@ We will make a [Breakout](https://en.wikipedia.org/wiki/Breakout_%28video_game%2
 
 Open a terminal and make a new directory (`mkdir unbricked`), and then enter it (`cd unbricked`), just like you did for ["Hello, world!"](../part1/hello_world.md).
 
-Start by creating a file called `main.asm`, and include `hardware.inc` in your code.
+Start by creating a file called `main.asm`, and include [`hardware.inc`](https://raw.githubusercontent.com/gbdev/hardware.inc/v5.3.0/hardware.inc) in your code.
 
 ```rgbasm,linenos,start={{#line_no_of "" ../../unbricked/getting-started/main.asm:includes}}
 {{#include ../../unbricked/getting-started/main.asm:includes}}
@@ -23,9 +23,9 @@ But, having to remember all the numbers ([non-exhaustive list](https://gbdev.io/
 
 :::tip
 
-Don't worry if this flew over your head, we'll see an example below with `rLCDC` and `LCDCF_ON`.
+Don't worry if this flew over your head, we'll see an example below with `rLCDC` and `LCDC_ON`.
 
-By the way, the `r` stands for "register", and the `F` in `LCDCF` stands for "flag".
+By the way, the `r` stands for "register".
 
 :::
 
@@ -78,7 +78,7 @@ But there is more to them than meets the eye, so we will start tackling them muc
 :::
 
 Finally, let's turn the screen back on, and set a [background palette](../part1/palettes.md).
-Rather than writing the non-descript number `%10000001` (or $81 or 129, to taste), we make use of two constants graciously provided by `hardware.inc`: `LCDCF_ON` and `LCDCF_BGON`.
+Rather than writing the non-descript number `%10000001` (or $81 or 129, to taste), we make use of two constants graciously provided by `hardware.inc`: `LCDC_ON` and `LCDC_BG_ON`.
 When written to [`rLCDC`](https://gbdev.io/pandocs/LCDC), the former causes the PPU and screen to turn back on, and the latter enables the background to be drawn.
 (There are other elements that could be drawn, but we are not enabling them yet.)
 Combining these constants must be done using `|`, the *binary "or"* operator; we'll see why later.