From de66f43e82bb12245a9668a1c77ba79c1f714247 Mon Sep 17 00:00:00 2001 From: Julian Cable Date: Thu, 23 Nov 2023 18:13:24 +0000 Subject: [PATCH 1/2] Add 64-bit architecture guidance --- en-US/0-9.xml | 71 ++++++++++++++++++++++++++++++ en-US/A.xml | 116 +++++++++++++++++++++++++++++++++++++++++++++++--- en-US/I.xml | 31 +++++++++++--- en-US/XYZ.xml | 35 +++++++++++++++ 4 files changed, 239 insertions(+), 14 deletions(-) diff --git a/en-US/0-9.xml b/en-US/0-9.xml index 76d5120..0138f97 100644 --- a/en-US/0-9.xml +++ b/en-US/0-9.xml @@ -38,6 +38,77 @@ + + 64-bit ARM + + + n. A 64-bit version of the ARM architecture. + This term can refer to both AArch66/aarch64 and to ARM64/arm64. + + + Use this format in general cases when writing for both names of the architecture and various cloud providers. + + + Cloud providers can use different formats of this term when using architectures. + If you are documenting code, commands, or outputs, confer with your subject-matter expert on the correct format for the specific use case. + + + Examples: + + + + + The customer is using Amazon Web Services (AWS) on 64-bit ARM systems. + + + + + The customer is using multiple machine types for Microsoft Azure on 64-bit ARM infrastructures. + + + + + Refer also to , , , , , and . + + + + + + + 64-bit x86 + + + n. A 64-bit version of the x86 architecture. + This term is a synonym of x86_64. + Use this format in general cases when writing for names of the architectures for various cloud providers. + + + Cloud providers can use different formats of this term when using architectures. + If you are documenting code, commands or outputs, confer with your subject-matter expert on the correct format for the specific use case. + + + Examples: + + + + + Amazon Web Services (AWS) on 64-bit x86 systems + + + + + Machine types for Microsoft Azure on 64-bit x86 infrastructures + + + + + Refer also to , , , , , and . + + + + + + diff --git a/en-US/A.xml b/en-US/A.xml index af66767..e08d542 100644 --- a/en-US/A.xml +++ b/en-US/A.xml @@ -102,21 +102,84 @@ + + + AArch64, aarch64 + + + n. A 64-bit version of the ARM architecture. + Use this term when referring to operating systems and server instances, for example Red Hat Enterprise Linux, Fedora, CoreOS, and other Linux distributions. + + + Use the uppercase (AArch64) format in general cases when referring to system architecture. + Use the lowercase (aarch64) format only when referring to objects or parameters. + It can be styled as code (monospace font or a code-styled block) when referring to code. + + + Cloud providers can use different formats of this term when using architectures. + If you are documenting code, commands, or outputs, confer with your subject-matter expert on the correct format for the specific use case. + + + Examples: + + + + + When running Red Hat Enterprise Linux with an AArch64 system, run the following commands: + + + + + Specify the system architecture of your cluster, such as x86_64 or aarch64. + + + + + Refer also to , , , , , and . + + + + - AMD64 + AMD64, amd64 - Correct. Do not use "Hammer", "x86_64", "x86-64", "x64", "64-bit x86" or other variations as the name of this architecture. + n. The AMD 64-bit version of the x86 architecture. + Use this term for Red Hat OpenShift Container Platform attributes, Kubernetes, operators, application programming interfaces (APIs), or command-line interface (CLI) objects. - 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. + Use the uppercase format (AMD64) in general sentences when referring to Red Hat OpenShift Container Platform features. + Use the lowercase format (amd64) only when referring to objects or parameters. + It can be styled as code (monospace font or a code-styled block) when referring to code. + + + Cloud providers can use different formats of this term when using architectures. + If you are documenting code, commands, or outputs, confer with your subject-matter expert on the correct format for the specific use case. + + + Examples: + + + + This operator is supported on AMD64 and ARM64 platforms. + + + + + In this scenario, amd64 is a valid value for X. + + + + - Refer also to . + Refer also to , , , , , and . - + + + + + + + ARM64, arm64 + + + n. A 64-bit version of the ARM architecture. + Use this term for Red Hat OpenShift Container Platform attributes, Kubernetes, operators, application programming interfaces (APIs), and command-line interface (CLI) objects. + + + Use the uppercase format (ARM64) in general sentences when referring to Red Hat OpenShift Container Platform features. + Use lowercase format (arm64) only when referring to objects or parameters. + It can be styled as code (monospace font or a code-styled block) when referring to code. + + + Cloud providers can use different formats of this term when using architectures. + If you are documenting code, commands, or outputs, confer with your subject-matter expert on the correct format for the specific use case. + + + Examples: + + + + + In this exercise, you create an ARM64 compute machine set. + + + + + In this scenario, arm64 is a valid value for X. + + + + + Refer also to , , , , , and . + + and/or diff --git a/en-US/I.xml b/en-US/I.xml index 8765b10..915626a 100644 --- a/en-US/I.xml +++ b/en-US/I.xml @@ -134,24 +134,41 @@ Intel 64 - Correct. + n. The Intel 64-bit version of the x86 architecture. + Use this format when referring to information that is exclusive to Intel processors. + For Red Hat products, it applies only to Red Hat Enterprise Linux content. + + + Cloud providers can use different formats of this term when using architectures. + If you are documenting code, commands, or outputs, confer with your subject-matter expert on the correct format for the specific use case. + + + Example: + + + + + This feature can run on only Intel 64 processors. + + + + - Refer also to . + Refer also to , , , , , and . - + + --> - For more information about Intel® trademarks, refer to and . + For more information about Intel trademarks, refer to and . diff --git a/en-US/XYZ.xml b/en-US/XYZ.xml index 5ffef67..670be20 100644 --- a/en-US/XYZ.xml +++ b/en-US/XYZ.xml @@ -16,6 +16,41 @@ + + x86_64 + + + n. A 64-bit version of the x86 architecture. + Use this term when referring to operating systems and server instances, for example Red Hat Enterprise Linux, Fedora, CoreOS and other Linux distributions. + Use this format without backticks in general cases when referring to system architecture. + Use this format in backticks when referring to architecture as a value or parameter. + + + Cloud providers can use different formats of this term when using architectures. + If you are documenting code, commands or outputs, confer with your subject-matter expert on the correct format for the specific use case. + + + Examples: + + + + + Specifies the type of architecture for your server, such as x86_64. + + + + + When specifying the architecture, x86_64 is a valid value. + + + + + Refer also to , , , , , and . + + + + + XEmacs From 5179d3cdf17b1bb2e40a02629b32a6d3222b0a4d Mon Sep 17 00:00:00 2001 From: Julian Cable Date: Mon, 27 Nov 2023 17:47:14 +0000 Subject: [PATCH 2/2] Implementing edits from review --- en-US/0-9.xml | 18 +++++++++--------- en-US/A.xml | 12 ++++++------ en-US/I.xml | 6 +++--- en-US/XYZ.xml | 4 ++-- 4 files changed, 20 insertions(+), 20 deletions(-) diff --git a/en-US/0-9.xml b/en-US/0-9.xml index 0138f97..e2d62cb 100644 --- a/en-US/0-9.xml +++ b/en-US/0-9.xml @@ -43,14 +43,14 @@ n. A 64-bit version of the ARM architecture. - This term can refer to both AArch66/aarch64 and to ARM64/arm64. + This term can refer to both AArch66/`aarch64` and to ARM64/`arm64`. - Use this format in general cases when writing for both names of the architecture and various cloud providers. + Use this format in general cases to refer to names of the architecture for various cloud providers. - Cloud providers can use different formats of this term when using architectures. - If you are documenting code, commands, or outputs, confer with your subject-matter expert on the correct format for the specific use case. + Cloud providers might use different formats of this term to refer to architectures. + If you are documenting code, commands, or outputs, then confer with your subject-matter expert on the correct format for the specific use case. Examples: @@ -58,12 +58,12 @@ - The customer is using Amazon Web Services (AWS) on 64-bit ARM systems. + Amazon Web Services (AWS) on 64-bit ARM systems - The customer is using multiple machine types for Microsoft Azure on 64-bit ARM infrastructures. + Machine types for Microsoft Azure on 64-bit ARM infrastructures @@ -80,11 +80,11 @@ n. A 64-bit version of the x86 architecture. This term is a synonym of x86_64. - Use this format in general cases when writing for names of the architectures for various cloud providers. + Use this format in general cases to refer to names of the architecture for various cloud providers. - Cloud providers can use different formats of this term when using architectures. - If you are documenting code, commands or outputs, confer with your subject-matter expert on the correct format for the specific use case. + Cloud providers might use different formats of this term to refer to architectures. + If you are documenting code, commands or outputs, then confer with your subject-matter expert on the correct format for the specific use case. Examples: diff --git a/en-US/A.xml b/en-US/A.xml index e08d542..72791ed 100644 --- a/en-US/A.xml +++ b/en-US/A.xml @@ -116,8 +116,8 @@ It can be styled as code (monospace font or a code-styled block) when referring to code. - Cloud providers can use different formats of this term when using architectures. - If you are documenting code, commands, or outputs, confer with your subject-matter expert on the correct format for the specific use case. + Cloud providers might use different formats of this term to refer to architectures. + If you are documenting code, commands, or outputs, then confer with your subject-matter expert on the correct format for the specific use case. Examples: @@ -154,8 +154,8 @@ It can be styled as code (monospace font or a code-styled block) when referring to code. - Cloud providers can use different formats of this term when using architectures. - If you are documenting code, commands, or outputs, confer with your subject-matter expert on the correct format for the specific use case. + Cloud providers might use different formats of this term to refer to architectures. + If you are documenting code, commands, or outputs, then confer with your subject-matter expert on the correct format for the specific use case. Examples: @@ -205,8 +205,8 @@ It can be styled as code (monospace font or a code-styled block) when referring to code. - Cloud providers can use different formats of this term when using architectures. - If you are documenting code, commands, or outputs, confer with your subject-matter expert on the correct format for the specific use case. + Cloud providers might use different formats of this term to refer to architectures. + If you are documenting code, commands, or outputs, then confer with your subject-matter expert on the correct format for the specific use case. Examples: diff --git a/en-US/I.xml b/en-US/I.xml index 915626a..9b603c5 100644 --- a/en-US/I.xml +++ b/en-US/I.xml @@ -136,11 +136,11 @@ n. The Intel 64-bit version of the x86 architecture. Use this format when referring to information that is exclusive to Intel processors. - For Red Hat products, it applies only to Red Hat Enterprise Linux content. + For Red Hat products, use only for Red Hat Enterprise Linux content. - Cloud providers can use different formats of this term when using architectures. - If you are documenting code, commands, or outputs, confer with your subject-matter expert on the correct format for the specific use case. + Cloud providers might use different formats of this term to refer to architectures. + If you are documenting code, commands, or outputs, then confer with your subject-matter expert on the correct format for the specific use case. Example: diff --git a/en-US/XYZ.xml b/en-US/XYZ.xml index 670be20..1d0bf21 100644 --- a/en-US/XYZ.xml +++ b/en-US/XYZ.xml @@ -26,8 +26,8 @@ Use this format in backticks when referring to architecture as a value or parameter. - Cloud providers can use different formats of this term when using architectures. - If you are documenting code, commands or outputs, confer with your subject-matter expert on the correct format for the specific use case. + Cloud providers might use different formats of this term to refer to architectures. + If you are documenting code, commands or outputs, then confer with your subject-matter expert on the correct format for the specific use case. Examples: