Skip to content

Commit ee9899b

Browse files
Spelling & punctuation for consistency (#250)
* Punctuation & spelling * Update mgcb_editor.md
1 parent 777a36b commit ee9899b

File tree

2 files changed

+9
-9
lines changed

2 files changed

+9
-9
lines changed

articles/getting_started/2_choosing_your_ide_vscode.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -78,9 +78,9 @@ The official Microsoft version includes proprietary features like settings sync,
7878

7979
## Setting up VS Code for development with MonoGame
8080

81-
1. Open Visual Studio Code
82-
1. Open up its terminal window (`Ctrl` + `` ` ``)
83-
1. Run the following command to install MonoGame Templates
81+
1. Open Visual Studio Code.
82+
1. Open up its terminal window (`Ctrl` + `` ` ``).
83+
1. Run the following command to install MonoGame Templates:
8484
8585
```sh
8686
dotnet new install MonoGame.Templates.CSharp
@@ -141,15 +141,15 @@ The .NET MAUI extension adds features for building mobile apps, including:
141141
142142
## Creating a new MonoGame project
143143
144-
1. Open up an empty folder in Visual Studio Code
145-
2. Open up its terminal window (`Ctrl` + `` ` ``)
144+
1. Open up an empty folder in Visual Studio Code.
145+
2. Open up its terminal window (`Ctrl` + `` ` ``).
146146
3. Run the following command to create an empty project for desktop platforms:
147147
148148
```sh
149149
dotnet new mgdesktopgl
150150
```
151151
152-
4. Once the files are created, open up the `Game1.cs` file and wait a second for the C# extension to load
152+
4. Once the files are created, open up the `Game1.cs` file and wait a second for the C# extension to load.
153153
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!
154154
155155
## Update Project Tool references
@@ -159,8 +159,8 @@ The MonoGame Content Editor (MGCB) it a tool delivered through NuGet for your pr
159159
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:
160160
161161
```dotnetcli
162-
dotnet tool restore
162+
dotnet tool restore
163163
```
164164
165165
> [!NOTE]
166-
> 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.
166+
> 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.

articles/getting_started/tools/mgcb_editor.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ dotnet mgcb-editor
2929
```
3030

3131
> [!NOTE]
32-
> 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.
32+
> 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.
3333
>
3434
> ```sh
3535
> dotnet tool restore

0 commit comments

Comments
 (0)