Skip to content

Commit e5b34bf

Browse files
pepelsbeyhamishwilleebsmthJosh-Cena
authored
Add branded capitalization guide (mdn#36846)
* Add branded capitalization guide * Update files/en-us/mdn/writing_guidelines/writing_style_guide/index.md * Update files/en-us/mdn/writing_guidelines/writing_style_guide/index.md Co-authored-by: Joshua Chen <sidachen2003@gmail.com> --------- Co-authored-by: Hamish Willee <hamishwillee@gmail.com> Co-authored-by: Brian Smith <brian@smith.berlin> Co-authored-by: Joshua Chen <sidachen2003@gmail.com>
1 parent 1d5f6ed commit e5b34bf

File tree

1 file changed

+4
-0
lines changed
  • files/en-us/mdn/writing_guidelines/writing_style_guide

1 file changed

+4
-0
lines changed

files/en-us/mdn/writing_guidelines/writing_style_guide/index.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -282,6 +282,10 @@ Some examples include:
282282
- JavaScript (a trademark of Oracle Corporation, it should always be written as trademarked)
283283
- Python, TypeScript, Django, and other programming languages and framework names
284284

285+
Some tool names and projects have their own branded capitalization rules. These might require names that are all lower case ("npm" or "webpack"), all upper case ("UNIX", "GNOME", "VIM"), or mixed case ("TypeScript", "macOS", or "jQuery").
286+
287+
The branded capitalization from the official website or documentation should always be used, even at the start of a sentence. If you are uncomfortable with a sentence starting with a lowercase letter, we recommend rewording to avoid the problem. For example, you might say "You can use the npm package manager to..." instead of "npm allows you to...".
288+
285289
### Contractions
286290

287291
Our writing style tends to be casual, so you should feel free to use contractions (e.g., "don't", "can't", "shouldn't"), if you prefer.

0 commit comments

Comments
 (0)