diff --git a/en-US/B.xml b/en-US/B.xml index 63b1d4b..081e4ab 100644 --- a/en-US/B.xml +++ b/en-US/B.xml @@ -423,7 +423,7 @@ button - Describe a GUI button as a "button," not a "pushbutton" or "push-button." + Describe a UI button as a "button," not a "pushbutton" or "push-button." Ordinarily you would not include the text "button" in a procedure or description. For example, "Click OK to continue" is perfectly acceptable. It might be necessary to distinguish between buttons and links; for example, "Click the Download link." diff --git a/en-US/C.xml b/en-US/C.xml index 2e349e4..98baf4a 100644 --- a/en-US/C.xml +++ b/en-US/C.xml @@ -149,7 +149,7 @@ click - v. Use when referring to a GUI control button, for example, "Click OK." Do not use "click on". + v. Use when referring to a UI control button, for example, "Click OK." Do not use "click on". diff --git a/en-US/Design.xml b/en-US/Design.xml index f630660..9db34dc 100644 --- a/en-US/Design.xml +++ b/en-US/Design.xml @@ -83,15 +83,15 @@ The following sections highlight exceptions or cases that might otherwise cause confusion.
- GUI Elements, Punctuation, and Symbols + User Interface (UI) Elements, Punctuation, and Symbols - When describing GUI elements, do not include punctuation that appears on those elements, unless omission of that punctuation might lead to confusion. + When describing UI elements, do not include punctuation that appears on those elements, unless omission of that punctuation might lead to confusion. For example, for a button labeled Save As..., do not include the ellipsis in the documentation. - In most cases, do not include the object type in instructions. + In most cases, do not include the element type in instructions. For example, rather than "Click the Save button," write "Click Save." @@ -123,9 +123,9 @@ See the UI elements chapter in the IBM Style Guide for more information.
- Navigating Through Multiple GUI Options + Navigating Through Multiple UI Options - Use "Navigate to" when moving through multiple GUI options because it covers all cases where you might have to click, point to, press, select, or otherwise make a series of selections to initiate an action. + Use "Navigate to" when moving through multiple UI options because it covers all cases where you might have to click, point to, press, select, or otherwise make a series of selections to initiate an action. For example, "From the OpenShift web console, navigate to Monitoring → Alerting." diff --git a/en-US/E.xml b/en-US/E.xml index 01cafdf..fa64967 100644 --- a/en-US/E.xml +++ b/en-US/E.xml @@ -100,7 +100,7 @@ n. Initialism for "end of line" - Always use uppercase for the initialism. Do not capitalize the expansion except at the beginning of a sentence. When documenting GUI objects, use the same capitalization as shown in the GUI. + Always use uppercase for the initialism. Do not capitalize the expansion except at the beginning of a sentence. When documenting UI objects, use the same capitalization as shown in the UI. diff --git a/en-US/Language.xml b/en-US/Language.xml index d06ea00..31bb084 100644 --- a/en-US/Language.xml +++ b/en-US/Language.xml @@ -1189,7 +1189,7 @@ Numbers (move from N entry) --> Sometimes multiple terms have a single meaning. If terms are used inconsistently, users (and translators) will assume they refer to different things. It is best to use a single term for a single concept throughout. - For example, "Administration GUI" and "Administration Console" could both be used to refer to a single application or to different applications. For this reason it is important that writers choose the most suitable term for each situation and use it consistently. + For example, "Administration UI" and "Administration Console" could both be used to refer to a single application or to different applications. For this reason it is important that writers choose the most suitable term for each situation and use it consistently. diff --git a/en-US/N.xml b/en-US/N.xml index 4ec6a2e..c5cee83 100644 --- a/en-US/N.xml +++ b/en-US/N.xml @@ -10,7 +10,7 @@ navigate to - Use "Navigate to" when moving through multiple GUI options, because it covers all cases where you might have to click, point to, select, or otherwise make a series of selections to initiate an action. For example, "From the OpenShift web console, navigate to Monitoring → Alerting." + Use "Navigate to" when moving through multiple UI options, because it covers all cases where you might have to click, point to, select, or otherwise make a series of selections to initiate an action. For example, "From the OpenShift web console, navigate to Monitoring → Alerting." Do not use "Go to", or "point to", or other variations. diff --git a/en-US/T.xml b/en-US/T.xml index f255be0..159c5f3 100644 --- a/en-US/T.xml +++ b/en-US/T.xml @@ -228,7 +228,7 @@ Initialism for "time to live" (n.) and "time-to-live" (adj.) - Neither the noun nor the adjective should be capitalized unless you are documenting a GUI field, label, or similar element, in which case you should use the same capitalization. Capitalization at the beginning of a sentence is acceptable. The initialism is always uppercase. + Neither the noun nor the adjective should be capitalized unless you are documenting a UI field, label, or similar element, in which case you should use the same capitalization. Capitalization at the beginning of a sentence is acceptable. The initialism is always uppercase.