From 09adf6a9355825b3ac5b6c8ce6320accdbe5e2cf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Aur=C3=A9lien=20Vivet?= Date: Thu, 13 Apr 2023 11:22:35 +0100 Subject: [PATCH] fix typo --- .../community/guide-for-submitting-an-example.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/gdevelop5/community/guide-for-submitting-an-example.md b/docs/gdevelop5/community/guide-for-submitting-an-example.md index 069e31fd95..94a6022650 100644 --- a/docs/gdevelop5/community/guide-for-submitting-an-example.md +++ b/docs/gdevelop5/community/guide-for-submitting-an-example.md @@ -145,11 +145,11 @@ You can submit the example to the [Example repository](https://github.com/GDevel - You will also be given a checklist of what is necessary. If you have done them, add `x` in the in brackets against each checklist. ``` - - [ ] My Game has a proper name in the game poperties. + - [ ] My Game has a proper name in the game properties. - [ ] My Game package name begins with 'com.examples'. - [ ] My Game has all events unfolded. - - [ ] I've Added myself as the author in the game properties. - - [ ] Iv' included a file caleed 'README.md' with a description in proper English, explaining what this example is doing. + - [ ] I've added myself as the author in the game properties. + - [ ] I've included a file called 'README.md' with a description in proper English, explaining what this example is doing. - [ ] I confirm that this game and all its resources can be integrated to this Github repository, distributed and MIT licensed. - [ ] I've cleaned unused resources in the project. ``` @@ -164,4 +164,4 @@ Congratulations! Now your example has been submitted, but it won't be directly a !!! warning There is no guarantee that your example will be accepted, it can be rejected if the example is not suitable - for the library. Also remember that while it's hard to get some feedback, reviewers are asking for changes because they believe this will improve your example. Try to rework the example using their feedback! Once you think it's good enough, you can ask for another review or discuss points where you might disagree. \ No newline at end of file + for the library. Also remember that while it's hard to get some feedback, reviewers are asking for changes because they believe this will improve your example. Try to rework the example using their feedback! Once you think it's good enough, you can ask for another review or discuss points where you might disagree.