Merge pull request #27633 from codyhoag/installer-terminology

Applying new style guidelines for Install docs

Author: codyhoag

installing/install_config/customizations.adoc

@@ -37,63 +37,63 @@ to @api-approvers (github) or #forum-api-review (slack).
 |Resource name
 |Description
 
-|apiserver.config.openshift.io
-|Provides api-server configuration such as xref:../../security/certificates/api-server.adoc#api-server-certificates[certificates and certificate authorities].
+|`apiserver.config.openshift.io`
+|Provides API server configuration such as xref:../../security/certificates/api-server.adoc#api-server-certificates[certificates and certificate authorities].
 
-|authentication.config.openshift.io
-|Controls the xref:../../authentication/understanding-identity-provider.adoc#understanding-identity-provider[identity provider]and authentication configuration for the cluster.
+|`authentication.config.openshift.io`
+|Controls the xref:../../authentication/understanding-identity-provider.adoc#understanding-identity-provider[identity provider] and authentication configuration for the cluster.
 
-|build.config.openshift.io
+|`build.config.openshift.io`
 |Controls default and enforced xref:../../builds/build-configuration.adoc#build-configuration[configuration] for all builds on the cluster.
 
-|console.config.openshift.io
+|`console.config.openshift.io`
 |Configures the behavior of the web console interface, including the xref:../../web_console/configuring-web-console.adoc#configuring-web-console[logout behavior].
 
-|featuregate.config.openshift.io
+|`featuregate.config.openshift.io`
 |Enables xref:../../nodes/clusters/nodes-cluster-enabling-features.adoc#nodes-cluster-enabling[FeatureGates]
 so that you can use Tech Preview features.
 
-|image.config.openshift.io
+|`image.config.openshift.io`
 |Configures how specific xref:../../openshift_images/image-configuration.adoc#image-configuration[image registries] should be treated (allowed, disallowed, insecure, CA details).
 
-|ingress.config.openshift.io
+|`ingress.config.openshift.io`
 |Configuration details related to xref:../../networking/ingress-operator.adoc#nw-installation-ingress-config-asset_configuring-ingress[routing] such as the default domain for routes.
 
-|oauth.config.openshift.io
+|`oauth.config.openshift.io`
 |Configures identity providers and other behavior related to xref:../../authentication/configuring-internal-oauth.adoc#configuring-internal-oauth[internal OAuth server] flows.
 
-|project.config.openshift.io
+|`project.config.openshift.io`
 |Configures xref:../../applications/projects/configuring-project-creation.adoc#configuring-project-creation[how projects are created] including the project template.
 
-|proxy.config.openshift.io
+|`proxy.config.openshift.io`
 |Defines proxies to be used by components needing external network access.  Note: not all components currently consume this value.
 
-|scheduler.config.openshift.io
-|Configures xref:../../nodes/scheduling/nodes-scheduler-default.adoc#nodes-scheduler-default[scheduler] behavior such as policies and default nodeselectors.
+|`scheduler.config.openshift.io`
+|Configures xref:../../nodes/scheduling/nodes-scheduler-default.adoc#nodes-scheduler-default[scheduler] behavior such as policies and default node selectors.
 
 |===
 
 [id="operator-configuration-resources_{context}"]
 == Operator configuration resources
 
 These configuration resources are cluster-scoped instances, named `cluster`, which control the behavior of a specific component as
-owned by a particular operator.
+owned by a particular Operator.
 
 [cols="2a,8a",options="header"]
 |===
 |Resource name
 |Description
 
-|console.operator.openshift.io
+|`console.operator.openshift.io`
 |Controls console appearance such as branding customizations
 
-|config.imageregistry.operator.openshift.io
+|`config.imageregistry.operator.openshift.io`
 |Configures xref:../../registry/configuring-registry-operator.adoc#registry-operator-configuration-resource-overview_configuring-registry-operator[internal image registry settings] such as public routing, log levels, proxy settings, resource constraints, replica counts, and storage type.
 
-|config.samples.operator.openshift.io
+|`config.samples.operator.openshift.io`
 |Configures the
 xref:../../openshift_images/configuring-samples-operator.adoc#configuring-samples-operator[Samples Operator]
-to control which example imagestreams and templates are installed on the cluster.
+to control which example image streams and templates are installed on the cluster.
 
 |===
 
