From af0bb40dbb226d77772c561110e7e94e5da3f0b0 Mon Sep 17 00:00:00 2001 From: Thomas Gazagnaire Date: Thu, 17 Mar 2016 15:07:52 +0000 Subject: [PATCH] Fix a typo in the triaging guidelines Spotted by @dgageot Signed-off-by: Thomas Gazagnaire Upstream-commit: 2d2d1bb2c6485a1f41ecbc3ab0d93cfd83f63150 Component: engine --- components/engine/project/ISSUE-TRIAGE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/engine/project/ISSUE-TRIAGE.md b/components/engine/project/ISSUE-TRIAGE.md index 388e623507..57c441bf36 100644 --- a/components/engine/project/ISSUE-TRIAGE.md +++ b/components/engine/project/ISSUE-TRIAGE.md @@ -3,7 +3,7 @@ Triaging of issues Triage provides an important way to contribute to an open source project. Triage helps ensure issues resolve quickly by: -- Describing the issue's intent and purpose is conveyed precisely. This is necessary because it can be difficult for an issue to explain how an end user experiences an problem and what actions they took. +- Describing the issue's intent and purpose is conveyed precisely. This is necessary because it can be difficult for an issue to explain how an end user experiences a problem and what actions they took. - Giving a contributor the information they need before they commit to resolving an issue. - Lowering the issue count by preventing duplicate issues. - Streamlining the development process by preventing duplicate discussions.