Merge pull request #99867 from ShaunaDiaz/OSDOCS-16338

OSDOCS-16338: fixes cluster mentions MicroShift

Author: ShaunaDiaz

_topic_maps/_topic_map_ms.yml

@@ -250,7 +250,7 @@ Topics:
     File: microshift-operators-olm
   - Name: Creating custom catalogs with oc-mirror
     File: microshift-operators-oc-mirror
-  - Name: Adding OLM-based Operators to a disconnected cluster
+  - Name: Adding OLM-based Operators to a disconnected node
     File: microshift-operators-oc-mirror-disconnected
 ---
 Name: Backup and restore
@@ -270,21 +270,21 @@ Topics:
   File: microshift-etcd
 - Name: The sos report tool
   File: microshift-sos-report
-- Name: Getting your cluster ID
-  File: microshift-getting-cluster-id
+- Name: Getting your node ID
+  File: microshift-getting-node-id
 - Name: Getting support
   File: microshift-getting-support
-- Name: Remote health monitoring with a connected cluster
-  File: microshift-remote-cluster-monitoring
+- Name: Remote health monitoring with a connected node
+  File: microshift-remote-node-monitoring
 ---
 Name: Troubleshooting
 Dir: microshift_troubleshooting
 Distros: microshift
 Topics:
 - Name: Check your version
   File: microshift-version
-- Name: Troubleshoot the cluster
-  File: microshift-troubleshoot-cluster
+- Name: Troubleshoot the node
+  File: microshift-troubleshoot-node
 - Name: Troubleshoot installation issues
   File: microshift-installing-troubleshooting
 - Name: Troubleshoot backup and restore

microshift_cli_ref/microshift-cli-using-oc.adoc

