Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
50f5f3c7
Commit
50f5f3c7
authored
Jan 09, 2019
by
carla
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
docs: Fix 'Gilab' typo
parent
a1b84c0c
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
doc/development/documentation/styleguide.md
doc/development/documentation/styleguide.md
+1
-1
No files found.
doc/development/documentation/styleguide.md
View file @
50f5f3c7
...
...
@@ -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
[
Gi
t
Lab 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
)
.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment