From 3d880b6b1e93fb5e349fe04ac674293176f4c2c5 Mon Sep 17 00:00:00 2001 From: Nievac Date: Wed, 16 Oct 2019 10:48:46 +0800 Subject: [PATCH] Minor grammar correction --- docs/contributing/triaging-github-issues.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/contributing/triaging-github-issues.md b/docs/contributing/triaging-github-issues.md index b2742cb61d72b..cfc24c0ac66e1 100644 --- a/docs/contributing/triaging-github-issues.md +++ b/docs/contributing/triaging-github-issues.md @@ -6,7 +6,7 @@ title: Triaging GitHub Issues On the Gatsby core team, we've found patterns that help us effectively triage incoming GitHub issues, provide answers to the community's questions, identify bugs, and provide contribution opportunities. Triaging issues is a great way to contribute to the Gatsby community and share your knowledge, without necessarily requiring a lot of deep context about the way the Gatsby codebase works. -We want to share these patterns with the broader community, so that if you're interesting in helping us triage, you're able to do so more effectively! +We want to share these patterns with the broader community, so that if you're interested in helping us triage, you're able to do so more effectively! In this document we’ll answer common questions, list guidelines and illustrate a decision tree.