summaryrefslogtreecommitdiff
path: root/doc/development/documentation
diff options
context:
space:
mode:
authorMarcel Amirault <ravlen@gmail.com>2019-03-25 04:56:57 +0000
committerEvan Read <eread@gitlab.com>2019-03-25 04:56:57 +0000
commitb41b03d47c529726501fb03181b9f065170945db (patch)
treef4d44a305fb9cdc32e821a82beed65df4bc3a00d /doc/development/documentation
parent6c36fe9d294a7db57221766ff33374f38bbffadb (diff)
downloadgitlab-ce-b41b03d47c529726501fb03181b9f065170945db.tar.gz
Docs: Fix missed or newly added broken anchors
Diffstat (limited to 'doc/development/documentation')
-rw-r--r--doc/development/documentation/feature-change-workflow.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/documentation/feature-change-workflow.md b/doc/development/documentation/feature-change-workflow.md
index 3f31fe5ca19..1f68b6a6a70 100644
--- a/doc/development/documentation/feature-change-workflow.md
+++ b/doc/development/documentation/feature-change-workflow.md
@@ -78,7 +78,7 @@ For issues requiring any new or updated documentation, the Product Manager (PM)
must:
- Add the `Documentation` label.
-- Confirm or add the [documentation requirements](#documentation-requirements).
+- Confirm or add the [documentation requirements](#documentation-requirements-in-feature-issues).
- Ensure the issue contains any new or updated feature name, overview/description,
and use cases, as required per the [documentation structure and template](structure.md), when applicable.