@@ -113,14 +113,14 @@ documentation for details on how and when you can create additional resource ins
 |Namespace
 |Description
 
-|alertmanager.monitoring.coreos.com
-|main
-|openshift-monitoring
+|`alertmanager.monitoring.coreos.com`
+|`main`
+|`openshift-monitoring`
 |Controls the xref:../../monitoring/managing-alerts.adoc#managing-alerts[Alertmanager] deployment parameters.
 
-|ingresscontroller.operator.openshift.io
-|default
-|openshift-ingress-operator
+|`ingresscontroller.operator.openshift.io`
+|`default`
+|`openshift-ingress-operator`
 |Configures xref:../../networking/ingress-operator.adoc#configuring-ingress[Ingress Operator] behavior such as domain, number of replicas, certificates, and controller placement.
 
 |===
@@ -135,23 +135,23 @@ You use these resources to retrieve information about the cluster. Do not edit t
 |===
 |Resource name|Instance name|Description
 
-|clusterversion.config.openshift.io
-|version
-|In {product-title} {product-version}, you must not customize the ClusterVersion
+|`clusterversion.config.openshift.io`
+|`version`
+|In {product-title} {product-version}, you must not customize the `ClusterVersion`
 resource for production clusters. Instead, follow the process to
 xref:../../updating/updating-cluster.adoc#updating-cluster[update a cluster].
 
-|dns.config.openshift.io
-|cluster
+|`dns.config.openshift.io`
+|`cluster`
 |You cannot modify the DNS settings for your cluster. You can
 xref:../../networking/dns-operator.adoc#dns-operator[view the DNS Operator status].
 
-|infrastructure.config.openshift.io
-|cluster
+|`infrastructure.config.openshift.io`
+|`cluster`
 |Configuration details allowing the cluster to interact with its cloud provider.
 
-|network.config.openshift.io
-|cluster
+|`network.config.openshift.io`
+|`cluster`
 |You cannot modify your cluster networking after installation. To customize your network, follow the process to
 xref:../../installing/installing_aws/installing-aws-network-customizations.adoc#installing-aws-network-customizations[customize networking during installation].
 

installing/install_config/installing-customizing.adoc

@@ -10,10 +10,10 @@ there are times when it is necessary to implement a
 required low-level security, networking, or performance feature.
 Direct changes to {product-title} nodes can be done by:
 
-* Creating MachineConfigs that are included in manifest files
+* Creating machine configs that are included in manifest files
 to start up a cluster during `openshift-install`.
 
-* Creating MachineConfigs that are passed to running
+* Creating machine configs that are passed to running
 {product-title} nodes via the Machine Config Operator.
 
 The following sections describe features that you might want to

installing/install_config/installing-restricted-networks-preparations.adoc

@@ -11,7 +11,7 @@ Before you install a cluster on infrastructure that you provision in a restricte
 ====
 You must have access to the internet to obtain the necessary container images.
 In this procedure, you place the mirror registry on a mirror host
-that has access to both your network and the internet. If you do not have access
+that has access to both your network and the Internet. If you do not have access
 to a mirror host, use the disconnected procedure to copy images to a device you
 can move across network boundaries with.
 ====

installing/installing-fips.adoc

@@ -7,16 +7,16 @@ toc::[]
 
 Starting with version 4.3, you can install an {product-title} cluster that uses FIPS Validated / Modules in Process cryptographic libraries.
 
-For the {op-system-first} machines in your cluster, this change is applied when the machines are deployed based on the status of an option in the `install-config.yaml` file, which governs the cluster options that a user can change during cluster deployment. With Red Hat Enterprise Linux machines, you must enable FIPS mode when you install the operating system on the machines that you plan to use as worker machines. These configuration methods ensure that your cluster meet the requirements of a FIPS compliance audit: only FIPS Validated / Modules in Process cryptography packages are enabled before the initial system boot.
+For the {op-system-first} machines in your cluster, this change is applied when the machines are deployed based on the status of an option in the `install-config.yaml` file, which governs the cluster options that a user can change during cluster deployment. With {op-system-base-full} machines, you must enable FIPS mode when you install the operating system on the machines that you plan to use as worker machines. These configuration methods ensure that your cluster meet the requirements of a FIPS compliance audit: only FIPS Validated / Modules in Process cryptography packages are enabled before the initial system boot.
 
 Because FIPS must be enabled before the operating system that your cluster uses boots for the first time, you cannot enable FIPS after you deploy a cluster.
 
 [id="installation-about-fips-validation_{context}"]
 == FIPS validation in {product-title}
 