@@ -11,7 +11,7 @@ The optional {oc-first} tool provides a subset of `oc` commands for {microshift-
 include::modules/microshift-cli-oc-about.adoc[leveloffset=+1]
 
 [id="cli-using-cli_{context}"]
-== Using oc with a {microshift-short} cluster
+== Using oc with a {microshift-short} node
 
 Review the following sections to learn how to complete common tasks in {microshift-short} using the `oc` CLI.
 

microshift_cli_ref/microshift-usage-oc-kubectl.adoc

@@ -11,7 +11,7 @@ The Kubernetes command-line interface (CLI), `kubectl`, can be used to run comma
 [id="microshift-kubectl-binary_{context}"]
 == The kubectl CLI tool
 
-You can use the `kubectl` CLI tool to interact with Kubernetes primitives on your {microshift-short} cluster. You can also use existing `kubectl` workflows and scripts for users coming from another Kubernetes environment, or for those who prefer to use the `kubectl` CLI.
+You can use the `kubectl` CLI tool to interact with Kubernetes primitives on your {microshift-short} node. You can also use existing `kubectl` workflows and scripts for users coming from another Kubernetes environment, or for those who prefer to use the `kubectl` CLI.
 
 * The `kubectl` CLI tool is included in the archive when you download `oc`.
 

microshift_configuring/microshift-node-access-kubeconfig.adoc

@@ -6,7 +6,7 @@ include::_attributes/attributes-microshift.adoc[]
 
 toc::[]
 
-Learn about how `kubeconfig` files are used with {microshift-short} deployments. CLI tools use `kubeconfig` files to communicate with the API server of a cluster. These files provide cluster details, IP addresses, and other information needed for authentication.
+Learn about how `kubeconfig` files are used with {microshift-short} deployments. CLI tools use `kubeconfig` files to communicate with the API server of a node. These files provide node details, IP addresses, and other information needed for authentication.
 
 include::modules/microshift-kubeconfig-overview.adoc[leveloffset=+1]
 

microshift_configuring/microshift-using-config-yaml.adoc

@@ -20,7 +20,7 @@ include::modules/microshift-nw-advertise-address.adoc[leveloffset=+2]
 
 include::modules/microshift-config-nodeport-limits.adoc[leveloffset=+2]
 
-[id="additional-resources_microshift-using-config-yaml_{context}"]
+[id="additional-resources_microshift-using-config-yaml"]
 [role="_additional-resources"]
 == Additional resources
 

microshift_configuring/microshift_auth_security/microshift-tls-config.adoc

@@ -20,5 +20,5 @@ include::modules/microshift-tls-default-cipher-suites.adoc[leveloffset=+2]
 
 * xref:../../microshift_configuring/microshift-config-snippets.adoc#microshift-config-snippets[Using configuration snippets]
 * xref:../../microshift_running_apps/microshift-authentication.adoc#authentication-microshift[Pod security authentication and authorization with SCC]
-* xref:../../microshift_configuring/microshift-node-access-kubeconfig#microshift-node-access-kubeconfig[Cluster access with kubeconfig]
+* xref:../../microshift_configuring/microshift-node-access-kubeconfig#microshift-node-access-kubeconfig[Node access with kubeconfig]
 * xref:../microshift_auth_security/microshift-custom-ca.adoc#microshift-custom-ca[Configuring custom certificate authorities]

microshift_install_get_ready/microshift-deploy-with-mirror-registry.adoc

@@ -6,7 +6,7 @@ include::_attributes/attributes-microshift.adoc[]
 
 toc::[]
 
-You can use a custom container registry when you deploy {microshift-short} in a disconnected network. Running your cluster in a restricted network without direct internet connectivity is possible by installing the cluster from a mirrored set of container images in a private registry.
+You can use a custom container registry when you deploy {microshift-short} in a disconnected network. Running your node in a restricted network without direct internet connectivity is possible by installing the node from a mirrored set of container images in a private registry.
 
 include::modules/microshift-mirror-container-images.adoc[leveloffset=+1]
 

microshift_install_rpm_opt/microshift-install-optional-rpms.adoc

@@ -6,7 +6,7 @@ include::_attributes/attributes-microshift.adoc[]
 
 toc::[]
 
-You can install optional RPM packages with {microshift-short} to provide additional cluster and application services.
+You can install optional RPM packages with {microshift-short} to provide additional node and application services.
 
 [id="microshift-install-rpm-add-ons"]
 == Installing optional packages

microshift_install_rpm_ostree/microshift-embed-in-rpm-ostree-offline-use.adoc

@@ -6,7 +6,7 @@ include::_attributes/attributes-microshift.adoc[]
 
 toc::[]
 
-Embedding {microshift-short} containers in an `rpm-ostree` commit means that you can run a cluster in air-gapped, disconnected, or offline environments. You can embed {product-title} containers in a {op-system-ostree-first} image so that container engines do not need to pull images over a network from a container registry. Workloads can start immediately without network connectivity.
+Embedding {microshift-short} containers in an `rpm-ostree` commit means that you can run a node in air-gapped, disconnected, or offline environments. You can embed {product-title} containers in a {op-system-ostree-first} image so that container engines do not need to pull images over a network from a container registry. Workloads can start immediately without network connectivity.
 
 include::modules/microshift-embed-microshift-image-offline-deploy.adoc[leveloffset=+1]
 

microshift_networking/microshift-cni.adoc

@@ -6,7 +6,7 @@ include::_attributes/attributes-microshift.adoc[]
 
 toc::[]
 
-The OVN-Kubernetes Container Network Interface (CNI) plugin is the default networking solution for the {microshift-short} node. OVN-Kubernetes is a virtualized network for pods and services that is based on Open Virtual Network (OVN).
+The OVN-Kubernetes Container Network Interface (CNI) plugin is the default networking solution for a {microshift-short} node. OVN-Kubernetes is a virtualized network for pods and services that is based on Open Virtual Network (OVN).
 
 * Default network configuration and connections are applied automatically in {microshift-short} with the `microshift-networking` RPM during installation.
 * A node that uses the OVN-Kubernetes network plugin also runs Open vSwitch (OVS) on the node.