Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add section on acronyms & abbreviations #239

Open
sffrench opened this issue Jun 10, 2021 · 4 comments
Open

Add section on acronyms & abbreviations #239

sffrench opened this issue Jun 10, 2021 · 4 comments
Labels
enhancement Will improve the guide but is not a bug or blocker.

Comments

@sffrench
Copy link
Contributor

Word nerds:
acronyms & abbreviations - updated with more info, and added to the corporate style guide

Things we should add to this entry:

  • Acrobot (get instructions from David O Brien)
  • Link to acronyms list that IC made on

"acronyms & abbreviations
Expand all acronyms and abbreviations on first use. Spell out acronyms or initializations before using them in text, e.g., ""Embedded DevKit (EDK)"", unless the acronym or initials stand for a proper noun, then use sentence case for the spelled-out version, e.g., ""central processing unit (CPU)"".
Avoid using acronyms and abbreviations for product names. Refer to products by full name, as shown in the official Red Hat product and solution names list (Google docs). Do not use product acronyms in formal communications.

Exceptions: There are cases where acronyms and abbreviations are acceptable. These include:

After the first use in technical, customer-facing documentation. Examples:
Getting started guides.
Install guides.
Documentation on the Customer Portal.
Knowledgebase solutions and articles.
Bugzilla entries.
Support case summaries or details.
Other subscription materials and resources.
Training materials.
When space is physically limited, such as:
Very small web or print ads.
Social media with a character or display limit (e.g. Twitter, Instagram).
Products where the abbreviation or acronym is part of the official product name, including Red Hat AMQ. (In these cases, the abbreviation is more well-known than its expansion.)

Always ensure that the acronyms or abbreviations you use will not be confusing or conflict with other offerings or common terms.

To form the plural of an acronym, add a trailing, lowercase ""s"" with no apostrophe, e.g., ROMs, PINs, BIOSs.

Exception: Technical documentation uses ""es"" in some cases, for example, BIOSes, OSes, and similar terms."

@sffrench sffrench added the enhancement Will improve the guide but is not a bug or blocker. label Jun 10, 2021
@daobrien
Copy link
Collaborator

"Link to acronyms list that IC made on" ?
I'm not sure what this means.

@sffrench
Copy link
Contributor Author

I just copied this stuff from the word nerds spreadsheet, I am not sure either.

@daobrien
Copy link
Collaborator

A lot of the other content in the original issue is already in the RH Tech Writing Guide, although some bits might be missing. I can have a look and find them.

Note too that is not 100% accurate: "Expand all acronyms and abbreviations on first use."
We don't expand common acronyms and abbreviations (RAM, HTTP, FTP) unless he happen to be explaining or teaching what they actually mean.

@daobrien
Copy link
Collaborator

This is marked as "Complete" in their spreadsheet, which is unfortunate, because it's incomplete. I can review our guide and make sure nothing is missing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Will improve the guide but is not a bug or blocker.
Projects
None yet
Development

No branches or pull requests

2 participants