docs: made some minor grammatical corrections (#61)

* fix: minor grammatical fix

* docs: update contributing.md

* fix: minor grammatical fix

Co-Authored-By: James George <[email protected]>

Co-authored-by: James George <[email protected]>

Author: annu12340

docs/guide/README.md

@@ -11,10 +11,10 @@ Users are required to solve 30 tasks that take them through the basic constructs
 - Follow the instructions as prompted.
 - Now type in `cd teachcode-solutions`.
 - Grab the initial key and type in `teachcode fetchtask <key>`.
-- Hurray :tada: you've got your first task.
+- Hurray :tada: , you've got your first task.
 - Now you can find a `config.json` and `task1.py` (language of choice) file within the `teachcode-solutions` directory.
-- Open up your favourite editor and code up the solution.
+- Open up your favorite editor and code up the solution.
 - Now type in `teachcode submit`.
 - Enter your Git credentials when prompted.
-- If the current solution satisfies all test cases, you'll get the key to proceed with.
+- If the current solution satisfies all test cases, you'll get the key to proceed farther.
 - Grab the key and type in `teachcode fetchtask <key>`.

docs/guide/contributing.md

@@ -19,5 +19,5 @@ title: 'Contributing'
 ## Points to ponder
 
 1. Make sure that you submit an issue first if you have something in mind that you're willing to work on.
-2. Follow a `rebase` strategy in order to update your remote branch with the latest changes.
+2. Follow a `rebase` strategy to update your remote branch with the latest changes.
 3. Prefix your branch names with `feat/`, `docs/` or `hotfix/` for feature proposals, docs-related and bug fixes, respectively.