-
Notifications
You must be signed in to change notification settings - Fork 25
daobrien/457 vale check #464
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -51,15 +51,13 @@ | |
| <term>offline backup</term> | ||
| <listitem> | ||
| <para> | ||
| Correct. Use this term to refer to backing up a database while the database is not being accessed by applications. Do not use "cold backup" or any other variations. | ||
| Correct. | ||
| Use this term to refer to backing up a database while the database is not being accessed by applications. | ||
| Do not use "cold backup" or any other variations. | ||
| </para> | ||
| <para> | ||
| The counterpart to this term is "online backup", to refer to the process of backing up a database while it is being accessed by other applications. Do not use "hot backup" or any other variations. | ||
| <!-- Deleted footnote: URL is no longer valid. --> | ||
| <!-- <footnote> <para> | ||
| <ulink url="http://www-01.ibm.com/software/globalization/terminology/o.html" /> | ||
| </para> | ||
| </footnote> --> | ||
| The counterpart to this term is "online backup", to refer to the process of backing up a database while it is being accessed by other applications. | ||
| Do not use "hot backup" or any other variations. | ||
| </para> | ||
|
|
||
| </listitem> | ||
|
|
@@ -69,12 +67,13 @@ | |
| <term>OK</term> | ||
| <listitem> | ||
| <para> | ||
| When referring to the <guibutton>OK</guibutton> button, it is not necessary to use "button" in the sentence. For example, "Click <guibutton>OK</guibutton> to close the dialog box." | ||
| When referring to the <guibutton>OK</guibutton> button, it is not necessary to use "button" in the sentence. | ||
| For example, "Click <guibutton>OK</guibutton> to close the dialog box." | ||
| </para> | ||
| <para> | ||
| Use "OK" only to refer to an interface element, not in general text. For example, instead of using "It is OK to run the command", use alternative wording, such as "You can run the command". | ||
| Use "OK" only to refer to an interface element, not in general text. | ||
| For example, instead of using "It is OK to run the command", use alternative wording, such as "You can run the command". | ||
| </para> | ||
| <!-- Added paragraph to avoid "OK" when not referring to a button. --> | ||
|
|
||
| </listitem> | ||
|
|
||
|
|
@@ -92,7 +91,8 @@ | |
| <term>once</term> | ||
| <listitem> | ||
| <para> | ||
| Use only to mean "one time". Do not use as a conjunction to mean "after" or "when". | ||
| Use only to mean "one time". | ||
| Do not use as a conjunction to mean "after" or "when". | ||
| </para> | ||
| <para> | ||
| Example 1: Instead of "Once the name is set for a network interface on the system, the name of the interface does not change", use "When the name is set for a network interface on the system, the name of the interface does not change". | ||
|
|
@@ -162,7 +162,9 @@ | |
| <term>on-the-fly</term> | ||
| <listitem> | ||
| <para> | ||
| Do not use. Avoid idioms, which might not be globally known. In this case, for example, "real time" is both non-idiomatic and more technically accurate. | ||
| Do not use. | ||
| Avoid idioms, which might not be globally known. | ||
| In this case, for example, "real time" is both non-idiomatic and more technically accurate. | ||
| </para> | ||
|
|
||
| </listitem> | ||
|
|
@@ -172,7 +174,10 @@ | |
| <term>oops</term> | ||
| <listitem> | ||
| <para> | ||
| A kernel oops is an error message that is generated as a result of a bug in the kernel. Do not use "oops" on its own. Also, avoid using "kernel oops" at the beginning of a sentence. See also "kernel panic". | ||
| A kernel oops is an error message that is generated because of a bug in the kernel. | ||
| Do not use "oops" on its own. | ||
| Also, avoid using "kernel oops" at the beginning of a sentence. | ||
| See also "kernel panic". | ||
| </para> | ||
|
|
||
| </listitem> | ||
|
|
@@ -244,10 +249,11 @@ | |
| <term>open source way</term> | ||
| <listitem> | ||
| <para> | ||
| A phrase that was coined by the Red Hat community and adopted by opensource.com in 2009. It is a reference to an "open source method", as in "Let's develop this project the open source way." | ||
| A phrase that was coined by the Red Hat community and adopted by opensource.com in 2009. | ||
| It is a reference to an "open source method", as in "Let's develop this project the open source way." | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Given our guidance to avoid contractions, we should avoid them here in a quoted example. |
||
| </para> | ||
| <para> | ||
| Do not use to suggest that something is being done only in the "spirit" of open source without actually having an open source policy as defined by <ulink url="http://opensource.org/osd">Open Source Initiative</ulink>, to avoid diluting the legal meaning of the term "open source". | ||
| Do not use to suggest that something is being done only in the "spirit" of open source without having an open source policy as defined by <ulink url="http://opensource.org/osd">Open Source Initiative</ulink>, to avoid diluting the legal meaning of the term "open source". | ||
| </para> | ||
|
|
||
| </listitem> | ||
|
|
@@ -287,7 +293,10 @@ | |
| <term>overcloud</term> | ||
| <listitem> | ||
| <para> | ||
| <emphasis>n.</emphasis> Always lowercase. This is a concept, not a technology or product name. Being a common noun, it requires an article in most cases. See also <xref linkend="undercloud" />. | ||
| <emphasis>n.</emphasis> Always lowercase. | ||
| This is a concept, not a technology or product name. | ||
| Being a common noun, it normally requires an article. | ||
| See also <xref linkend="undercloud" />. | ||
| </para> | ||
|
|
||
| </listitem> | ||
|
|
@@ -297,7 +306,8 @@ | |
| <term>override</term> | ||
| <listitem> | ||
| <para> | ||
| Correct. Do not use "over-ride" or "over ride". | ||
| Correct. | ||
| Do not use "over-ride" or "over ride". | ||
| </para> | ||
|
|
||
| </listitem> | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -72,10 +72,13 @@ | |
| <term>plain text</term> | ||
| <listitem> | ||
| <para> | ||
| <emphasis>n.</emphasis> Two words. In most cases, do not use "plaintext", "cleartext", or other variants. | ||
| <emphasis>n.</emphasis> Two words. | ||
| In most cases, do not use "plaintext", "cleartext", or other variants. | ||
| </para> | ||
| <para> | ||
| Cryptographers distinguish between "cleartext" (unencrypted data) and "plaintext" (unencrypted data as input to an encryption algorithm). Red Hat uses "plain text" as a plain English denotation of all unencrypted information, whether it is stored or being fed to an encryption algorithm. Unless it is necessary to make the cryptographer's distinction, do not use "plaintext" or "cleartext". | ||
| Cryptographers distinguish between "cleartext" (unencrypted data) and "plaintext" (unencrypted data as input to an encryption algorithm). | ||
| Red Hat uses "plain text" as a plain English denotation of all unencrypted information, whether it is stored or being fed to an encryption algorithm. | ||
| Unless it is necessary to make the cryptographer's distinction, do not use "plaintext" or "cleartext". | ||
| </para> | ||
|
|
||
| </listitem> | ||
|
|
@@ -85,9 +88,9 @@ | |
| <term>please</term> | ||
| <listitem> | ||
| <para> | ||
| Do not use. Instead of saying "Please see the <citetitle>Getting Started Guide</citetitle>", use "See the <citetitle>Getting Started Guide."</citetitle> | ||
| Do not use. | ||
| Instead of saying "Please see the <citetitle>Getting Started Guide</citetitle>", use "See the <citetitle>Getting Started Guide."</citetitle> | ||
| </para> | ||
| <!-- Added justification --> | ||
| <para> | ||
| Technical information requires an authoritative tone; terms of politeness convey the wrong tone for technical information and are not regarded the same way in all cultures. | ||
| </para> | ||
|
|
@@ -109,12 +112,11 @@ | |
| <term>plug-in</term> | ||
| <listitem> | ||
| <para> | ||
| <emphasis>n.</emphasis> Write hyphenated. Do not use "plugin". | ||
| <emphasis>n.</emphasis> Write hyphenated. | ||
| Do not use "plugin". | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Although some product terminology uses "plugin", and the CCS Supplementary Style Guide now defines the unhyphenated form as the standard. |
||
| </para> | ||
| <para> | ||
| A hardware or software module that adds a specific feature or service to a larger system. | ||
| <!-- Removed dated example. --> | ||
| <!-- For example, a number of plug-ins are available for the Netscape Navigator browser that enable it to display different types of audio or video messages. Navigator plug-ins are based on MIME file types. --> | ||
| </para> | ||
|
|
||
| </listitem> | ||
|
|
@@ -173,10 +175,12 @@ | |
| <emphasis>n.</emphasis> The name of the Power architecture is "Power", but the designation of individual chips tends to be either "PowerPC" or "POWER". Refer to IBM marketing or the <ulink url="http://openpowerfoundation.org">Open Power Foundation</ulink> if unsure. | ||
| </para> | ||
| <para> | ||
| Do not use the "PPC64" or "ppc64le" shorthand. Depending on context, either "64-bit PowerPC" (which covers most 64-bit PowerPC implementations) or "64-bit IBM Power Series" (which covers the IBM POWER2 and IBM POWER8 and POWER9 series) is correct. Additional application binary interface (ABI) features are important, but are not officially part of the Power architecture name, so use them as descriptors, such as "64-bit IBM Power Series in little-endian mode". | ||
| Do not use the "PPC64" or "ppc64le" shorthand. | ||
| Depending on context, either "64-bit PowerPC" (which covers most 64-bit PowerPC implementations) or "64-bit IBM Power Series" (which covers the IBM POWER2 and IBM POWER8 and POWER9 series) is correct. | ||
| Additional application binary interface (ABI) features are important, but are not officially part of the Power architecture name, so use them as descriptors, such as "64-bit IBM Power Series in little-endian mode". | ||
| </para> | ||
| <para> | ||
| Note: The PowerPC version of Red Hat Enterprise Linux runs on 64-bit IBM Power Series hardware in almost all cases. | ||
| Note: The PowerPC version of Red Hat Enterprise Linux runs on 64-bit IBM Power Series hardware in most cases. | ||
| </para> | ||
|
|
||
| </listitem> | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know that Microsoft advises otherwise, but I don't much like this word replacement at the start of this sentence, which results in a sentence in the format "Or A, or B, or C".