Merge branch 'feature/proof-run' of https://github.com/SimonDarksideJ/docs.monogame.github.io into feature/proof-run

Author: SimonDarksideJ

articles/tutorials/building_2d_games/03_the_game1_file/index.md

@@ -108,7 +108,7 @@ In the next chapter, you will start working with sprites and learn how to load a
 1. Can the `Game1` class be renamed or is it required to be called `Game1`
 
     :::question-answer
-    It is not a requirement that it be called `Game1`.  This is just the default name given to it by the templates when creating a new MonoGame game project.  However, you cannot change the name of the Base class `Game`, as this is a MonoGame construct.
+    It is not a requirement that it be called `Game1`.  This is just the default name given to it by the templates when creating a new MonoGame game project.  However, you cannot change the name of the *BASE* class `Game`, as this is a MonoGame construct.
     :::
 
 2. What is the [**SpriteBatch**](xref:Microsoft.Xna.Framework.Graphics.SpriteBatch) used for?

articles/tutorials/building_2d_games/16_working_with_spritefonts/index.md

@@ -65,7 +65,7 @@ Alternatively, for better portability across development environments, it is rec
 2. Place it in the **same folder** as the `.spritefont` file.
 
     > [!IMPORTANT]
-    > You place the font file in the **same folder** as the *.spritefont* file directly, not through the MGCB Editor.
+    > You place the font file in the **same folder** as the `.spritefont` file directly, not through the MGCB Editor.
 
 3. Update the `<FontName>` element to include the exact filename with extension.
 

articles/tutorials/building_2d_games/17_scenes/index.md

@@ -27,7 +27,7 @@ We will being by first defining the lifecycle of a scene that will be followed.
 In Chapter 03, you learned the basic [lifecycle of the `Game` class](../03_the_game1_file/index.md#exploring-the-game1-class).  To be consistent, we can borrow from this lifecycle and adapt it for our scenes. The order of operations for this lifecycle will be:
 
 1. A scene is created and set as the active scene.
-2. The initial active scene is initialized and content loaded.
+2. The first screen is made active and is initialized and content loaded.
 3. The active scene is updated and drawn each cycle.
 4. When transitioning to a new scene, or when the scene ends:
     1. The current scene is unloaded and disposed of.

articles/tutorials/building_2d_games/19_user_interface_fundamentals/index.md

@@ -62,7 +62,7 @@ Anchoring allows you to position UI elements relative to specific reference poin
 | :--------------------------------------------------------------------------------------: |
 |                  **Figure 19-1: Diagram showing common anchor points**                   |
 
-When you set an anchor point, the elements' position coordinates become relative to that anchor point.  For example with a "Right" anchor and an X value of -5, you element would position itself 5 pixels to the left of the parent's right edge, creating a consistent margin regardless of the parent's size, as demonstrated in the following diagram:
+When you set an anchor point, the elements' position coordinates become relative to that anchor point.  For example with a "Right" anchor and an X value of *-5*, you element would position itself *5 pixels* to the left of the parent's right edge, creating a consistent margin regardless of the parent's size, as demonstrated in the following diagram:
 
 | ![Figure 19-2: Diagram showing anchored element positioning relative to anchor regardless of parent size](./images/user_interface_anchor_positioning.svg) |
 | :-------------------------------------------------------------------------------------------------------------------------------------------------------: |
@@ -84,7 +84,7 @@ Creating accessible user interfaces is an essential aspect of inclusive game des
 
 ### Visual Accessibility
 
-- **Color contrast**: Ensure sufficient contrast between text and backgrounds
+- **Color contrast**: Ensure sufficient contrast between text and backgrounds.
 - **Use shapes**: Do not rely solely on color to convey important information; add shapes, patterns, or text labels as well.  For example, if displaying warning text, also use something such as the common warning sign ⚠️.
 - **Text size and scaling**: Allow players to adjust text size or implement a UI scaling option.
 - **Internationalization (i18n)**: Consider how your UI might be interpreted across different cultures and regions. Number formatting can vary significantly - some regions use periods for thousands separators (1.000.000) while others use commas (1,000,000). Control symbolism also differs culturally; for example, on console controllers, the Cross button typically means "Select" in Western regions but "Cancel" in Japan, with Circle having the opposite meaning.