k8s/installation: remove unnecessary header

k8s/installation: fixup! numbering and lists

src/content/docs/kubernetes-pixie/kubernetes-integration/installation/install-kubernetes-integration-using-helm.mdx

@@ -40,7 +40,6 @@ Note these values somewhere safe, as you will need them later during the install
 
 ## Install Kubernetes integration with Helm [#install-k8-helm]
 
-### Install with Helm 3 and nri-bundle (recommended)
 New Relic has several charts for the different components which offer different features for the platform:
 
 - [`newrelic-infrastructure-v3`](https://github.com/newrelic/helm-charts/tree/master/charts/newrelic-infrastructure-v3): Contains the main Kubernetes integration and the infrastructure agent. This is the core component for the New Relic Kubernetes experience, responsible for reporting most of the data that is surfaced in dashboard and the Kubernetes Cluster Explorer.
@@ -102,7 +101,7 @@ ksm:
   enabled: true
 ```
 
-3. Make sure everything is configured properly in the chart by running the following command. Notice that we are specifying `--dry-run` and `--debug`, so nothing will be installed in this step:
+4. Make sure everything is configured properly in the chart by running the following command. Notice that we are specifying `--dry-run` and `--debug`, so nothing will be installed in this step:
 
 ```shell
 helm upgrade --install <mark>newrelic</mark> newrelic/nri-bundle \
@@ -126,7 +125,7 @@ Please notice and adjust the following flags:
 
 Our Kubernetes charts have a comprehensive set of flags and tunables that can be edited to better fit your particular needs. Please check the [Configure the integration](#configure) section below to see what can be changed.
 
-4. Install the Kubernetes integration by running the command without `--debug` and `--dry-run`:
+5. Install the Kubernetes integration by running the command without `--debug` and `--dry-run`:
 
 ```shell
 helm upgrade --install <mark>newrelic</mark> newrelic/nri-bundle \
@@ -135,7 +134,7 @@ helm upgrade --install <mark>newrelic</mark> newrelic/nri-bundle \
 <mark>--devel</mark>
 ```
 
-5. Check that pods are being deployed and reach a stable state:
+6. Check that pods are being deployed and reach a stable state:
 
 ```shell
 kubectl -n <mark>newrelic</mark> get pods -w
@@ -260,14 +259,14 @@ newrelic-infrastructure:
 
 The full list of flags that can be tweaked can be found in our chart's repository:
 * [`newrelic-infrastructure`](https://github.com/newrelic/helm-charts/tree/master/charts/newrelic-infrastructure-v3)
-  - Configure debug logs, privilege mode, control plane monitoring, etc.
+ * Configure debug logs, privilege mode, control plane monitoring, etc.
 * [`nri-kube-events`](https://github.com/newrelic/helm-charts/tree/master/charts/nri-kube-events)
 * [`nri-metadata-injection`](https://github.com/newrelic/helm-charts/tree/master/charts/nri-metadata-injection)
-  - Configure how the webhook for APM linkage is deployed.
+ * Configure how the webhook for APM linkage is deployed.
 * [`nri-prometheus`](https://github.com/newrelic/helm-charts/tree/master/charts/nri-prometheus)
- - Configure which prometheus endpoints are scraped.
+ * Configure which prometheus endpoints are scraped.
 * [`newrelic-logging`](https://github.com/newrelic/helm-charts/tree/master/charts/newrelic-logging)
- - Configure which logs are sent to New Relic.
+ * Configure which logs are sent to New Relic.
 
 <Callout variant="tip">
   Remember that when specifying options for these charts, you must put them under the chart name in your `values-newrelic.yaml`.