Skip to content

Commit cb5c95a

Browse files
Remove contractions. You'll, let's etc. (#15)
1 parent ba1387c commit cb5c95a

File tree

4 files changed

+10
-10
lines changed

4 files changed

+10
-10
lines changed

articles/tutorials/advanced/MobileDeployment/01_getting_started/index.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,11 @@ description: "Get started with MonoGame mobile development by setting up your de
55

66
# Getting Started and Overview
77

8-
This tutorial extends the **MonoGame 2D Dungeon Slime tutorial** to mobile platforms. If you haven't completed the desktop tutorial yet, we recommend finishing it first as we'll be building directly on that foundation.
8+
This tutorial extends the **MonoGame 2D Dungeon Slime tutorial** to mobile platforms. If you have not completed the desktop tutorial yet, we recommend finishing it first as we will be building directly on that foundation.
99

10-
## What You'll Learn
10+
## What You Will Learn
1111

12-
By the end of this mobile tutorial series, you'll have:
12+
By the end of this mobile tutorial series, you will have:
1313
- Ported the **Dungeon Slime** game to run on Android and iOS
1414
- Implemented touch controls to replace mouse and keyboard input
1515
- Set up cross-platform project architecture for code sharing
@@ -43,12 +43,12 @@ This tutorial utilizes modern .NET project management features to streamline cro
4343

4444
## Central Package Management
4545

46-
We'll be using [Central Package Management](https://learn.microsoft.com/en-us/nuget/consume-packages/central-package-management) to maintain consistent package versions across all platform projects. This ensures your shared code library and platform-specific projects use identical dependency versions.
46+
We will be using [Central Package Management](https://learn.microsoft.com/en-us/nuget/consume-packages/central-package-management) to maintain consistent package versions across all platform projects. This ensures your shared code library and platform-specific projects use identical dependency versions.
4747

4848
## SLNX Solution Format
4949

5050
The sample projects use the new [SLNX solution format](https://devblogs.microsoft.com/dotnet/introducing-slnx-support-dotnet-cli/) for improved cross-platform development experience and better integration with modern .NET tooling.
5151

5252
# Next Steps
5353

54-
In the next chapter, we'll convert the existing Windows-only Dungeon Slime project to support multiple platforms and explore the cross-platform project architecture.
54+
In the next chapter, we will convert the existing Windows-only Dungeon Slime project to support multiple platforms and explore the cross-platform project architecture.

articles/tutorials/advanced/MobileDeployment/02_crossplatform/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: "02: Setting Up Cross-Platform Projects"
33
description: "Learn how to convert a Windows-only MonoGame project to support iOS and Android platforms, creating a unified codebase for multi-platform deployment."
44
---
55

6-
# What You'll Learn
6+
# What You Will Learn
77

88
In this chapter you will:
99
- Convert a Windows-only MonoGame project to support multiple platforms
@@ -27,7 +27,7 @@ Before starting this chapter, ensure you have:
2727

2828
The Dungeon Slime game from the 2D tutorial serves as our practical example for cross-platform conversion. This approach can be applied to any MonoGame project you want to deploy across multiple platforms.
2929

30-
The key principle is **code sharing** of the game logic - we'll extract the game logic into a common library that all platform-specific projects can refer to and use.
30+
The key principle is **code sharing** of the game logic - we will extract the game logic into a common library that all platform-specific projects can refer to and use.
3131

3232
# Cross-Platform Project Structure
3333

articles/tutorials/advanced/MobileDeployment/03_touch/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: "03: Touch Gesture Handling"
33
description: "Learn the fundamentals of touch gesture recognition in MonoGame - registration, detection, and processing."
44
---
55

6-
Before proceeding with the cross-platform conversion, let's review how to handle touch input in MonoGame. The concepts discussed here apply to any MonoGame project. For our Dungeon Slime demo, touch input is managed by the Gum library, but understanding the fundamentals is still important.
6+
Before proceeding with the cross-platform conversion, let us review how to handle touch input in MonoGame. The concepts discussed here apply to any MonoGame project. For our Dungeon Slime demo, touch input is managed by the Gum library, but understanding the fundamentals is still important.
77

88
## Gesture Registration
99

@@ -134,7 +134,7 @@ switch (gesture.GestureType)
134134

135135
## Complete Example
136136

137-
Here's a minimal working example demonstrating all three concepts:
137+
Here is a minimal working example demonstrating all three concepts:
138138

139139
```csharp
140140
public class TouchGame : Game

articles/tutorials/advanced/MobileDeployment/04_publishing/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: "Learn how to publish your MonoGame mobile application to both the
55

66
# Publishing Overview
77

8-
This chapter covers the complete publishing process for both major mobile app stores. You'll learn the requirements, workflows, and common pitfalls for getting your MonoGame app successfully published on iOS and Android platforms.
8+
This chapter covers the complete publishing process for both major mobile app stores. You will learn the requirements, workflows, and common pitfalls for getting your MonoGame app successfully published on iOS and Android platforms.
99

1010
## Prerequisites
1111

0 commit comments

Comments
 (0)