From 0e34d44e2bd8c66a101408a0fa3f1d2f1924d286 Mon Sep 17 00:00:00 2001
From: bop <59298999+boooooooop@users.noreply.github.com>
Date: Wed, 4 Mar 2026 08:27:00 +0100
Subject: [PATCH 1/2] Punctuation & spelling

---
 .../2_choosing_your_ide_vscode.md                | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/articles/getting_started/2_choosing_your_ide_vscode.md b/articles/getting_started/2_choosing_your_ide_vscode.md
index f4e63b98..ed7e27fb 100644
--- a/articles/getting_started/2_choosing_your_ide_vscode.md
+++ b/articles/getting_started/2_choosing_your_ide_vscode.md
@@ -78,9 +78,9 @@ The official Microsoft version includes proprietary features like settings sync,
 
 ## Setting up VS Code for development with MonoGame
 
-1. Open Visual Studio Code
-1. Open up its terminal window (`Ctrl` + `` ` ``)
-1. Run the following command to install MonoGame Templates
+1. Open Visual Studio Code.
+1. Open up its terminal window (`Ctrl` + `` ` ``).
+1. Run the following command to install MonoGame Templates:
 
     ```sh
     dotnet new install MonoGame.Templates.CSharp
@@ -141,15 +141,15 @@ The .NET MAUI extension adds features for building mobile apps, including:
 
 ## Creating a new MonoGame project
 
-1. Open up an empty folder in Visual Studio Code
-2. Open up its terminal window (`Ctrl` + `` ` ``)
+1. Open up an empty folder in Visual Studio Code.
+2. Open up its terminal window (`Ctrl` + `` ` ``).
 3. Run the following command to create an empty project for desktop platforms:
 
     ```sh
     dotnet new mgdesktopgl
     ```
 
-4. Once the files are created, open up the `Game1.cs` file and wait a second for the C# extension to load
+4. Once the files are created, open up the `Game1.cs` file and wait a second for the C# extension to load.
 5. You can now press F5, select C# and then your projects name if Visual Studio Code asks you, and it should start up your brand new game!
 
 ## Update Project Tool references
@@ -159,8 +159,8 @@ The MonoGame Content Editor (MGCB) it a tool delivered through NuGet for your pr
 Once you have created your project you should run the following terminal/command-line command to ensure the tool (and the pipeline) is setup and read for your project:
 
 ```dotnetcli
-    dotnet tool restore
+dotnet tool restore
 ```
 
 > [!NOTE]
-> If you ever change the version of the tools or want to upgrade them by editing the `dotnet-tools.json` configuration, you MUST run this command again to update te tools.
+> If you ever change the version of the tools or want to upgrade them by editing the `dotnet-tools.json` configuration, you MUST run this command again to update the tools.

From 20d518ef0a42a136d06012917781cc19ee438e1f Mon Sep 17 00:00:00 2001
From: bop <59298999+boooooooop@users.noreply.github.com>
Date: Fri, 6 Mar 2026 13:36:07 +0100
Subject: [PATCH 2/2] Update mgcb_editor.md

---
 articles/getting_started/tools/mgcb_editor.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/articles/getting_started/tools/mgcb_editor.md b/articles/getting_started/tools/mgcb_editor.md
index c334b339..fa4078c3 100644
--- a/articles/getting_started/tools/mgcb_editor.md
+++ b/articles/getting_started/tools/mgcb_editor.md
@@ -29,7 +29,7 @@ dotnet mgcb-editor
 ```
 
 > [!NOTE]
-> You will need to buid the project at least once in order for the .NET system to download and register the tool with your project utilizing the `dotnet-tools.json` configuration file located in the `.config` folder, or use the `dotnet tool restore` command shown below.
+> You will need to build the project at least once in order for the .NET system to download and register the tool with your project utilizing the `dotnet-tools.json` configuration file located in the `.config` folder, or use the `dotnet tool restore` command shown below.
 >
 > ```sh
 > dotnet tool restore