Apply suggestions from code review

Co-authored-by: JC Palmer <me@jccpalmer.com>

Author: LadyBluenotes

CONTRIBUTING.md

@@ -2,7 +2,8 @@
 
 Thank you for helping us make this project great and being a part of the Solid community!
 
-We welcome contributions from anyone, regardless of your skill level of the size of the contribution. We are happy to help with guidance on PRs, technical writing, and turning features into realities.
+We welcome contributions from anyone, regardless of your skill level.
+We are happy to help with guidance on PRs, technical writing, and turning features into realities.
 
 >  **New to contributing?**
 Take a look at [this GitHub guide](https://docs.github.com/en/get-started/quickstart/hello-world) to learn how to use Git and GitHub to contribute to open-source. 
@@ -12,11 +13,15 @@ If you're new to Solid, we ask that you check out our [Writing Guide](https:/
 ## Types of contributions
 There are many ways to contribute to the Solid's documentation!
 
-The Solid Docs website is built on Solid! Maintaining it requires not only written content but also maintaining the Solid code, addressing a11y, CSS, UI, and UX concerns. We also aim to make our documentation available in several languages, so we need help translating the entire site.
+The Solid Docs website is built on Solid!
+Maintaining it requires not only written content and Solid code maintenance, but it also needs to address accessibility (a11y), CSS, UI, and UX concerns.
+We also aim to make our documentation available in several languages, so we need help translating the entire site.
 
-You can help out by getting involved by leaving review comments on [PRs](https://github.com/solidjs/solid-docs-next/pulls) and adding ideas in existing GitHub [issues ](https://github.com/solidjs/solid-docs-next/issues)and [discussions](https://github.com/solidjs/solid-docs-next/discussions).
+You can help out by leaving review comments on [PRs](https://github.com/solidjs/solid-docs-next/pulls) and adding ideas in existing GitHub [issues ](https://github.com/solidjs/solid-docs-next/issues) and [discussions](https://github.com/solidjs/solid-docs-next/discussions).
 
-Every PR, especially translation PRs, will need reviewers. Reviewing PRs and leaving comments, suggestions, or even saying "looks good!" can be a great way to get started on contributing alongside our Docs team, and to learn more about Solid.
+Every PR, especially translation PRs, will need reviewers.
+Reviewing PRs and leaving comments, suggestions, or even saying "Looks good!" can be a great way to get started on contributing alongside our Docs team.
+It's also a great way to learn more about Solid!
 
 We encourage you to:
 
@@ -30,9 +35,9 @@ Issues are a great way to keep track of tasks, enhancements, and bugs for our pr
 
 After an issue has been considered by the community, we often reach out to community members to encourage them to submit PRs based on existing issues. 
 
-Larger contributions to the docs are encouraged after participating in Issues and Discussions, as unsolicited material may not fit into our existing plans.
+We encourage larger contributions to the docs after you participate in Issues and Discussions, as unsolicited material may not fit into our existing plans.
 
-> While you're more than welcomed to mention a bug you've encountered on our Discord, we ask that you also report it as an issue!
+> While you're more than welcome to mention a bug that you've encountered on our Discord, we ask that you also report it as an issue!
 
 ### Writing an issue
 Helpful issues generally include:
@@ -42,7 +47,7 @@ Helpful issues generally include:
 - Explanations as to why (or _for whom_) this is a problem
 - _Option_: proposed solutions
 ### Examples of helpful new issues
-- An explanation is confusing (with an explanation as to why)
+- An explanation is confusing (with a reason why)
 - a code example is wrong (with or without a proposed fix)
 - accessibility (a11y) issues discovered
 - missing content
@@ -56,7 +61,8 @@ We use labels as a way to organize and categorize our issues. Here are some comm
 - `help wanted` - when we are looking for assistance on an issue
 - `i18n`  - anything to do with internationalization and translation
 ## Start a discussion
-Discussion are a place within this repository where we can have open-ended conversations. It's the perfect place for Q&A, sharing ideas, community engagement, and connecting with other members.
+Discussions are a place within this repository where we can have open-ended conversations.
+It's the perfect place for Q&A, sharing ideas, community engagement, and connecting with other members.
 
 Feel free to start a [new discussion](https://github.com/solidjs/solid-docs-next/discussions) on any topic related to our docs!
 
@@ -66,14 +72,15 @@ Feel free to start a [new discussion](https://github.com/solidjs/solid-docs-n
 - Is the site navigation clear and helpful?
 - Any suggestions of content that you think could be helpful adding
 ## Make a PR (Pull Request)
->  If you've never submitted a pull request on GitHub before, check out [this overview](https://opensource.guide/how-to-contribute/#opening-a-pull-request). 
+>  If you've never submitted a pull request on GitHub before, check out [this overview on how to open a PR](https://opensource.guide/how-to-contribute/#opening-a-pull-request). 
 
-PRs are the heart of collaboration on GitHub. When you open a pull request, you are putting forward your suggested changes, inviting us to review it, and requesting for these changes to be merged into our main branch.
+PRs are the heart of collaboration on GitHub.
+When you open a pull request, you are putting forward your suggested changes, inviting us to review it, and requesting for these changes to be merged into our main branch.
 
 Here's how to effectively contribute via a PR:
 
 - **Understand the Scope**: Before creating a PR, ensure it addresses an existing issue. Remember to link your PR to the issue it solves for easy tracking and understanding.
-- **Singular Focus**: Each PR should address a single issue or enhancement. Want to propose a larger change? Reach out to us on [Discord ](http://discord.com/invite/solidjs)and let's discuss the best way forward!
+- **Singular Focus**: Each PR should address a single issue or enhancement. Want to propose a larger change? Reach out to us on [Discord](http://discord.com/invite/solidjs) and let's discuss the best way forward!
 - **Drafts for Early Feedback**: If you're seeking early feedback but aren't quite finished with your changes, consider creating a draft PR. Simply prefix your PR title with `**[Draft]**`. This way, you can get input on your work-in-progress.
 - **Quality over Quantity**: Strive for the quality of your contribution rather than the quantity. A well-thought-out, cleanly coded, and thoroughly tested PR is much more valuable than a hastily done large one.
 Contributing via PRs not only enhances the project, but also allows you to be a part of the active community, sharing ideas, learning, and growing with the project. 
@@ -83,16 +90,19 @@ Contributing via PRs not only enhances the project, but also allows you to be a
 ### Writing a PR
 > Need help making a PR? [Join us on Discord](http://discord.com/invite/solidjs), we'll be more than happy to help you out!
 
-Contributions to the documentation site are made by editing the docs repository. You can do this directly on GitHub.com or by creating a copy of the repository locally, making your changes there, and contributing back to our repository.
+Contributions to the documentation site are made by editing the docs repository.
+You can do this directly on GitHub.com or by creating a copy of the repository locally, making your changes there, and contributing back to our repository.
 
 #### Examples of helpful PRs
 - PRs addressing an existing fix
-- unsolicited PRs addressing typos, broken links, and other minor problems
+- Unsolicited PRs addressing typos, broken links, and other minor problems
 
 ### Edit this page via GitHub
-Every page on [docs.solidjs.com ](https://docs.solidjs.com/)has an **Edit this page** link at the bottom. You can click on that button to edit the source code for that page in **GitHub**.
+Every page on [docs.solidjs.com](https://docs.solidjs.com/) has an **Edit this page** link at the bottom.
+You can click on that button to edit the source code for that page in **GitHub**.
 
-After you make your changes, click **Commit changes**. This will automatically create a [fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) of the docs in your GitHub account with the changes.
+After you make your changes, click **Commit changes**.
+This will automatically create a [fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) of the docs in your GitHub account with the changes.
 
 Once you have committed your edits within your fork, follow the prompts to create a **pull request** and submit your changes for review.
 
@@ -101,11 +111,13 @@ Every pull request needs to be reviewed by our contributors and approved by a ma
 ### Open a PR
 Once you have made your changes using your preferred method, you're ready to create a 'pull request'.
 
-This will let the Solid docs team know you have some changes you would like to propose. At this point, we can give you feedback and possibly request changes.
+This will let the Solid docs team know you have some changes you would like to propose.
+At this point, we can give you feedback and possibly request changes.
 
 [Read more about making a pull request in GitHub's docs.](https://docs.github.com/en/get-started/quickstart/contributing-to-projects#making-a-pull-request)
 
-Please include a clear title. The description will have some pre-filled questions that we would like you to answer.
+Please include a clear title.
+The description will have some pre-filled questions that we would like you to answer.
 
 Every pull request generates a preview of the site, including your proposed changes, using **Netlify** for anyone to see.
 
@@ -115,15 +127,19 @@ The docs site will be automatically updated whenever pull requests are merged.
 
 ## Helpful information
 ### Forks
-On GitHub, you will need a 'fork' of this repository to work on. This is your own copy of the code base where you can make changes. [You can read more about folks in GitHub's documentation.](https://guides.github.com/activities/forking/)
+On GitHub, you will need a 'fork' of this repository to work on.
+This is your own copy of the code base where you can make changes. You can read more about forks in [GitHub's documentation](https://guides.github.com/activities/forking/).
 
-Not sure how to get started with GitHub, forks, pull requests, or want a refresher? You can watch this video series: [How to Contribute to an Open Source Project on GitHub](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github).
+Not sure how to get started with GitHub, forks, pull requests, or want a refresher?
+You can watch this video series: [How to Contribute to an Open Source Project on GitHub](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github).
 
 #### Creating a fork
 To create your copy, click the `Fork` button at the top right of any page in this repository.
 
 #### Maintaining a fork
-When you first create your fork, it will be an exact copy of this repository. Over time, our docs will change as they are updated, but your fork won’t automatically stay up-to-date. Here are some ways to keep your fork in sync with this repo:
+When you first create your fork, it will be an exact copy of this repository.
+Over time, our docs will change as they are updated, but your fork won’t automatically stay up-to-date.
+Here are some ways to keep your fork in sync with this repo:
 
 ##### Update through GitHub UI
 1. Navigate to your fork on GitHub