diff --git a/guides/student.rst b/guides/contributor.rst
similarity index 56%
rename from guides/student.rst
rename to guides/contributor.rst
index 0013b225f59f660e11da8b325b1614b9dc86758b..5c120fc579d9f570814464ebc2ea0b53b54e0815 100644
--- a/guides/student.rst
+++ b/guides/contributor.rst
@@ -1,7 +1,7 @@
-.. _gsoc-student-guide:
+.. _gsoc-contributor-guide:
 
-Student guide 
-#############
+Contributor Guide 
+#################
 
 .. youtube:: YN7uGCg5vLg
     :width: 100%
@@ -12,13 +12,13 @@ General requirements
 
 All projects have the following basic requirements:
 
-1. Students must create accounts on `OpenBeagle <https://openbeagle.org/>`_, `Discord <http://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 students shall retain copyright on their works.
-3. Students 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 `Discord <http://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.
+1. Contributors must create accounts on `OpenBeagle <https://openbeagle.org/>`_, `Discord <http://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 `Discord <http://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. Students will demonstrate their ability to collaborate by creating a project proposal on this site using our :ref:`proposal template <gsoc-proposal-template>` and utilizing `Discord <http://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**.
+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 `Discord <http://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 (and we’ll setup a mirror on `Github.com <http://github.com/>`_).
-7. Students 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 on `http://beagleboard.org/gsoc <http://beagleboard.org/gsoc>`_. There is no requirement to show your faces or use English.
+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 on `http://beagleboard.org/gsoc <http://beagleboard.org/gsoc>`_. There is no requirement to show your faces or use English.
 
 .. important:: 
 
@@ -37,8 +37,8 @@ All projects have the following basic requirements:
 Student proposals can encompass projects based on the :ref:`ideas page <gsoc-project-ideas>`  or can include personal project ideas, 
 but should be focused on generating a sustainable and reusable open source software component. Previous Google Summer of Code projects show 
 that the key to success is being passionate about your project, so propose something that is extremely interesting to you, even 
-if it is not on this list. We will be glad to help students develop ideas into projects via `Discord <http://bbb.io/gsocchat>`_ 
-and `Forum <https://forum.beagleboard.org/c/gsoc>`_. There are many potential project ideas and we will match students to projects 
+if it is not on this list. We will be glad to help contributors develop ideas into projects via `Discord <http://bbb.io/gsocchat>`_ 
+and `Forum <https://forum.beagleboard.org/c/gsoc>`_. There are many potential project ideas and we will match contributors to projects 
 based on their interests and help scope the proposals to something that can be completed in the Summer of Code timeframe.
 
 .. tip::
diff --git a/guides/index.rst b/guides/index.rst
index 969299f6688c078b6e9442ff82af0690e6757a21..5bfb060bfd211a0ffbd4b56bb8cfcb90ec37bd1e 100644
--- a/guides/index.rst
+++ b/guides/index.rst
@@ -3,16 +3,16 @@
 Guides
 ######
 
-This section includes guides for :ref:`students <gsoc-student-guide>` & :ref:`mentors <gsoc-mentor-guide>` who want to participate 
+This section includes guides for :ref:`contributors <gsoc-contributor-guide>` & :ref:`mentors <gsoc-mentor-guide>` who want to participate 
 in GSoC 2024 with `BeagleaBoard.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>`.
 
 .. card::
-    :link: gsoc-student-guide
+    :link: gsoc-contributor-guide
     :link-type: ref
 
-    :fas:`graduation-cap` **Student Guide**
+    :fas:`graduation-cap` **Contributor Guide**
     ^^^^
 
     If you want to increase your chances of being accepted into (and succeed during) Google Summer of Code, we strongly 
@@ -26,7 +26,7 @@ a step by step :ref:`contribution guide <gsoc-contribution-guide>`.
     :fas:`person-chalkboard` **Mentor Guide**
     ^^^^
 
