Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Commit bf719ba

Browse files
authored
Small tweak
1 parent 44ffa8a commit bf719ba

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/contributor-guide/processing-workflow.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ group: contributor-guide
33
title: GitHub issue processing workflow
44
---
55

6-
The Github issue workflow ensures that issues are clear, well written, and thoroughly vetted. Following these procedures allows valid issues to get the attention they deserve.
6+
The GitHub issue workflow ensures that issues are clear, well written, and thoroughly vetted. Following these procedures allows valid issues to get the attention they deserve.
77

88
Magento issues that are reported on the public [GitHub](https://github.com/magento/magento2/issues) must pass through a series of gates, or stages of quality assessment, to ensure that their quality meets our standards. There are three gates, and an issue must pass through all three of these assessments before we will transfer it to either Magento core developers or community developers.
99
The purpose of these gates is to identify core technical issues common to all reported tickets, and to show the progress on each reported issue.
@@ -119,4 +119,4 @@ Label descriptions:
119119

120120
## Questions and Discussion
121121

122-
If you have any questions, feedback, or proposals for this workflow, join the [Community Engineering Slack Workspace](https://opensource.magento.com/slack). We have a [#backlog-maintainers](https://magentocommeng.slack.com/messages/CCV2S9P7S) channel specifically for these discussions.
122+
If you have any questions, feedback, or proposals for this workflow, join the [Community Engineering Slack Workspace](https://opensource.magento.com/slack). We have a [#backlog-maintainers](https://magentocommeng.slack.com/messages/CCV2S9P7S) channel specifically for these discussions.

0 commit comments

Comments
 (0)