diff options
| author | carla <carla@tuxcomputing.com> | 2019-01-09 09:28:01 +0300 |
|---|---|---|
| committer | carla <carla@tuxcomputing.com> | 2019-01-09 09:28:01 +0300 |
| commit | 50f5f3c72178fb4ede1bdcd317ca92cd124f304f (patch) | |
| tree | 97567a046ea13b95880c27b09bd11ee8fbaf342f | |
| parent | a1b84c0ce7fc2e3f910ff30abe1a01dd2422ffbf (diff) | |
docs: Fix 'Gilab' typo
| -rw-r--r-- | doc/development/documentation/styleguide.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/documentation/styleguide.md b/doc/development/documentation/styleguide.md index a18c21d921a..590dc41cf98 100644 --- a/doc/development/documentation/styleguide.md +++ b/doc/development/documentation/styleguide.md @@ -34,7 +34,7 @@ in October, 2018. The [`gitlab-kramdown`](https://gitlab.com/gitlab-org/gitlab_kramdown) gem will support all [GFM markup](../../user/markdown.md) in the future. For now, use regular markdown markup, following the rules on this style guide. For a complete -Kramdown reference, check the [GiLab Markdown Kramdown Guide](https://about.gitlab.com/handbook/product/technical-writing/markdown-guide/). +Kramdown reference, check the [GitLab Markdown Kramdown Guide](https://about.gitlab.com/handbook/product/technical-writing/markdown-guide/). Use Kramdown markup wisely: do not overuse its specific markup (e.g., `{:.class}`) as it will not render properly in [`/help`](#gitlab-help). |