Move ServiceMonitor into its own section instead of using tabs

Author: shaun-nx

docs/content/logging-and-monitoring/prometheus.md

@@ -15,9 +15,7 @@ The Ingress Controller exposes a number of metrics in the [Prometheus](https://p
 
 ## Enabling Metrics
 
-{{<tabs name="apply-and-configure-prometheus-resource">}}
-
-{{%tab name="Using Manifest"%}}
+### Using Manifest
 
 If you're using *Kubernetes manifests* (Deployment or DaemonSet) to install the Ingress Controller, to enable Prometheus metrics:
 
@@ -39,13 +37,13 @@ If you're using *Kubernetes manifests* (Deployment or DaemonSet) to install the
         prometheus.io/scheme: http
     ```
 
-{{%/tab%}}
-
-{{%tab name="Using Helm"%}}
+### Using Helm
 
 If you're using *Helm* to install the Ingress Controller, to enable Prometheus metrics, configure the `prometheus.*` parameters of the Helm chart. See the [Installation with Helm](/nginx-ingress-controller/installation/installation-with-helm) doc.
 
-When deploying with *Helm*, you can also choose to deploy a `Service` and `ServiceMonitor` resource using the `prometheus.service.*` and `prometheus.serviceMonitor.*` parameters.
+### Using ServiceMonitor
+
+When deploying with *Helm*, you can deploy a `Service` and `ServiceMonitor` resource using the `prometheus.service.*` and `prometheus.serviceMonitor.*` parameters.
 When these resources are deployed, Prometheus metrics exposed by the NGINX Ingress Controller can be captured and enumerated using a `Prometheus` resource alongside a Prometheus Operator deployment.
 
 To view metrics captured this way, the following is required:
@@ -56,9 +54,6 @@ curl https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/$
 ```
 * A working [Prometheus resource and Prometheus Operator](https://prometheus-operator.dev/docs/user-guides/getting-started/)
 
-{{%/tab%}}
-
-{{</tabs>}}
 
 ## Available Metrics