minor grammatical fixes (#9530)

docs/docs/how-to-label-an-issue.md

@@ -28,7 +28,7 @@ You can get an invite to the team by having a Pull Request merged into the Gatsb
 
 ## How to label an issue
 
-Ideally every issue should have a single `type:` label applied to it. Optionally a `status:` label, or other labels may also be applied.
+Ideally, every issue should have a single `type:` label applied to it. Optionally a `status:` label or other labels may also be applied.
 
 Before continuing, get familiar with [Gatsby's issue labels and their descriptions](https://github.com/gatsbyjs/gatsby/issues/labels).
 
@@ -42,7 +42,7 @@ The rest of this document will describe how to choose the right labels for an is
 
 ### Find an issue that you're interested in
 
-Start with [Gatsby's issues list](https://github.com/gatsbyjs/gatsby/issues) and scroll through until you see a recent one that strikes your interest. Alternatively you can view the [list of unlabelled issues](https://github.com/gatsbyjs/gatsby/issues?q=is%3Aopen+is%3Aissue+no%3Alabel).
+Start with [Gatsby's issues list](https://github.com/gatsbyjs/gatsby/issues) and scroll through until you see a recent one that strikes your interest. Alternatively, you can view the [list of unlabelled issues](https://github.com/gatsbyjs/gatsby/issues?q=is%3Aopen+is%3Aissue+no%3Alabel).
 
 ### Read the issue
 
@@ -78,7 +78,7 @@ Examples of applying `status:` labels might be:
 
 - An issue describing a bug without clear steps to reproduce could be labelled with `status: needs reproduction`
 
-- An issue describing a bug where there's steps to reproduce the bug _and_ you've run the code locally and seen the error yourself can be labelled `status: confirmed`
+- An issue describing a bug where there are steps to reproduce the bug _and_ you've run the code locally and seen the error yourself can be labelled `status: confirmed`
 
 ### Choose any other labels