From 17451e8ce8bff057db17411f0b61572c8fa3d9b4 Mon Sep 17 00:00:00 2001
From: Seth Berger <4310743-sethgitlab@users.noreply.gitlab.com>
Date: Thu, 12 Sep 2019 00:47:39 +0000
Subject: Apply suggestion to
 doc/development/documentation/feature-change-workflow.md

---
 doc/development/documentation/feature-change-workflow.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/doc/development/documentation/feature-change-workflow.md b/doc/development/documentation/feature-change-workflow.md
index 3dae4ca2518..99cd474e9bb 100644
--- a/doc/development/documentation/feature-change-workflow.md
+++ b/doc/development/documentation/feature-change-workflow.md
@@ -92,8 +92,7 @@ do the following:
 
 #### Authoring
 
-As a developer, you should ship the documentation with the code of the feature that
-you are creating or updating. The documentation is an essential part of the product.
+As a developer, if a ~feature issue also contains the ~Documentation label, you must ship the new or updated documentation with the code of the feature. The documentation is an essential part of the product.
 Technical writers are happy to help, as requested and planned on an issue-by-issue basis.
 
 Follow the process below unless otherwise agreed with the product manager and technical writer for a given issue:
-- 
cgit v1.2.3