Remove telco ref from files and file names

Author: amolnar-rh

edge_computing/day_2_core_cnf_clusters/troubleshooting/telco-troubleshooting-bmn-maintenance.adoc renamed to edge_computing/day_2_core_cnf_clusters/troubleshooting/troubleshooting-bmn-maintenance.adoc

@@ -1,29 +1,29 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="telco-troubleshooting-bmn-maintenance"]
+[id="troubleshooting-bmn-maintenance"]
 = Bare-metal node maintenance
 include::_attributes/common-attributes.adoc[]
-:context: telco-troubleshooting-bmn-maintenance
+:context: troubleshooting-bmn-maintenance
 
 toc::[]
 
 You can connect to a node for general troubleshooting.
 However, in some cases, you need to perform troubleshooting or maintenance tasks on certain hardware components.
 This section discusses topics that you need to perform for hardware maintenance.
 
-include::modules/telco-troubleshooting-bmn-connect-to-node.adoc[leveloffset=+1]
-include::modules/telco-troubleshooting-bmn-move-apps-to-pods.adoc[leveloffset=+1]
+include::modules/troubleshooting-bmn-connect-to-node.adoc[leveloffset=+1]
+include::modules/troubleshooting-bmn-move-apps-to-pods.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../nodes/nodes/nodes-nodes-working.adoc#nodes-nodes-working_nodes-nodes-working[Working with nodes]
 
-include::modules/telco-troubleshooting-bmn-replace-dimm.adoc[leveloffset=+1]
+include::modules/troubleshooting-bmn-replace-dimm.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../storage/index.adoc#storage-overview_storage-overview[{product-title} storage overview]
 
-include::modules/telco-troubleshooting-bmn-replace-disk.adoc[leveloffset=+1]
-include::modules/telco-troubleshooting-bmn-replace-nw-card.adoc[leveloffset=+1]
+include::modules/troubleshooting-bmn-replace-disk.adoc[leveloffset=+1]
+include::modules/troubleshooting-bmn-replace-nw-card.adoc[leveloffset=+1]

edge_computing/day_2_core_cnf_clusters/troubleshooting/telco-troubleshooting-cert-maintenance.adoc renamed to edge_computing/day_2_core_cnf_clusters/troubleshooting/troubleshooting-cert-maintenance.adoc

@@ -1,8 +1,8 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="telco-troubleshooting-cert-maintenance"]
+[id="troubleshooting-cert-maintenance"]
 = Certificate maintenance
 include::_attributes/common-attributes.adoc[]
-:context: telco-troubleshooting-cert-maintenance
+:context: troubleshooting-cert-maintenance
 
 toc::[]
 
@@ -14,22 +14,22 @@ Learn about certificates in {product-title} and how to maintain them by using th
 * link:https://access.redhat.com/solutions/5018231[Which OpenShift certificates do rotate automatically and which do not in Openshift 4.x?]
 * link:https://access.redhat.com/solutions/7000968[Checking etcd certificate expiry in OpenShift 4]
 
-include::modules/telco-troubleshooting-certs-manual.adoc[leveloffset=+1]
-include::modules/telco-troubleshooting-certs-manual-proxy.adoc[leveloffset=+2]
+include::modules/troubleshooting-certs-manual.adoc[leveloffset=+1]
+include::modules/troubleshooting-certs-manual-proxy.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../security/certificate_types_descriptions/proxy-certificates.adoc#cert-types-proxy-certificates[Proxy certificates]
 
-include::modules/telco-troubleshooting-certs-manual-user-provisioned.adoc[leveloffset=+2]
+include::modules/troubleshooting-certs-manual-user-provisioned.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../security/certificate_types_descriptions/user-provided-certificates-for-api-server.adoc#cert-types-user-provided-certificates-for-the-api-server[User-provisioned certificates for the API server]
 
