diff options
author | Mike Lewis <mlewis@gitlab.com> | 2019-02-14 15:06:49 +0000 |
---|---|---|
committer | Mike Lewis <mlewis@gitlab.com> | 2019-02-14 15:06:49 +0000 |
commit | 2f66d23d938e995fab3f599adc8b03d82c805486 (patch) | |
tree | 1ac42384e3cfd30f55ec4846a77f4cd76c52b03c | |
parent | e1a1ca0ed81d6212737f11e5c3697d438e013409 (diff) | |
download | gitlab-ce-2f66d23d938e995fab3f599adc8b03d82c805486.tar.gz |
Fix typo and updatee tech writer planning section
-rw-r--r-- | doc/development/documentation/feature-change-workflow.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/documentation/feature-change-workflow.md b/doc/development/documentation/feature-change-workflow.md index 41068b5cb6b..dac0021a4b8 100644 --- a/doc/development/documentation/feature-change-workflow.md +++ b/doc/development/documentation/feature-change-workflow.md @@ -146,9 +146,9 @@ Any party can raise the item to the PM for review at any point: the dev, the tec #### Planning - The technical writer monitors the documentation needs of issues assigned to the current and next milestone -for their DevOps stage(s), and participates in any needed discussion on docs planning +for their DevOps stage(s), and participates in any needed discussion on docs planning and requirements refinement with the dev, PM, and others. -- The technical writer will review these again upon the kickoff and provide feedback, as needed. +- The technical writer will review these requirements again upon the kickoff and provide feedback, as needed. This is not a blocking review and developers should not wait to work on docs. #### Collaboration |