fix-warning

guides/contributor.rst

@@ -17,7 +17,7 @@ All projects have the following basic requirements:
 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.
 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/>`_).
+6. Source code generated during the project must be released on OpenBeagle (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.
 
 .. important:: 

guides/index.rst

@@ -6,7 +6,7 @@ Guides
 This section includes guides for :ref:`contributors <gsoc-contributor-guide>` & :ref:`mentors <gsoc-mentor-guide>` who want to participate 
 in GSoC 2024 with `BeagleBoard.org <www.beagleboard.org>`_. It's highly recommended to check `GSoC Frequently Asked Questions 
 <https://developers.google.com/open-source/gsoc/faq>`_. For anyone who just want to contribute to this site we also have 
-a step by step :ref:`contribution guide <gsoc-contribution-guide>`.
+a step by step :ref:`contribution guide <gsoc-contributor-guide>`.
 
 .. card::
     :link: gsoc-contributor-guide

guides/mentor.rst

@@ -39,7 +39,7 @@ Mentors should:
 
 Only ideas deemed by administrators as being sufficiently supported by qualified mentors will be merged.
 
-.. admonishment:: Remember
+.. admonition:: Remember
 
     BeagleBoard.org mentored GSoC projects are supposed to be for software projects that service the Beagle and general open source
     embedded systems community, not theses, how-to guides or what I did over my summer vacation ideas.

guides/proposal.rst

@@ -47,9 +47,9 @@ Using proposal template
 To make the project proposal writing process easier for all the GSoC contributors we have created a :ref:`gsoc-proposal-template`.
 
 .. tip:: 
-    Start with :ref:`gsoc-contribution-guide` to simplify the proposal writing process using OpenBeagle CI. It's always recommended to create a fork 
+    Start with :ref:`gsoc-contributor-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-contribution-guide`. For any query you, can reach out on 
+    setting up Sphinx on local machine are also provided on :ref:`gsoc-contributor-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,