-include::modules/telco-troubleshooting-certs-auto.adoc[leveloffset=+1]
+include::modules/troubleshooting-certs-auto.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
@@ -44,21 +44,21 @@ include::modules/telco-troubleshooting-certs-auto.adoc[leveloffset=+1]
 * xref:../../../security/certificate_types_descriptions/control-plane-certificates.adoc#cert-types-control-plane-certificates_cert-types-control-plane-certificates[Control plane certificates]
 * xref:../../../security/certificate_types_descriptions/ingress-certificates.adoc#cert-types-ingress-certificates_cert-types-ingress-certificates[Ingress certificates]
 
-include::modules/telco-troubleshooting-certs-auto-etcd.adoc[leveloffset=+2]
+include::modules/troubleshooting-certs-auto-etcd.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../security/certificate_types_descriptions/etcd-certificates.adoc#cert-types-etcd-certificates_cert-types-etcd-certificates[etcd certificates]
 
-include::modules/telco-troubleshooting-certs-auto-node.adoc[leveloffset=+2]
+include::modules/troubleshooting-certs-auto-node.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../security/certificate_types_descriptions/node-certificates.adoc#cert-types-node-certificates_cert-types-node-certificates[Node certificates]
 
-include::modules/telco-troubleshooting-certs-auto-service-ca.adoc[leveloffset=+2]
+include::modules/troubleshooting-certs-auto-service-ca.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
 .Additional resources

edge_computing/day_2_core_cnf_clusters/troubleshooting/telco-troubleshooting-cluster-maintenance.adoc renamed to edge_computing/day_2_core_cnf_clusters/troubleshooting/troubleshooting-cluster-maintenance.adoc

@@ -1,8 +1,8 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="telco-troubleshooting-cluster-maintenance"]
+[id="troubleshooting-cluster-maintenance"]
 = Cluster maintenance
 include::_attributes/common-attributes.adoc[]
-:context: telco-troubleshooting-cluster-maintenance
+:context: troubleshooting-cluster-maintenance
 
 toc::[]
 
@@ -17,5 +17,5 @@ You can troubleshoot more effectively by completing these tasks:
 For hardware monitoring, contact your hardware vendor to find the appropriate logging tool for your specific hardware.
 ====
 
-include::modules/telco-troubleshooting-clusters-check-cluster-operators.adoc[leveloffset=+1]
-include::modules/telco-troubleshooting-clusters-check-for-failed-pods.adoc[leveloffset=+1]
+include::modules/troubleshooting-clusters-check-cluster-operators.adoc[leveloffset=+1]
+include::modules/troubleshooting-clusters-check-for-failed-pods.adoc[leveloffset=+1]

edge_computing/day_2_core_cnf_clusters/troubleshooting/telco-troubleshooting-general-troubleshooting.adoc renamed to edge_computing/day_2_core_cnf_clusters/troubleshooting/troubleshooting-general-troubleshooting.adoc

@@ -1,8 +1,8 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="telco-troubleshooting-general-troubleshooting"]
+[id="troubleshooting-general-troubleshooting"]
 = General troubleshooting
 include::_attributes/common-attributes.adoc[]
-:context: telco-troubleshooting-general-troubleshooting
+:context: troubleshooting-general-troubleshooting
 
 toc::[]
 
@@ -14,15 +14,15 @@ To narrow down the potential problematic areas, complete one or more of the foll
 * Debug a pod
 * Review events
 
-include::modules/telco-troubleshooting-general-query-cluster.adoc[leveloffset=+1]
+include::modules/troubleshooting-general-query-cluster.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../cli_reference/openshift_cli/developer-cli-commands.adoc#oc-get[oc get]
 * xref:../../../support/troubleshooting/investigating-pod-issues.adoc#reviewing-pod-status_investigating-pod-issues[Reviewing pod status]
 
