diff options
| author | Stan Hu <stanhu@gmail.com> | 2019-01-09 10:18:33 +0300 |
|---|---|---|
| committer | Stan Hu <stanhu@gmail.com> | 2019-01-09 10:18:33 +0300 |
| commit | cfaa19f21ea4f01ef8e77fbacbdfd0e1b965a8aa (patch) | |
| tree | 09b09be088155d19d668f502ad994ede9c1e3971 | |
| parent | 9370ba6fc5dc86fdc6992e5a30dd82aab71f7451 (diff) | |
| parent | 50f5f3c72178fb4ede1bdcd317ca92cd124f304f (diff) | |
Merge branch 'patch-37' into 'master'
docs: Fix 'Gilab' typo
See merge request gitlab-org/gitlab-ce!24260
| -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). |