convert blockquote notes to admonition boxes in part2 and part3 (#161)

Author: avivace

src/part2/bcd.md

@@ -81,8 +81,12 @@ This should make the tile set look like this on start up:
 
 ![Screenshot of tile map with two zeroes added](../assets/part2/img/bcd-tilemap.png)
 
-> **Tip:** You can find the address in VRAM in your emulator's tile map viewer by selecting the tile and looking at the index.
-> The screenshot above is from emulucious.
+:::tip
+
+You can find the address in VRAM in your emulator's tile map viewer by selecting the tile and looking at the index.
+The screenshot above is from emulucious.
+
+:::
 
 Let's remember their positions by defining a constant for VRAM location of the 10s and the 1s at the top of our file, behind the other constants.
 

src/part3/collision.md

@@ -20,7 +20,11 @@ Here's an example of how to call this function:
 
 When checking for collision, we'll use that function twice. Once for the x-axis, and again for the y-axis.
 
-> NOTE: We don't need to test the y-axis if the x-axis fails. 
+:::tip Note
+
+We don't need to test the y-axis if the x-axis fails.
+
+:::
 
 The source code for that function looks like this:
 

src/part3/gameplay.md

@@ -64,7 +64,11 @@ Each object will use a random shadow OAM sprite. We need a way to keep track of
 
 When we reset our current Shadow OAM sprite address, we just set the "mLastOAMAddress" RAM variable to point to the first shadow OAM sprite. 
 
-> **NOTE:** We also keep a counter on how many shadow OAM sprites are used. In our "ResetOAMSpriteAddress" function, we'll reset that counter too.
+:::tip Note
+
+We also keep a counter on how many shadow OAM sprites are used. In our "ResetOAMSpriteAddress" function, we'll reset that counter too.
+
+:::
 
 ```rgbasm,linenos,start={{#line_no_of "" ../../galactic-armada/src/main/utils/sprites-utils.asm:reset-oam-sprite-address}}
 {{#include ../../galactic-armada/src/main/utils/sprites-utils.asm:reset-oam-sprite-address}}

src/part3/heads-up-interface.md

@@ -9,7 +9,12 @@ On our HUD, we'll draw both our score and our lives. We'll also use STAT interru
 
 The window is not enabled by default. We can enable the window using the `LCDC` register. RGBDS comes with constants that will help us. 
 
-> ⚠️ NOTE: The window can essentially be a copy of the background. The `LCDCF_WIN9C00|LCDCF_BG9800` portion makes the background and window use different tilemaps when drawn.
+:::warning Note
+
+The window can essentially be a copy of the background. The `LCDCF_WIN9C00|LCDCF_BG9800` portion makes the background and window use different tilemaps when drawn.
+
+:::
+
 There’s only one problem. Since the window is drawn between sprites and the background. Without any extra effort, our scrolling background tilemap will be covered by our window. In addition, our sprites will be drawn over our hud. For this, we’ll need STAT interrupts. Fore more information on STAT interrupts, check out the pandocs: [https://gbdev.io/pandocs/Interrupt_Sources.html](https://gbdev.io/pandocs/Interrupt_Sources.html)
 
 

src/part3/object-pools.md

@@ -38,7 +38,11 @@ The two object types that we need to loop through are Enemies and Bullets.
 
 ![BulletBytesVisualized.png](../assets/part3/img/BulletBytesVisualized.png)
 
-> ⚠️ **NOTE:** Scaled integers are used for only the y positions of bullets and enemies. Scaled Integers are a way to provide smooth “sub-pixel” movement. They only move vertically, so the x position can be 8-bit.
+:::warning Note
+
+Scaled integers are used for only the y positions of bullets and enemies. Scaled Integers are a way to provide smooth “sub-pixel” movement. They only move vertically, so the x position can be 8-bit.
+
+:::
 
 When looping through an object pool, we’ll check if an object is active. If it’s active, we’ll run the logic for that object. Otherwise, we’ll skip to the start of the next object’s bytes. 
 

src/part3/scrolling-background.md

@@ -3,7 +3,11 @@
 
 Scrolling the background is an easy task. However, for a SMOOTH slow scrolling background: scaled integers[^1] will be used.
 
->⚠️ Scaled Integers[^1] are a way to provide smooth “sub-pixel” movement. They are slightly more difficult to understand & implement than implementing a counter, but they provide smoother motion.
+:::warning Note
+
+Scaled Integers[^1] are a way to provide smooth “sub-pixel” movement. They are slightly more difficult to understand & implement than implementing a counter, but they provide smoother motion.
+
+:::
 
 ## Initializing the Background
 

src/part3/sprites-metasprites.md

@@ -26,7 +26,11 @@ An example of metasprite is the enemy ship:
 
 The Previous snippet draws two sprites. One that the object’s actual position, which uses tile 4 and 5. The second sprite is 8 pixels to the right, and uses tile 6 and 7
 
->⚠️ **NOTE**: Sprites are in 8x16 mode for this project.
+:::warning Note
+
+Sprites are in 8x16 mode for this project.
+
+:::
 
 I can later draw such metasprite by calling the "DrawMetasprite" function that
 

src/part3/the-player.md

@@ -7,7 +7,11 @@ Our player will have 3 variables:
 - wePlayerPositionY - a 16-bit scaled integer
 - wPlayerFlash - a 16-bit integer used when the player gets damaged
 
-> ⚠️ **NOTE**: The player can move vertically AND horizontally. So, unlike bullets and enemies, it’s x position is a 16-bit scaled integer.
+:::warning Note
+
+The player can move vertically AND horizontally. So, unlike bullets and enemies, its x position is a 16-bit scaled integer.
+
+:::
 
 These are declared at the top of the "src/main/states/gameplay/objects/player.asm" file
 
@@ -72,7 +76,11 @@ After we've potentially moved the player and/or shot a new bullet. We need to dr
     - If the result is less than 5, we'll stop flashing and draw our player metasprite.
     - Otherwise, if the first bit of the descaled "wPlayerFLash" variable is 1, we'll skip drawing the player.
 
-> ***NOTE:** The following resumes from where the "UpdatePlayer_HandleInput" label ended above.
+:::tip Note
+
+The following resumes from where the "UpdatePlayer_HandleInput" label ended above.
+
+:::
 
 ```rgbasm,linenos,start={{#line_no_of "" ../../galactic-armada/src/main/states/gameplay/objects/player.asm:player-update-flashing}}
 {{#include ../../galactic-armada/src/main/states/gameplay/objects/player.asm:player-update-flashing}}

src/part3/title-screen.md

@@ -36,7 +36,11 @@ In order to draw text in our game, we've created a function called "DrawTextTile
 
 The "DrawTitleScreen" function puts the tiles for our title screen graphic in VRAM, and draws its tilemap to the background:
 
-> **NOTE:** Because of the text font, we'll add an offset of 52 to our tilemap tiles. We've created a function that adds the 52 offset, since we'll need to do so more than once.
+:::tip Note
+
+Because of the text font, we'll add an offset of 52 to our tilemap tiles. We've created a function that adds the 52 offset, since we'll need to do so more than once.
+
+:::
 
 ```rgbasm,linenos,start={{#line_no_of "" ../../galactic-armada/src/main/states/title-screen/title-screen-state.asm:draw-title-screen}}
 {{#include ../../galactic-armada/src/main/states/title-screen/title-screen-state.asm:draw-title-screen}}