-include::modules/telco-troubleshooting-general-check-logs.adoc[leveloffset=+1]
+include::modules/troubleshooting-general-check-logs.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
@@ -32,37 +32,37 @@ include::modules/telco-troubleshooting-general-check-logs.adoc[leveloffset=+1]
 * xref:../../../support/troubleshooting/investigating-pod-issues.adoc#inspecting-pod-and-container-logs_investigating-pod-issues[Inspecting pod and container logs]
 
 
-include::modules/telco-troubleshooting-general-describe-pod.adoc[leveloffset=+1]
+include::modules/troubleshooting-general-describe-pod.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../cli_reference/openshift_cli/developer-cli-commands.adoc#oc-describe[oc describe]
 
-include::modules/telco-troubleshooting-general-review-events.adoc[leveloffset=+1]
+include::modules/troubleshooting-general-review-events.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../security/container_security/security-monitoring.adoc#security-monitoring-events_security-monitoring[Watching cluster events]
 
-include::modules/telco-troubleshooting-general-connect-to-pod.adoc[leveloffset=+1]
+include::modules/troubleshooting-general-connect-to-pod.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../cli_reference/openshift_cli/developer-cli-commands.adoc#oc-rsh[oc rsh]
 * xref:../../../support/troubleshooting/investigating-pod-issues.adoc#accessing-running-pods_investigating-pod-issues[Accessing running pods]
 
-include::modules/telco-troubleshooting-general-debug-pod.adoc[leveloffset=+1]
+include::modules/troubleshooting-general-debug-pod.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources
 
 * xref:../../../cli_reference/openshift_cli/developer-cli-commands.adoc#oc-debug[oc debug]
 * xref:../../../support/troubleshooting/investigating-pod-issues.adoc#starting-debug-pods-with-root-access_investigating-pod-issues[Starting debug pods with root access]
 
-include::modules/telco-troubleshooting-general-run-command-on-pod.adoc[leveloffset=+1]
+include::modules/troubleshooting-general-run-command-on-pod.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources

edge_computing/day_2_core_cnf_clusters/troubleshooting/telco-troubleshooting-intro.adoc renamed to edge_computing/day_2_core_cnf_clusters/troubleshooting/troubleshooting-intro.adoc

@@ -1,8 +1,8 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="telco-troubleshooting-intro"]
+[id="troubleshooting-intro"]
 = Troubleshooting and maintaining OpenShift clusters
 include::_attributes/common-attributes.adoc[]
-:context: telco-troubleshooting-intro
+:context: troubleshooting-intro
 
 toc::[]
 

edge_computing/day_2_core_cnf_clusters/troubleshooting/telco-troubleshooting-mco.adoc renamed to edge_computing/day_2_core_cnf_clusters/troubleshooting/troubleshooting-mco.adoc

@@ -1,8 +1,8 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="telco-troubleshooting-mco"]
+[id="troubleshooting-mco"]
 = Machine Config Operator
 include::_attributes/common-attributes.adoc[]
-:context: telco-troubleshooting-mco
+:context: troubleshooting-mco
 
 toc::[]
 
@@ -12,9 +12,9 @@ The Machine Config Operator differentiates between different groups of nodes in
 These groups of nodes run worker or application pods, which are called `MachineConfigPool` (`mcp`) groups.
 The same machine config is applied on all nodes or only on one MCP in the cluster.
 
-For more information about how and why to apply MCPs in a telco core cluster, see xref:../../../edge_computing/day_2_core_cnf_clusters/updating/telco-update-ocp-update-prep.adoc#telco-update-applying-mcp-labels-to-nodes-before-the-update_ocp-update-prep[Applying MachineConfigPool labels to nodes before the update].
+For more information about how and why to apply MCPs in a telco core cluster, see xref:../../../edge_computing/day_2_core_cnf_clusters/updating/update-ocp-update-prep.adoc#update-applying-mcp-labels-to-nodes-before-the-update_ocp-update-prep[Applying MachineConfigPool labels to nodes before the update].
 
 For more information about the Machine Config Operator, see xref:../../../operators/operator-reference.adoc#machine-config-operator_cluster-operators-ref[Machine Config Operator].
 
