diff --git a/en-US/A.xml b/en-US/A.xml index 41aa978..26b30c4 100644 --- a/en-US/A.xml +++ b/en-US/A.xml @@ -17,7 +17,8 @@ - agile, agile development + agile + agile development adj. Use only as an adjective. It is not a proper noun, nor is it owned or trademarked and should not be capitalized. @@ -27,7 +28,8 @@ - air gap + air gap + air wall n. Use "air gap" to describe systems that are separated, not by software, but physically. Do not use "air wall." "Air gap" is preferred in technical publications because there is no actual wall that you need to breach, but rather a gap that you need to bridge. You cannot break through something that does not exist. @@ -36,12 +38,16 @@ - - a.m. and p.m. + + a.m. + am Correct. Use the lowercase form and include the periods, and use a preceding space. + + See also . + See The IBM Style Guide for a full discussion of how to represent times. @@ -50,7 +56,8 @@ - all-in-one + all-in-one + allinone n., adj. Correct. Hyphenate in both cases. Do not use "allinone" or other variations. @@ -59,15 +66,19 @@ - - AMD64 and Intel 64 + + AMD64 Correct. Do not use "Hammer," "x86_64," "x86-64," "x64," "64-bit x86" or other variations as the name of this architecture. - The correct term for AMD's implementation of this architecture is "AMD64." The correct term for Intel's implementation of this architecture is "Intel® 64." Until late 2006, Intel's official name for the architecture was "Intel EM64T" (for Extended Memory 64 Technology). They have since changed the name to "Intel® 64" however, and Red Hat documentation should reflect this change. When discussing the architecture generally, reference both implementations specifically. + The correct term for AMD's implementation of this architecture is "AMD64." + When discussing the architecture generally, reference both AMD64 and Intel 64 implementations specifically. + + See also . + The AMD64 logo is trademarked; the term "AMD64" is not. For more information about AMD trademarks, see the AMD Trademark Information page at . @@ -82,20 +93,23 @@ - ATM + ATM - Initialism for Asynchronous Transfer Mode, a network technology based on transferring data in cells or packets of a fixed size. The cell size used with ATM is relatively small compared to units used with older technologies. + Initialism for Asynchronous Transfer Mode, a network technology based on transferring data in cells or packets of a fixed size. + The cell size used with ATM is relatively small compared to units used with older technologies. - above + above - Do not use to refer to information mentioned previously. When documents are converted to online format, the information may no longer be "above." Use a cross-reference if the referenced material is sufficiently removed, or write "as mentioned previously" instead. + Do not use to refer to information mentioned previously. + When documents are converted to online format, the information may no longer be "above." + Use a cross-reference if the referenced material is sufficiently removed, or write "as mentioned previously" instead. @@ -105,10 +119,14 @@ acronyms - An acronym is a word formed from the initial letters of a name, such as ROM for Read Only Memory, or by combining initial letters or part of a series of words, such as LILO for LInux LOader. Note that an acronym is pronounced as a word. Compare this to an initialism, which is also formed in a similar fashion to an acronym, but in which each letter is pronounced separately. + An acronym is a word formed from the initial letters of a name, such as ROM for Read Only Memory, or by combining initial letters or part of a series of words, such as LILO for LInux LOader. + Note that an acronym is pronounced as a word. + Compare this to an initialism, which is also formed in a similar fashion to an acronym, but in which each letter is pronounced separately. - Spell out most acronyms and initialisms before using them in text, such as "The Embedded DevKit (EDK)..." Unless the acronym or initialism stands for a proper noun, use sentence case for the spelled out version - for example, "central processing unit (CPU)." Unless required for the audience or the topic, do not spell out well-known abbreviations, such as HTML. + Spell out most acronyms and initialisms before using them in text, such as "The Embedded DevKit (EDK)..." + Unless the acronym or initialism stands for a proper noun, use sentence case for the spelled out version - for example, "central processing unit (CPU)." + Unless required for the audience or the topic, do not spell out well-known abbreviations, such as HTML. To form the plural of an acronym, add a trailing, lowercase "s," or "es," for example, ROMs, PINs, BIOSes. @@ -117,41 +135,53 @@ - - alright, all right + + alternate - Avoid if at all possible. These terms carry a more familiar or colloquial tone than is expected in Red Hat documentation. Use more formal alternatives such as "correct" or "as expected," depending on context. + vb. "Alternate" as a verb means to change between two states or options. + + See also . + - - alternate + + + alternative - Do not use this to mean "an alternative to something." "Alternate" (vb.) means to change between two states or options. If you mean "another way of doing something," use "an alternative method is to..." + adj. Used to describe another way or method of doing something. + "Alternate" (vb.) means to change between two states or options. If you mean "another way of doing something," use "an alternative method is to..." + + See also . + - and/or + and/or - Avoid if possible. Try to rewrite to make the available options explicit and clear. Do not write this and/or that. Write this or that or both. + Avoid if possible. + Try to rewrite to make the available options explicit and clear. + Do not write this and/or that. + Write this or that or both. - - applications + + application - When used as a proper name, use the capitalization of the product, such as GNUPro, Source-Navigator, and Red Hat Enterprise Linux. When used as a command, use lowercase as appropriate, such as "To start GCC, type gcc." + When used as a proper name, use the capitalization of the product, such as GNUPro, Source-Navigator, and Red Hat Enterprise Linux. + When used as a command, use lowercase as appropriate, such as "To start GCC, type gcc." @@ -164,10 +194,13 @@ - Applixware + Applixware + Applix + ApplixWare - Correct. Do not use "Applix" or "ApplixWare." + Correct. + Do not use "Applix" or "ApplixWare." @@ -177,25 +210,33 @@ architect - Do not use as a verb. Even though it might make sense in the correct context, using it as a verb can be jargon or unclear for your audience. Use "design," "build," "create," or another descriptive verb instead. Before replacing the verb form of "architect" during the editing process, check with the writer to find out the intended meaning. For example, a sentence that mentions rearchitecting might require "refactoring" as a replacement rather than "rebuilding." + Do not use as a verb. + Even though it might make sense in the correct context, using it as a verb can be jargon or unclear for your audience. + Use "design," "build," "create," or another descriptive verb instead. + Before replacing the verb form of "architect" during the editing process, check with the writer to find out the intended meaning. + For example, a sentence that mentions rearchitecting might require "refactoring" as a replacement rather than "rebuilding." - as well as + as well as - Not interchangeable with "and." "As well as" used in a series places more emphasis on the items preceding it, whereas "and" places equal weight on all items in the series. For example, "We sell kitchen electronics and china, as well as some gourmet foods." But "We sell kitchen electronics, china, and silverware." + Not interchangeable with "and." + "As well as" used in a series places more emphasis on the items preceding it, whereas "and" places equal weight on all items in the series. + For example, "We sell kitchen electronics and china, as well as some gourmet foods." + But "We sell kitchen electronics, china, and silverware." - as-a-Service + as-a-Service - Be aware that there is a great deal of overlap in as-a-Service acronyms. To avoid confusion, always spell out the full term on first possible use. + Be aware that there is a great deal of overlap in as-a-Service acronyms. + To avoid confusion, always spell out the full term on first use. @@ -272,7 +313,9 @@ - Hyphenate when written out: Thing-as-a-Service. For two-word prefixes, do not include a hyphen between the first and second words: Mobile Backend-as-a-Service. Can be used as an adjective to describe multiple (e.g., when referring to an IaaS, PaaS, and SaaS, use as-a-Service offerings, as-a-Service products, or similar wording). + Hyphenate when written out: Thing-as-a-Service. + For two-word prefixes, do not include a hyphen between the first and second words: Mobile Backend-as-a-Service. + Can be used as an adjective to describe multiple (e.g., when referring to an IaaS, PaaS, and SaaS, use as-a-Service offerings, as-a-Service products, or similar wording). @@ -288,7 +331,7 @@ - + - autofs + autofs - Always lowercase. This refers to the kernel-based automount utility. No other forms are recognized. + Always lowercase. + This refers to the kernel-based automount utility. + No other forms are recognized. diff --git a/en-US/I.xml b/en-US/I.xml index d5c1977..84703f8 100644 --- a/en-US/I.xml +++ b/en-US/I.xml @@ -99,6 +99,35 @@ + + Intel 64 + + + Correct. Do not use "Hammer," "x86_64," "x86-64," "x64," "64-bit x86" or other variations as the name of this architecture. + + + The correct term for Intel's implementation of this architecture is "Intel® 64." + Until late 2006, Intel's official name for the architecture was "Intel EM64T" (for Extended Memory 64 Technology). + They have since changed the name to "Intel® 64" however, and Red Hat documentation should reflect this change. + When discussing the architecture generally, reference both AMD64 and Intel 64 implementations specifically. + + + See also . + + + + The AMD64 logo is trademarked; the term "AMD64" is not. + For more information about AMD trademarks, see the AMD Trademark Information page at . + + + For more information about Intel® trademarks, see and . + + + + + + + Intel® CoreTM diff --git a/en-US/P.xml b/en-US/P.xml index 71e6aaf..c110e46 100644 --- a/en-US/P.xml +++ b/en-US/P.xml @@ -111,6 +111,22 @@ + + p.m. + + + Correct. Use the lowercase form and include the periods, and use a preceding space. + + + See also . + + + See The IBM Style Guide for a full discussion of how to represent times. + + + + + pop-up