docs: final check before launch

CONTRIBUTING.md

@@ -1,4 +1,4 @@
-# Contributing to OpenSauced Intro
+# Contributing to OpenSauced Becoming a Maintainer Course
 
 Contributions are always welcome, no matter how large or small. Before contributing, please read the [Code of Conduct](https://docs.opensauced.pizza/contributing/code-of-conduct/) and follow the directions in this guide.
 
@@ -36,7 +36,15 @@ You can always ask for help in the `🍕opensauced-contributors-chat` channel on
    cd maintainer-intro-course
    ```
 
-4. Run the project.
+4. Create a new branch to work on your changes.
+
+   ```bash
+   git checkout -b YOUR-BRANCH-NAME
+   ```
+
+   Replace "YOUR-BRANCH-NAME" with a descriptive name for your branch — for example, `feat/add-submit-button`.
+
+5. Run the project.
 
 ### Running the Project Locally
 
@@ -136,13 +144,13 @@ Follow these steps to add a new chapter to our course:
 
    Create a new Markdown (`.md`) file in the root and name the file to reflect the chapter's content—for example, `how-to-contribute-to-open-source.md` for a chapter about how to contribute to open source.
 
-   > **NOTE**: Be sure to follow naming conventions. Notice that file names are not capitalized, and there are hyphens in place of spaces between words.
+   !> Be sure to follow naming conventions. Notice that file names are not capitalized, and there are hyphens in place of spaces between words.
 
 2. **Write content**.
 
    Open the newly created Markdown file in a text editor and write the content for your chapter using the Markdown syntax. You can include headings, text, images, links, lists, and other elements to present your information effectively.
 
-   > **Note**: There should only be **one** `heading 1` in each file.
+   !> There should only be **one** `heading 1` in each file.
 
 3. **Test your changes**.
 

README.md

@@ -81,7 +81,7 @@ Happy learning and contributing!
 
 ---
 
-## 🤝 Contributing to this Repository
+## 🤝 Contributing to OpenSauced Becoming a Maintainer Repository
 
 We encourage you to contribute to OpenSauced! All contributors are required to abide by our [Code of Conduct](https://github.com/open-sauced/.github/blob/main/CODE_OF_CONDUCT.md). Please check out the [Contributing Guidelines](CONTRIBUTING.md) for information on how to contribute.
 

community-translations.md

@@ -0,0 +1,3 @@
+# Community Course Translations
+
+We are grateful for the contributions of the community in translating this course. Although the OpenSauced team does not currently maintain these projects, we want to share the forked copy of the repositories with those taking the course. Below, you will find the latest community translations.

getting-practical.md

@@ -16,7 +16,7 @@ Sometimes, the hardest part is deciding what you will work on. Here are some gen
 - Think about a topic you're passionate about that others might be interested in.
 - Think about a problem you've had to solve that others can benefit from.
 
-Don't think too hard about it now. You can always go back and update things later. For now, if you need a place to get started, let's create a repository about your favorite open source resources.
+Don't think too hard about it now. You can always go back and update things later. For now, if you need a place to start, let's create a repository about your favorite open source resources.
 
 ## Creating Your Repository
 
@@ -28,7 +28,7 @@ We will walk through the steps to set up your project in GitHub. Although it's n
 - Initialize the repository with a README file and add a license.
 - Click the "Create repository" button.
 
-![setting up a repo](./assets/gifs/set-up-repo.gif)
+![setting up a repo](./assets/gif/set-up-repo.gif)
 
 If you're using our starter idea, you could use the following:
 
@@ -319,7 +319,7 @@ body:
 
 - In your repository, click the "Issues" tab and then the "New issue" button.
 
-  ![create issue](./assets/images/create-issue.png)
+  ![create issue](./assets/img/create-issue.png)
 
 - Select the type of issue you want to create. In this example, we'll select Feature Request.
 - Write your issue. If you're following along the example, we'll write a feature request for a new resource:
@@ -334,7 +334,7 @@ body:
 
 - Once you've completed the issues, click "Submit new issue."
 
-  ![feature-form.png](./assets/images/feature-form.png)
+  ![feature-form.png](./assets/img/feature-form.png)
 
 ### Promoting Your Project
 

i18n-guidelines.md

@@ -1,19 +1,19 @@
 # 🌐 i18n Guidelines
 
-Welcome to our i18n Guidelines! We appreciate your interest in translating our Intro to Open Source course.
+Welcome to our i18n Guidelines! We appreciate your interest in translating our Becoming a Maintainer with OpenSauced course.
 
 At the moment, we have the course in the following languages:
 
-- English
+- [English](./README.md)
 
 ## How Can I Contribute?
 
 There are two types of i18n contributions that we accept:
 
-1. Translate our Intro to Open Source course.
+1. Translate our Becoming a Maintainer with OpenSauced course.
 2. Review pull requests (PRs) and translations.
 
-### Translate the Intro to Open Source Course
+### Translate the Becoming a Maintainer with OpenSauced Course
 
 We have two types of translations:
 
@@ -23,9 +23,9 @@ Official translations start as a post on our [discussion board](https://github.c
 
 #### 2. Community Translations
 
-We can't always support the maintenance of translations. However, we know some contributors are willing to translate, and we value these contributions. For that reason, we have a Community Translations section.
+We can't always support the maintenance of translations. However, we know some contributors are willing to translate, and we value these contributions. For that reason, we have a [Community Translations](./community-translations.md) section.
 
-If you're interested in translating our Intro to OSS course, fork this repository and add the translation to your forked repository. Then, you can add a link to your translation in the `community-translations.md` file.
+If you're interested in translating our Becoming a Maintainer with OpenSauced course, fork this repository and add the translation to your forked repository. Then, you can add a link to your translation in the [`community-translations.md`](./community-translations.md) file that you can find in the root directory.
 
 We encourage you to add it to the [discussion board](https://github.com/open-sauced/maintainer-intro-course/discussions) as well. We will consider moving it to an official translation if it becomes popular and has enough support.
 
@@ -35,22 +35,22 @@ If you are familiar with the translated language(s), you can help us review the
 
 ## Adding Translations
 
-First, please read our [Contributing Guide](CONTRIBUTING.md) to setting up the project locally and for the technical instruction. Then, follow these steps to add the translations:
+First, please read our [Contributing Guide](./CONTRIBUTING.md) to setting up the project locally and for the technical instruction. Then, follow these steps to add the translations:
 
 1. **Identify target languages**.
 
    Determine which languages you want to add translations for. Make sure these languages are relevant to the project's user base.
 
 2. **Create translation files**.
 
-   Inside the "translations" directory, create a new subdirectory for each language you plan to support. Use language codes (e.g., "en" for English, "fr" for French) as directory names.
+   Inside the "translations" directory, create a new subdirectory for each language you plan to support. Use language codes (e.g., "en" for English, "fr" for French, etc.) as directory names.
 
    ```markdown
    .
    └── translations/
-      ├── en/ (English)
-      ├── fr/ (French)
-      └── es/ (Spanish)
+      ├── en/
+      ├── fr/
+      └── es/
    ```
 
 3. **Translate content**.
@@ -100,4 +100,13 @@ When it comes to reviewing a translation PR, ask yourself the following question
 - Are there links that could be localized and translated? (e.g., Wikipedia and MDN links)
 - Is the translation correctly written following the translated language's norms and practices?
 
-When you think a PR is ready to be merged after your suggestions were addressed (if any), approve it through GitHub's "Review Changes" button or leave an "LGTM!" in the comment section and tag the `@open-sauced/docs` maintainers. (“LGTM” is an abbreviation of “Looks Good to Me” or “Let’s Get to Merging”, often used to approve pull requests.)
+When you think a PR is ready to be merged after your suggestions were addressed (if any):
+
+1. Click the "Files changed" tab under the PR's title.
+2. Click the green "Review changes" button.
+3. Select "Approve."
+4. Click the green "Submit review" button.
+
+Alternatively, you can leave an LGTM\* in the comment section and tag the `@open-sauced/docs` maintainers.
+
+?> \*LGTM is an abbreviation of “Looks Good to Me” or “Let’s Get to Merging”, often used to approve pull requests.

index.html

@@ -57,5 +57,6 @@
 			src="//cdn.jsdelivr.net/npm/docsify-darklight-theme@latest/dist/index.min.js"
 			type="text/javascript"
 		></script>
+		<script src="//cdn.jsdelivr.net/npm/docsify-pagination/dist/docsify-pagination.min.js"></script>
 	</body>
 </html>