Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

fix typo #61

Merged
merged 1 commit into from
Apr 13, 2023
Merged

fix typo #61

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/gdevelop5/community/guide-for-submitting-an-example.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
```
Expand All @@ -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.
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.