-{product-title} uses certain FIPS Validated / Modules in Process modules within Red Hat Enterprise Linux (RHEL) and {op-system} for the operating system components that it uses. See link:https://access.redhat.com/articles/3359851[RHEL7 core crypto components]. For example, when users SSH into {product-title} clusters and containers, those connections are properly encrypted.
+{product-title} uses certain FIPS Validated / Modules in Process modules within {op-system-base} and {op-system} for the operating system components that it uses. See link:https://access.redhat.com/articles/3359851[RHEL7 core crypto components]. For example, when users SSH into {product-title} clusters and containers, those connections are properly encrypted.
 
-{product-title} components are written in Go and built with Red Hat’s golang compiler. When you enable FIPS mode for your cluster, all {product-title} components that require cryptographic signing call RHEL and {op-system} cryptographic libraries.
+{product-title} components are written in Go and built with Red Hat's golang compiler. When you enable FIPS mode for your cluster, all {product-title} components that require cryptographic signing call {op-system-base} and {op-system} cryptographic libraries.
 
 .FIPS mode attributes and limitations in {product-title} {product-version}
 [cols="8a,8a",options="header"]
@@ -25,13 +25,13 @@ Because FIPS must be enabled before the operating system that your cluster uses
 |Attributes
 |Limitations
 
-|FIPS support in RHEL 7 operating systems.
+|FIPS support in {op-system-base} 7 operating systems.
 .3+|The FIPS implementation does not offer a single function that both computes hash functions and validates the keys that are based on that hash. This limitation will continue to be evaluated and improved in future {product-title} releases.
 
 |FIPS support in CRI-O runtimes.
 |FIPS support in {product-title} services.
 
-|FIPS Validated / Modules in Process cryptographic module and algorithms that are obtained from RHEL 7 and {op-system} binaries and images.
+|FIPS Validated / Modules in Process cryptographic module and algorithms that are obtained from {op-system-base} 7 and {op-system} binaries and images.
 |
 
 |Use of FIPS compatible golang compiler.
@@ -52,14 +52,14 @@ To ensure that the secrets that are stored in etcd use FIPS Validated / Modules
 [id="installation-about-fips-components-storage_{context}"]
 === Storage
 
-For local storage, use RHEL-provided disk encryption or Container Native Storage that uses RHEL-provided disk encryption. By storing all data in volumes that use RHEL-provided disk encryption and enabling FIPS mode for your cluster, both data at rest and data in motion, or network data, are protected by FIPS Validated / Modules in Process encryption.
+For local storage, use {op-system-base}-provided disk encryption or Container Native Storage that uses {op-system-base}-provided disk encryption. By storing all data in volumes that use {op-system-base}-provided disk encryption and enabling FIPS mode for your cluster, both data at rest and data in motion, or network data, are protected by FIPS Validated / Modules in Process encryption.
 You can configure your cluster to encrypt the root filesystem of each node, as described
 in xref:../installing/install_config/installing-customizing.adoc#installing-customizing[Customizing nodes].
 
 [id="installation-about-fips-components-runtimes_{context}"]
 === Runtimes
 
-To ensure that containers know that they are running on a host that is using FIPS Validated / Modules in Process cryptography modules, use CRI-O to manage your runtimes. CRI-O supports FIPS-Mode, in that it configures the containers to know that they are running in FIPS mode.
+To ensure that containers know that they are running on a host that is using FIPS Validated / Modules in Process cryptography modules, use CRI-O to manage your runtimes. CRI-O supports FIPS mode, in that it configures the containers to know that they are running in FIPS mode.
 
 [id="installing-fips-mode_{context}"]
 ==  Installing a cluster in FIPS mode
@@ -75,4 +75,4 @@ To install a cluster in FIPS mode, follow the instructions to install a customiz
 
 To apply `AES CBC` encryption to your etcd data store, follow the xref:../security/encrypting-etcd.adoc#encrypting-etcd[Encrypting etcd data] process after you install your cluster.
 
