Fix typos in multiple files

guides/contributor.rst

@@ -29,7 +29,7 @@ All projects have the following basic requirements:
 1. Contributors must create accounts on our `OpenBeagle <https://openbeagle.org/>`_, `Discord <https://bbb.io/gsocchat>`_ and `Beagle Forum <http://bbb.io/gsocml>`_ prior to creating their application.
 2. All newly generated materials must be released under an `open source license <http://www.opensource.org/licenses>`_. Individual contributors shall retain copyright on their works.
 3. Contributors will demonstrate their ability to cross-compile and utilize version control software by creating a “Hello World” application and generating a pull request to `jadonk/gsoc-application <https://github.com/jadonk/gsoc-application/tree/master/ExampleEntryJasonKridner>`_. For assistance, please visit our `Discord <https://bbb.io/gsocchat>`_ or utilize the `Beagle Forum <http://bbb.io/gsocml>`_. The “Hello World” application must print your name and the date out in an ARM Linux environment. Freely available emulators may be used to test your application or you can ask anyone on the chat or mailing list to help you test.
-4. All projects will produce reusable software components and will not be “what–I-built-over-my-summer-vacation” projects. Including a hardware component is welcome, but the project deliverable will be software that may be utilized by a wide audience of the `BeagleBoard.org <https://www.beagleboard.org/>`_ community.
+4. All projects will produce reusable software components and will not be “what-I-built-over-my-summer-vacation” projects. Including a hardware component is welcome, but the project deliverable will be software that may be utilized by a wide audience of the `BeagleBoard.org <https://www.beagleboard.org/>`_ community.
 5. Contributors will demonstrate their ability to collaborate by creating a project proposal on this site using our :ref:`proposal template <gsoc-proposal-template>` and utilizing our `Discord <https://bbb.io/gsocchat>`_ to collect quotes regarding the usefulness of their proposal to the `BeagleBoard.org <https://www.beagleboard.org/>`_ community. **Use of Google Docs for proposal development is discouraged due to insufficient revision control and extensive use of computing resources having numerous documents open simultaneously**.
 6. Source code generated during the project must be released on `OpenBeagle <https://openbeagle.org/>`_ (and we’ll setup a mirror on `Github.com <http://github.com/>`_).
 7. Contributors will provide two recorded audio/video presentations uploaded to Youtube or Vimeo (screencasts are appropriate), one near the beginning of the project summarizing their project goals and another in the wrap-up phase to summarize their accomplishments. Examples can be found in :ref:`Past_Projects`. There is no requirement to show your faces or use English.

guides/proposal.rst

@@ -21,7 +21,7 @@ How to write an *unsuccessful* proposal
 
 Unsuccessful proposals often:
 
-1. Try to pass off previous school projects as something to do for GSoC. The work has already done, and the project often has very little to do with `BeagleBoard.org hardware <https://www.beagleboard.org/boards>`_,
+1. Try to pass off previous school projects as something to do for GSoC. The work is already done, and the project often has very little to do with `BeagleBoard.org hardware <https://www.beagleboard.org/boards>`_,
 2. Show up shortly before the submission deadline with only a half page of “proposal”, being little more than a name, contact information, and a statement of “I will work hard”,
 3. Are generic and sent to every other GSoC org with very few details on deliverables or schedule, or
 4. Introduce an idea that was never talked about to the `BeagleBoard.org <https://www.beagleboard.org/>`_ mentors in our `Forum <https://bbb.io/gsocml>`_ and submitted without ever engaging the Beagle community.

guides/site-editing.rst

@@ -107,11 +107,11 @@ Now you have to select a file and start editing. Below image shows some,
     :align: center
 
 .. tip:: Just like you do on your normal Visual Studio Code desktop application, to commit your changes you can either 
-    click on Source control ( :fa:`code-branch;pst-color-secondary` ) button or press ``CTRL + SHIFT + G`` to see all the edited fils.
+    click on Source control ( :fa:`code-branch;pst-color-secondary` ) button or press ``CTRL + SHIFT + G`` to see all the edited files.
 
-After swithing to source control you have to,
+After switching to source control you have to,
 
-1. Add a commit message in the input feild.
+1. Add a commit message in the input field.
 2. Click on ``Commit to main`` button or click on drop down button to choose ``Commit to new branch``.
 
 .. image:: media/commit-changes.png
@@ -132,8 +132,8 @@ ee/user/project/protected_branches.html>`_ by default.
 .. image:: media/commit-branch.png
     :align: center
 
-When all done right, the lower right side of the ``Web IDE`` you'll a prompt showing ``Success! Your changes have been committed`` message with 
-two button,
+When all done right, at the lower right side of the ``Web IDE`` you'll see a prompt showing ``Success! Your changes have been committed`` message with 
+two buttons,
 
 1. ``Got to Project``
 2. ``Continue working``
@@ -142,7 +142,7 @@ two button,
     :align: center
 
 If you click on ``Go to Project`` button, you'll see the commit successfully applied as shown in the red box in the image below and the 
-green tick shows on the right side indicates that the CI build was also successful.
+green tick shown on the right side indicates that the CI build was also successful.
 
 .. image:: media/commit.png
     :align: center
@@ -156,15 +156,15 @@ Create a pull request
 
 After making your changes and commiting them to your forked repo, you are set to create a new `pull request / merge request 
 <https://en.wikipedia.org/wiki/Distributed_version_control#Pull_requests>`_ so that those changes can be merged to upstream 
-repo. To start your new PR click on the dedicated button to create a new merge request and fill out all the details. The image 
-below shows all the feilds you have to update,
+repo. To start your new PR, click on the dedicated button to create a new merge request and fill out all the details. The image 
+below shows all the fields you have to update,
 
-1. Provided a good title that reflects your work.
+1. Provide a good title that reflects your work.
 2. Add a detailed description of the work you have done. Add pictures whenever seems useful.
 3. (Optional) you can assign it to yourself if you'll be working on further updates or assign it to someone else who might want to work on the comments we may provide on your work.
 4. Add ``lorforlinux`` or ``jkridner`` as reviewer for PRs with site content update or add your mentor as reviewer if it's related to project work / proposal.
-5. If you want your commits to be shows as a single commit then you can choose the ``sqash commits ...`` check box.
-6. Check if all your commits are shown in the bottom of the screen and if everything looks okay then click on ``Create merge request`` button.
+5. If you want your commits to be shown as a single commit, then you can choose the ``sqash commits ...`` check box.
+6. Check if all your commits are shown in the bottom of the screen and if everything looks okay, then click on ``Create merge request`` button.
 
 .. tip:: If you are still working on some updates, you may also choose ``Mark as draft`` checkbox (below title) 
     which indicates that you are seeking feedback before making your commits suitable to merge.