Commit d4c923e6 authored by Mike Lewis's avatar Mike Lewis

Clarify language on review/merge requirements

parent be17281e
...@@ -266,9 +266,8 @@ correct by the person merging the MR or the SME (such as a developer) who contri ...@@ -266,9 +266,8 @@ correct by the person merging the MR or the SME (such as a developer) who contri
Further needs for ‘what would make this doc even better’ should be immediately addressed in a Further needs for ‘what would make this doc even better’ should be immediately addressed in a
follow-up MR or issue. follow-up MR or issue.
The individual who merges the documentation must have also reviewed the documentation The individual who merges the documentation must reviewed the documentation
for the above standard. Typically this is a technical writer, but others, such as Support Managers, for the above standard.
can freely merge smaller changes. See the [Documentation Workflows](workflow.md).
NOTE: **Note:** NOTE: **Note:**
If the release version you want to add the documentation to has already been If the release version you want to add the documentation to has already been
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment