AWS gameliftservers documentation change
Summary
Fixed minor typos: changed 'Github' to 'GitHub' and corrected 'to to' to 'to'.
Security assessment
These are purely editorial corrections with no security implications. No security features, vulnerabilities, or security-related content were added or modified.
Diff
diff --git a/gameliftservers/latest/developerguide/gamelift-wrapper-tutorial.md b/gameliftservers/latest/developerguide/gamelift-wrapper-tutorial.md index 05ecd299c..e47919bb6 100644 --- a//gameliftservers/latest/developerguide/gamelift-wrapper-tutorial.md +++ b//gameliftservers/latest/developerguide/gamelift-wrapper-tutorial.md @@ -72 +72 @@ In this tutorial you will: -Use the following commands to get the game server wrapper source and build the wrapper. These commands use SSH, but you can also go to the Github repository directly. +Use the following commands to get the game server wrapper source and build the wrapper. These commands use SSH, but you can also go to the GitHub repository directly. @@ -225 +225 @@ When your fleet status shows **Active** , this means that game servers are ready -Keep in mind that creating a game session using the AWS CLI is useful for testing and becoming familiar with the process. At some point, you'll add programmatic AWS SDK calls to to your game backend service as part of your game's matchmaking or game session placement system. +Keep in mind that creating a game session using the AWS CLI is useful for testing and becoming familiar with the process. At some point, you'll add programmatic AWS SDK calls to your game backend service as part of your game's matchmaking or game session placement system.