-If you add RHEL nodes to your cluster, ensure that you enable FIPS mode on the machines before their initial boot. See xref:../machine_management/user_infra/adding-rhel-compute.adoc#adding-rhel-compute[Adding RHEL compute machines to an {product-title} cluster] and link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/security_guide/chap-federal_standards_and_regulations#sec-Enabling-FIPS-Mode[Enabling FIPS Mode] in the RHEL 7 documentation.
+If you add {op-system-base} nodes to your cluster, ensure that you enable FIPS mode on the machines before their initial boot. See xref:../machine_management/user_infra/adding-rhel-compute.adoc#adding-rhel-compute[Adding RHEL compute machines to an {product-title} cluster] and link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/security_guide/chap-federal_standards_and_regulations#sec-Enabling-FIPS-Mode[Enabling FIPS Mode] in the {op-system-base} 7 documentation.

installing/installing_aws/installing-aws-network-customizations.adoc

@@ -66,7 +66,7 @@ include::modules/nw-modifying-operator-install-config.adoc[leveloffset=+1]
 
 [NOTE]
 ====
-For more information on using a Network Load Balancer(NLB) on AWS, see xref:../../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws-network-load-balancer.adoc#configuring-ingress-cluster-traffic-aws-network-load-balancer[Configuring Ingress cluster traffic on AWS using a Network Load Balancer].
+For more information on using a Network Load Balancer (NLB) on AWS, see xref:../../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws-network-load-balancer.adoc#configuring-ingress-cluster-traffic-aws-network-load-balancer[Configuring Ingress cluster traffic on AWS using a Network Load Balancer].
 ====
 
 include::modules/nw-aws-nlb-new-cluster.adoc[leveloffset=+1]

installing/installing_aws/installing-restricted-networks-aws.adoc

@@ -12,7 +12,7 @@ an internal mirror of the installation release content.
 [IMPORTANT]
 ====
 While you can install an {product-title} cluster by using mirrored installation
-release content, your cluster still requires internet access to use the AWS APIs.
+release content, your cluster still requires Internet access to use the AWS APIs.
 ====
 
 One way to create this infrastructure is to use the provided

installing/installing_bare_metal_ipi/ipi-install-prerequisites.adoc

@@ -8,8 +8,8 @@ toc::[]
 
 Installer-provisioned installation of {product-title} requires:
 
-. One provisioner node with RHEL 8.1 installed.
-. Three Control Plane nodes.
+. One provisioner node with {op-system-base-full} 8.1 installed.
+. Three control plane nodes.
 . Baseboard Management Controller (BMC) access to each node.
 ifeval::[{release} > 4.5]
 . At least one network:

installing/installing_bare_metal_ipi/ipi-install-troubleshooting.adoc

@@ -5,7 +5,6 @@ include::modules/common-attributes.adoc[]
 
 toc::[]
 
-
 == Troubleshooting the installer workflow
 
 Prior to troubleshooting the installation environment, it is critical to understand the overall flow of the installer-provisioned installation on bare metal. The diagrams below provide a troubleshooting flow with a step-by-step breakdown for the environment.

installing/installing_ibm_power/installing-ibm-power.adoc

@@ -20,7 +20,7 @@ link:https://access.redhat.com/articles/4207611[guidelines for deploying {produc
 * Provision
 xref:../../storage/persistent_storage/persistent-storage-nfs.adoc#persistent-storage-nfs[persistent storage using NFS]
 for your cluster. To deploy a private image registry, your storage must provide
-ReadWriteMany access modes.
+`ReadWriteMany` access modes.
 * Review details about the
 xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
 processes.

installing/installing_ibm_power/installing-restricted-networks-ibm-power.adoc

@@ -26,7 +26,7 @@ Ensure that installation steps are performed on a machine with access to the ins
 * Provision
 xref:../../storage/understanding-persistent-storage.adoc#understanding-persistent-storage[persistent storage]
 for your cluster. To deploy a private image registry, your storage must provide
-ReadWriteMany access modes.
+`ReadWriteMany` access modes.
 * Review details about the
 xref:../../architecture/architecture-installation.adoc#architecture-installation[{product-title} installation and update]
 processes.