From 1752d9ee2d0a4468c32f05493479f07176a528bc Mon Sep 17 00:00:00 2001 From: Brad Topol Date: Sat, 20 Jun 2020 00:39:12 -0400 Subject: [PATCH] updated phrasing --- content/en/docs/contribute/advanced.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/contribute/advanced.md b/content/en/docs/contribute/advanced.md index 5bed4259d7..594816a2b5 100644 --- a/content/en/docs/contribute/advanced.md +++ b/content/en/docs/contribute/advanced.md @@ -39,7 +39,7 @@ The PR wrangler’s duties include: - Assign `Doc Review: Open Issues` or `Tech Review: Open Issues` for PRs that have been reviewed and require further input or action before merging. - Assign `/lgtm` and `/approve` labels to PRs that can be merged. - Merge PRs when they are ready, or close PRs that shouldn’t be accepted. - - Because we are limited on resources, we are willing to accept solid technical content even if all [style guidelines](/docs/contribute/style/style-guide/) are not met. Consider merging this type of content and opening a good first issue to address the style concerns. + - Consider accepting accurate technical content even if the content meets only some of the docs' [style guidelines](/docs/contribute/style/style-guide/). Open a new issue with the label `good first issue` to address style concerns. - Triage and tag incoming issues daily. See [Triage and categorize issues](/docs/contribute/review/for-approvers/#triage-and-categorize-issues) for guidelines on how SIG Docs uses metadata. ### Helpful GitHub queries for wranglers