summaryrefslogtreecommitdiffhomepage
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorRDR8 <[email protected]>2017-12-19 02:27:12 -0600
committerGitHub <[email protected]>2017-12-19 02:27:12 -0600
commit22e72cb0a1795c642505ad86106e26effbe18310 (patch)
tree85cba188e36b48e7cefd9dc93c40791135062fbd /CONTRIBUTING.md
parent8d5484bbe0bc589ba92f8859d8878728151aeb86 (diff)
downloadraylib-22e72cb0a1795c642505ad86106e26effbe18310.tar.gz
raylib-22e72cb0a1795c642505ad86106e26effbe18310.zip
Update CONTRIBUTING.md
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 8dbc1ced..26f15156 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -37,7 +37,7 @@ Source code is extensively commented for that purpose, raylib primary learning m
### Using raylib develop branch
-raylib [master branch](https://github.com/raysan5/raylib) contains latest raylib release but all
+raylib [master branch](https://github.com/raysan5/raylib) contains the latest raylib release but all
the future work is always done on [develop branch](https://github.com/raysan5/raylib/tree/develop),
it's far ahead of master and I try to keep it always stable with latest library changes.
@@ -50,7 +50,7 @@ For detailed information on building raylib and examples, please check [raylib W
### Opening new Issues
-To open new issue for raylib (bug, enhacement, discussion...), just try to follow these rules:
+To open new issue for raylib (bug, enhancement, discussion...), just try to follow these rules:
- Make sure the issue has not already been reported before by searching on GitHub under Issues.
- If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a