Merge branch 'main' into 'main'

Fix typos in guides files

See merge request gsoc/gsoc.beagleboard.io!21

guides/proposal.rst

@@ -49,7 +49,7 @@ To make the project proposal writing process easier for all the GSoC contributor
 .. tip:: 
     Start with :ref:`gsoc-site-editing-guide` to simplify the proposal writing process using OpenBeagle CI. It's always recommended to create a fork 
     of `gsoc.beagleboard.io repo on OpenBeagle <https://openbeagle.org/gsoc/gsoc.beagleboard.io>`_ and clone on your local machine. Instructions for 
-    setting up Sphinx on local machine are also provided on :ref:`gsoc-site-editing-guide`. For any query you, can reach out on 
+    setting up Sphinx on local machine are also provided on :ref:`gsoc-site-editing-guide`. For any query, you can reach out on 
     our `Discord <https://bbb.io/gsocchat>`_ or `Forum <https://bbb.io/gsocml>`_.
 
 You can either open your cloned `gsoc.beagleboard.io repo <https://openbeagle.org/gsoc/gsoc.beagleboard.io>`_ using Visual Studio Code on your local machine or use OpenBeagle Web IDE. Now, follow steps below to write your proposal,

guides/site-editing.rst

@@ -68,7 +68,7 @@ After selecting the file you have to click on ``edit button`` and then choose ei
 
 .. note:: 
     Choosing ``Web IDE`` will load a `Visual Studio Code Server <https://code.visualstudio.com/docs/remote/vscode-server>`_
-    instance which is a feature rich source code editor. Depending on the internent connection your machine will take some to 
+    instance which is a feature rich source code editor. Depending on the internent connection, your machine will take some time to 
     load the editor and it can be a bit heavy for some machines to handle. Once fully loaded it should run smoothly but, if that is 
     not the case then please consider using single file editor option. Considering majority of the users will be using ``Web IDE`` option,
     we are using the ``Web IDE`` for the rest of this guide.