TELCODOCS-2171#Generalize Day2Ops for Telco

Author: amolnar-rh

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

@@ -8,7 +8,7 @@ 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 that hardware maintenance.
+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]

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

@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-In telco networks, you must pay more attention to certain configurations due the nature of bare-metal deployments.
+When using bare-metal deployments on {product-title}, you must pay more attention to certain configurations which can have a significant impact on cluster stability.
 You can troubleshoot more effectively by completing these tasks:
 
 * Monitor for failed or failing hardware components

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

@@ -7,7 +7,7 @@ include::_attributes/common-attributes.adoc[]
 toc::[]
 
 When you encounter a problem, the first step is to find the specific area where the issue is happening.
-To narrow down the potential problematic areas, complete one or more tasks:
+To narrow down the potential problematic areas, complete one or more of the following tasks:
 
 * Query your cluster
 * Check your pod logs

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

@@ -1,6 +1,6 @@
 :_mod-docs-content-type: ASSEMBLY
 [id="telco-troubleshooting-intro"]
-= Troubleshooting and maintaining telco core CNF clusters
+= Troubleshooting and maintaining OpenShift clusters
 include::_attributes/common-attributes.adoc[]
 :context: telco-troubleshooting-intro
 
@@ -9,13 +9,13 @@ toc::[]
 Troubleshooting and maintenance are weekly tasks that can be a challenge if you do not have the tools to reach your goal, whether you want to update a component or investigate an issue.
 Part of the challenge is knowing where and how to search for tools and answers.
 
-To maintain and troubleshoot a bare-metal environment where high-bandwidth network throughput is required, see the following procedures.
+To maintain and troubleshoot a bare-metal environment with high performance requirements, see the following procedures.
 
 [IMPORTANT]
 ====
-This troubleshooting information is not a reference for configuring {product-title} or developing Cloud-native Network Function (CNF) applications.
+This troubleshooting information is not a reference for configuring {product-title} or developing cloud-native applications
 
-For information about developing CNF applications for telco, see link:https://redhat-best-practices-for-k8s.github.io/guide/[Red Hat Best Practices for Kubernetes].
+For information about developing cloud-native applications on {product-title}, see link:https://redhat-best-practices-for-k8s.github.io/guide/[Red Hat Best Practices for Kubernetes].
 ====
 
 include::modules/telco-troubleshooting-cnfs.adoc[leveloffset=+1]

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

@@ -6,7 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-Implementing a robust cluster security profile is important for building resilient telco networks.
+Implementing a robust cluster security profile is important for building resilient environments.
 
 include::modules/telco-troubleshooting-security-authentication.adoc[leveloffset=+1]
 

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

@@ -15,9 +15,9 @@ Configuring the cluster node from the host operating system is not recommended o
 
 To troubleshoot your nodes, you can do the following tasks:
 
-* Retrieve logs from node
+* Retrieve logs from a node
 * Use debugging
-* Use SSH to connect to the node
+* Use SSH to connect to a node
 
 [IMPORTANT]
 ====

modules/telco-troubleshooting-bmn-replace-nw-card.adoc

@@ -7,7 +7,7 @@
 = Cluster network card replacement
 
 When you replace a network card, the MAC address changes.
-The MAC address can be part of the DHCP or SR-IOV Operator configuration, router configuration, firewall rules, or application Cloud-native Network Function (CNF) configuration.
+The MAC address can be part of the DHCP or SR-IOV Operator configuration, router configuration, firewall rules, or application cloud-native application configuration.
 Before you bring back a node online after replacing a network card, you must verify that these configurations are up-to-date.
 
 [IMPORTANT]