-include::modules/telco-troubleshooting-mco-purpose.adoc[leveloffset=+1]
-include::modules/telco-troubleshooting-mco-apply-several-mcs.adoc[leveloffset=+1]
+include::modules/troubleshooting-mco-purpose.adoc[leveloffset=+1]
+include::modules/troubleshooting-mco-apply-several-mcs.adoc[leveloffset=+1]

edge_computing/day_2_core_cnf_clusters/troubleshooting/telco-troubleshooting-security.adoc renamed to edge_computing/day_2_core_cnf_clusters/troubleshooting/troubleshooting-security.adoc

@@ -1,14 +1,14 @@
 :_mod-docs-content-type: ASSEMBLY
-[id="telco-troubleshooting-security"]
+[id="troubleshooting-security"]
 = Security
 include::_attributes/common-attributes.adoc[]
-:context: telco-troubleshooting-security
+:context: troubleshooting-security
 
 toc::[]
 
 Implementing a robust cluster security profile is important for building resilient environments.
 
-include::modules/telco-troubleshooting-security-authentication.adoc[leveloffset=+1]
+include::modules/troubleshooting-security-authentication.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
 .Additional resources

modules/telco-troubleshooting-bmn-connect-to-node.adoc renamed to modules/troubleshooting-bmn-connect-to-node.adoc

@@ -1,9 +1,9 @@
 // Module included in the following assemblies:
 //
-// * edge_computing/day_2_core_cnf_clusters/troubleshooting/telco-troubleshooting-bmn-maintenance.adoc
+// * edge_computing/day_2_core_cnf_clusters/troubleshooting/troubleshooting-bmn-maintenance.adoc
 
 :_mod-docs-content-type: PROCEDURE
-[id="telco-troubleshooting-bmn-connect-to-node_{context}"]
+[id="troubleshooting-bmn-connect-to-node_{context}"]
 = Connecting to a bare-metal node in your cluster
 
 You can connect to bare-metal cluster nodes for general maintenance tasks.

modules/telco-troubleshooting-bmn-move-apps-to-pods.adoc renamed to modules/troubleshooting-bmn-move-apps-to-pods.adoc

@@ -1,9 +1,9 @@
 // Module included in the following assemblies:
 //
-// * edge_computing/day_2_core_cnf_clusters/troubleshooting/telco-troubleshooting-bmn-maintenance.adoc
+// * edge_computing/day_2_core_cnf_clusters/troubleshooting/troubleshooting-bmn-maintenance.adoc
 
 :_mod-docs-content-type: PROCEDURE
-[id="telco-troubleshooting-bmn-move-apps-to-pods_{context}"]
+[id="troubleshooting-bmn-move-apps-to-pods_{context}"]
 = Moving applications to pods within the cluster
 
 For scheduled hardware maintenance, you need to consider how to move your application pods to other nodes within the cluster without affecting the pod workload.

modules/telco-troubleshooting-bmn-replace-dimm.adoc renamed to modules/troubleshooting-bmn-replace-dimm.adoc

@@ -1,9 +1,9 @@
 // Module included in the following assemblies:
 //
-// * edge_computing/day_2_core_cnf_clusters/troubleshooting/telco-troubleshooting-bmn-maintenance.adoc
+// * edge_computing/day_2_core_cnf_clusters/troubleshooting/troubleshooting-bmn-maintenance.adoc
 
 :_mod-docs-content-type: CONCEPT
-[id="telco-troubleshooting-bmn-replace-dimm_{context}"]
+[id="troubleshooting-bmn-replace-dimm_{context}"]
 = DIMM memory replacement
 
 Dual in-line memory module (DIMM) problems sometimes only appear after a server reboots.