summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaulo Ribeiro <paulo@diffraction.pt>2019-09-09 12:51:41 +0000
committerAchilleas Pipinellis <axil@gitlab.com>2019-09-09 12:51:41 +0000
commit06d4c54119db8e9806604871514bc4bd8af88c82 (patch)
tree2371d129dafe7775e51b21b68db2a08179440bb8
parent5abc37bd85ca3ab28f7fb6fdbb6db8161f51d8fb (diff)
downloadgitlab-ce-06d4c54119db8e9806604871514bc4bd8af88c82.tar.gz
Correct typo in documentation
-rw-r--r--doc/development/documentation/styleguide.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/documentation/styleguide.md b/doc/development/documentation/styleguide.md
index 09dd31e2aee..4a50e90a26c 100644
--- a/doc/development/documentation/styleguide.md
+++ b/doc/development/documentation/styleguide.md
@@ -85,7 +85,7 @@ The more we reflexively add useful information to the docs, the more (and more s
If you have questions when considering, authoring, or editing docs, ask the Technical Writing team on Slack in `#docs` or in GitLab by mentioning the writer for the applicable [DevOps stage](https://about.gitlab.com/handbook/product/categories/#devops-stages). Otherwise, forge ahead with your best effort. It does not need to be perfect; the team is happy to review and improve upon your content. Please review the [Documentation guidelines](index.md) before you begin your first documentation MR.
-Having a knowledge base is any form that is separate from the documentation would be against the docs-first methodology because the content would overlap with the documentation.
+Having a knowledge base in any form that is separate from the documentation would be against the docs-first methodology because the content would overlap with the documentation.
## Markdown