From 83f6ec595d76796ca3072553a05c0e52b5c33660 Mon Sep 17 00:00:00 2001
From: jcol <116673918+jeff-colucci@users.noreply.github.com>
Date: Tue, 15 Oct 2024 12:55:32 -0500
Subject: [PATCH] Update k8s-agent-operator.mdx

style changes
---
 .../installation/k8s-agent-operator.mdx                       | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx
index cd9be745ab2..65fad0cbbdc 100644
--- a/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx
+++ b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx
@@ -262,7 +262,7 @@ Once an application is monitored, it's not automatically upgraded to a newer ver
 
 ## Remove APM instrumentation in applications [#remove-apm-instrumentation]
 
-To remove the APM instrumentation in an application, you must remove the matching label selector inside either the podLabelSelector or namespaceLabelSelector used by the Kubernetes agent operator and then simply restart the deployment. In a few seconds, you will see that the APM agents have been automatically removed.
+To remove the APM instrumentation in an application, you must remove the matching label selector inside either the `podLabelSelector` or `namespaceLabelSelector` used by the Kubernetes agent operator, then restart the deployment. In a few seconds, you will see that the APM agents have been automatically removed.
 
 ## Updating the Kubernetes agent operator [#upgrading-k8s-operator]
 
@@ -374,7 +374,7 @@ If your applications are not instrumented, you should check the following:
   kubectl get instrumentation -n NAMESPACE
   ```
 
-* Check that the pod has the required labels that enable automatic instrumentation through CR when using podLabelSelector. Similarly, check that the namespace has the required labels when using namespaceLabelSelector inside the CR.
+* Check that the pod has the required labels that enable automatic instrumentation through CR when using `podLabelSelector`. Similarly, check that the namespace has the required labels when using `namespaceLabelSelector` inside the CR.
 
   ```shell
   kubectl get pod POD_NAME -n NAMESPACE  -o jsonpath='{.metadata.annotations}'