-    If you want to mentor a students for GSoC this year read this short guide made for mentors wondering where to help.
+    If you want to mentor for GSoC this year read this short guide made for mentors wondering where to help.
 
 .. card:: 
     :link: gsoc-proposal-guide
@@ -55,7 +55,7 @@ a step by step :ref:`contribution guide <gsoc-contribution-guide>`.
     :hidden:
     :maxdepth: 2
 
-    student
+    contributor
     mentor
     proposal
     contrib
\ No newline at end of file
diff --git a/guides/mentor.rst b/guides/mentor.rst
index 1d345b5aba4d093c236574715feeff5568e61c1e..ed4bae63b0b85a2859faf44a73cd8330cf362686 100644
--- a/guides/mentor.rst
+++ b/guides/mentor.rst
@@ -9,7 +9,7 @@ Mentor guide
 
 .. important:: 
 
-    As a mentor you have to guide students/contributors through the entire process of GSoC, from learning 
+    As a mentor you have to guide contributors through the entire process of GSoC, from learning 
     about `BeagleBoard.org <https://www.beagleboard.org/>`_ community, to helping GSoC Contributors 
     become familiar with the code base and testing practices, to finally releasing their code on 
     `OpenBeagle <https://openbeagle.org/>`_ for the world to use!
@@ -33,9 +33,9 @@ capacity, as much as they would answer anyone’s questions on `Discord <http://
 
 Prospective mentors, sudents will use `Discord <http://bbb.io/gsocchat>`_ and `Forum <https://forum.beagleboard.org/c/gsoc>`_ 
 to make contact with you, so be sure to provide up-to-date information. Please feel free to add yourself on mentors page and we will monitor 
-and police that list. Acceptance as an official mentor with the ability to rate proposals and grade students will come via the Google system. 
+and police that list. Acceptance as an official mentor with the ability to rate proposals and grade contributors will come via the Google system. 
 We will only approve official mentors who have a prove track record with Beagle, but welcome all community members to provide guidance to both 
-mentors and students to best service the community as a whole. Don’t be shy and don’t be offended when we edit. We are thrilled to have you on-board!
+mentors and contributors to best service the community as a whole. Don’t be shy and don’t be offended when we edit. We are thrilled to have you on-board!
 
 
 
diff --git a/guides/proposal.rst b/guides/proposal.rst
index 79f6bd7ab632c51f1b3c75bcc79f9957647e2046..717645e9f33031214cdd46521c35aa7c5c39e2f5 100644
--- a/guides/proposal.rst
+++ b/guides/proposal.rst
@@ -35,7 +35,7 @@ suggestions that improve the proposal.
 Using proposal template
 ************************
 
-To make the project proposal writing process easier for all the GSoC contributors/students we have created a :ref:`gsoc-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 
diff --git a/index.rst b/index.rst
index d78832cc7927b7cdc52ffd6bb98ee56828c9cefd..041b6b1df990aeca76761048149392a5a6f40f49 100644
--- a/index.rst
+++ b/index.rst
@@ -14,7 +14,7 @@ GSoC @ BeagleBoard.org
    :class: admonition-code
 
    Spend your summer break writing code and learning about open source development while earning money!
-   Accepted students work with a mentor and become a part of the open source community. Many become lifetime
+   Accepted contributors work with a mentor and become a part of the open source community. Many become lifetime
    open source developers! The 2024 student application window will be open from
    `March 18th 2024 <https://developers.google.com/open-source/gsoc/timeline#march_18_-_1800_utc>`_ to
    `April 2nd 2024 <https://developers.google.com/open-source/gsoc/timeline#april_2_-_1800_utc>`_!
@@ -105,7 +105,7 @@ GSoC @ BeagleBoard.org
 
 .. important::
 
-   Students will be expected to execute a series of prerequisites to demonstrate and
+   Contributors will be expected to execute a series of prerequisites to demonstrate and
    expand familiarity with embedded systems development. Don't worry, the
    `live chat <https://bbb.io/gsocchat>`_ channel has over 1,000 active members to
    travel with you on your journey.