Typo fix, heading style compliance

Author: denrea

articles/operator-service-manager/TOC.yml

@@ -35,7 +35,8 @@
     items:
       - name: Get Started with Safe Upgrade Practices
         href: safe-upgrade-practices.md
-      - name: Control rollback beavhior on upgrade failure 
+      - name: Control rollback behavior on upgrade failure 
+
         href: safe-upgrades-nf-level-rollback.md
 - name: Quickstarts
   expanded: false

articles/operator-service-manager/index.yml

@@ -90,7 +90,7 @@ landingContent:
             url: safe-upgrade-practices.md
       - linkListType: concept
         links:
-          - text: Control rollback beavhior on upgrade failure
+          - text: Control rollback behavior on upgrade failure
             url: safe-upgrades-nf-level-rollback.md
 
   # Card

articles/operator-service-manager/safe-upgrades-nf-level-rollback.md

@@ -98,15 +98,15 @@ example:
 > * If multiple entries of nfConfiguration are found in the roleOverrideValues, then the NF reput is returned as a bad request.
 
 ## How to troubleshoot rollback on failure
-### Understanding Pod States
+### Understand pod states
 Understanding the different pod states is crucial for effective troubleshooting. The following are the most common pod states:
 * Pending: Pod scheduling is in progress by Kubernetes.
 * Running: All containers in the pod are running and healthy.
 * Failed: One or more containers in the pod are terminated with a nonzero exit code.
 * CrashLoopBackOff: A container within the pod is repeatedly crashing and Kubernetes is unable to restart it.
 * ContainerCreating: Container creation is in progress by the container runtime.
 
-### Checking Pod Status and Logs
+### Check pod status and logs
 First start by checking pod status and logs using a kubectl command:
 ```
 $ kubectl get pods