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
0d279cb5
Commit
0d279cb5
authored
Sep 11, 2019
by
Matt Penna
Committed by
Evan Read
Oct 11, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Moved punctuation mark and unified structure
parent
e7cd8f6c
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
doc/development/documentation/styleguide.md
doc/development/documentation/styleguide.md
+3
-3
No files found.
doc/development/documentation/styleguide.md
View file @
0d279cb5
...
...
@@ -230,11 +230,11 @@ Do not include the same information in multiple places. [Link to a SSOT instead.
"Create a new merge request for Z.".
-
Avoid use of the future tense.
-
Instead of, "After you execute this command, the result will be displayed
",
say "After you execute this command, the result is displayed."
-
Instead of, "After you execute this command, the result will be displayed
,"
say "After you execute this command, the result is displayed."
-
Only use the future tense to convey when the action or result will actually occur at a future time.
-
Do not use contractions.
-
Say "do not", "cannot", or "does not" instead of "don't", "can't", "doesn't", and so on.
-
Possible exceptions are cases when a more familiar tone is desired, such as a blog post or other c
onversation
al context.
-
Instead of "don't", "can't", "doesn't", and so on, say "do not", "cannot", or "does not."
-
Possible exceptions are cases when a more familiar tone is desired, such as a blog post or other c
asu
al context.
-
Do not use slashes to clump different words together.
-
Instead of "and/or", consider saying "or", or use another sensible construction.
-
Other examples include "author/asignee" and "namespace/repository name". Break apart any such instances in an appropriate way.
...
...
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