Globally import Tabs and TabItem

versioned_docs/version-2.6/reference-guides/cluster-configuration/downstream-cluster-configuration/node-template-configuration/nutanix.md

@@ -2,7 +2,6 @@
 title: Nutanix Node Template Configuration
 ---
 
-
 ## Account Access
 
 | Parameter                    | Required | Description | Default

versioned_docs/version-2.6/reference-guides/cluster-configuration/downstream-cluster-configuration/node-template-configuration/vsphere.md

@@ -2,7 +2,6 @@
 title: VSphere Node Template Configuration
 ---
 
-
 ## Account Access
 
 | Parameter                | Required | Description |

versioned_docs/version-2.6/reference-guides/monitoring-v2-configuration/examples.md

@@ -2,7 +2,6 @@
 title: Examples
 ---
 
-
 ### ServiceMonitor
 
 An example ServiceMonitor custom resource can be found [here.](https://github.com/prometheus-operator/prometheus-operator/blob/master/example/prometheus-operator-crd/monitoring.coreos.com_servicemonitors.yaml)

versioned_docs/version-2.6/reference-guides/monitoring-v2-configuration/helm-chart-options.md

@@ -2,7 +2,6 @@
 title: Helm Chart Options
 ---
 
-
 ## Configuring Resource Limits and Requests
 
 The resource requests and limits can be configured when installing `rancher-monitoring`.

versioned_docs/version-2.6/reference-guides/monitoring-v2-configuration/receivers.md

@@ -2,9 +2,6 @@
 title: Receiver Configuration
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 The [Alertmanager Config](https://prometheus.io/docs/alerting/latest/configuration/#configuration-file) Secret contains the configuration of an Alertmanager instance that sends out notifications based on alerts it receives from Prometheus.
 
 :::note

versioned_docs/version-2.6/reference-guides/monitoring-v2-configuration/routes.md

@@ -2,9 +2,6 @@
 title: Route Configuration
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 The route configuration is the section of the Alertmanager custom resource that controls how the alerts fired by Prometheus are grouped and filtered before they reach the receiver.
 
 When a Route is changed, the Prometheus Operator regenerates the Alertmanager custom resource to reflect the changes.

versioned_docs/version-2.6/reference-guides/pipelines/configure-persistent-data.md

@@ -2,9 +2,6 @@
 title: Configuring Persistent Data for Pipeline Components
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
 The pipelines' internal Docker registry and the Minio workloads use ephemeral volumes by default. This default storage works out-of-the-box and makes testing easy, but you lose the build images and build logs if the node running the Docker Registry or Minio fails. In most cases this is fine. If you want build images and logs to survive node failures, you can configure the Docker Registry and Minio to use persistent volumes.
 
 This section assumes that you understand how persistent storage works in Kubernetes. For more information, refer to the section on [how storage works.](../../how-to-guides/new-user-guides/manage-clusters/create-kubernetes-persistent-storage/manage-persistent-storage/about-persistent-storage.md)

versioned_docs/version-2.6/reference-guides/single-node-rancher-in-docker/advanced-options.md

@@ -2,7 +2,6 @@
 title: Advanced Options for Docker Installs
 ---
 
-
 ### Custom CA Certificate
 
 If you want to configure Rancher to use a CA root certificate to be used when validating services, you would start the Rancher container sharing the directory that contains the CA root certificate.