Fixing grammar errors (nodejs#2852)

Author: Zack-Dx

CONTRIBUTING.md

@@ -58,7 +58,7 @@ This project follows the [Conventional Commits][] specification.
 
 Basic rules:
 
-* Commit messages must be prefixed with the name of the changed subsystem, followed by a colon and a space and start with an imperative verb. Check the output of `git log --oneline files/you/changed` to find out what subsystems your changes touch.
+* Commit messages must be prefixed with the name of the changed subsystem, followed by a colon and a space, and start with an imperative verb. Check the output of `git log --oneline files/you/changed` to find out what subsystems your changes touch.
 
   Supported subsystems:
 
@@ -74,15 +74,15 @@ Basic rules:
 
 * Pull Requests must be open for at least 48 hours unless changes include errata fixes, infrastructure maintenance, or tests
 * There must be no objections after a 48 hour period
-* Pull Requests for a new feature or bug fix must include tests
+* Tests must be included in Pull Requests for new features or bug fixes
 
 The default for each contribution is that it is accepted once no collaborator has an objection. During review collaborators may also request that a specific contributor who is most versed in a particular area gives a "LGTM" before the PR can be merged.
 
 In the case of an objection being raised in a pull request by another collaborator, all involved collaborators should seek to arrive at a consensus by way of addressing concerns being expressed by discussion, compromise on the proposed change, or withdrawal of the proposed change.
 
 ## When Landing
 
-* Do not use merge button
+* Do not use the merge button
 * [`squash`][] pull-requests made up of multiple commits
 * Land how you like as long as there are no merge commits
 

docs/project-overview.md

@@ -7,14 +7,14 @@ A quick look at some of the top-level files and directories found in this projec
 1. **`/node_modules`**: The directory where all of the modules of code that your project depends on (npm packages) are automatically installed.
 1. **`/src`**: This directory will contain all of the code related to what you will see on the front-end of your site (what you see in the browser), like your site header, or a page template. "Src" is a convention for "source code."
 1. **`/content`**: This directory contains all the contents of (pages, blog posts, doc pages) of the website. They're all done in Markdown and MDX.
-1. **`/test`**: Tests for this projects are stored in this directory. This project uses [Jest](https://jestjs.io/) as it's testing framework.
+1. **`/test`**: Tests for this projects are stored in this directory. This project uses [Jest](https://jestjs.io/) as its testing framework.
 1. **`/util-node`**: Custom utility functions that require nodeJs to run can be stored in files inside this directory. An example is the create-slug function in the createSlug.js file that generates unique slugs for articles.
 1. **`.gitignore`**: This file tells git which files it should not track/not maintain a version history.
 1. **`.nvmrc`**: nvm configuration so packages work as they should
 1. **`.prettierrc`**: This is a configuration file for a tool called [Prettier](https://prettier.io/), which is a tool to help keep the formatting of your code consistent.
 1. **`empty.env`**: Rename to **`.env`** and set your Contentful API key
 1. **`gatsby-browser.js`**: This file is where Gatsby expects to find any usage of the [Gatsby browser APIs](https://www.gatsbyjs.com/docs/browser-apis/) (if any). These allow customization/extension of default Gatsby settings affecting the browser.
-1. **`gatsby-config.js`**: This is the main configuration file for a Gatsby site. This is where you can specify information about your site (metadata) like the site title and description, which Gatsby plugins you'd like to include, etc. (Check out the [config docs](https://www.gatsbyjs.com/docs/reference/config-files/gatsby-config/) for more detail).
+1. **`gatsby-config.js`**: This is the main configuration file for a Gatsby site. This is where you can specify information about your site (metadata), like the site title and description, which Gatsby plugins you'd like to include, etc. (Check out the [config docs](https://www.gatsbyjs.com/docs/reference/config-files/gatsby-config/) for more detail).
 1. **`gatsby-node.js`**: This file is where Gatsby expects to find any usage of the [Gatsby node APIs](https://www.gatsbyjs.com/docs/reference/config-files/gatsby-node/) (if any). These allow customization/extension of default Gatsby settings affecting pieces of the site build process.
 1. **`LICENSE`**: Gatsby is licensed under the MIT license.
 1. **`package-lock.json`** (See `package.json` below, first). This is an automatically generated file based on the exact versions of your npm dependencies that were installed for your project. (You won't change this file directly)
@@ -35,5 +35,5 @@ The content folder is responsible for aggregating all the content of the Website
 
 Looking for more guidance? Full documentation for Gatsby lives [on the website](https://www.gatsbyjs.com/). Here are some places to start:
 
-- **For most developers, we recommend starting with our [in-depth tutorial for creating a site with Gatsby](https://www.gatsbyjs.com/docs/tutorial/).** It starts with zero assumptions about your level of ability and walks through every step of the process.
-- **To dive straight into code samples head [to our documentation](https://www.gatsbyjs.com/docs/).** In particular, check out the "Guides", API reference, and "Advanced Tutorials" sections in the sidebar.
+- **For most developers, we recommend starting with our [in-depth tutorial for creating a site with Gatsby](https://www.gatsbyjs.com/docs/tutorial/).** It starts with zero assumptions about your level of ability and walks you through every step of the process.
+- **To dive straight into code samples, head [to our documentation](https://www.gatsbyjs.com/docs/).** In particular, check out the "Guides", "API Reference", and "Advanced Tutorials" sections in the sidebar.