docs: normalize weight values

The `kube` page index gets a weight of 300 and its child pages should
get weight values starting > 300.

Signed-off-by: Simon Pasquier <spasquie@redhat.com>

docs/blackbox-exporter.md

@@ -1,15 +1,14 @@
 ---
-weight: 630
+weight: 304
 toc: true
 title: Blackbox Exporter
 menu:
     docs:
         parent: kube
-lead: This Document documents the types introduced by the Prometheus Operator to be consumed by users.
-lastmod: "2021-03-08T08:49:31+00:00"
+lead: This guide will help you deploying the blackbox-exporter with the Probe custom resource definition.
 images: []
 draft: false
-description: Generated API docs for the Prometheus Operator
+description: This guide will help you deploying the blackbox-exporter with the Probe custom resource definition.
 date: "2021-03-08T08:49:31+00:00"
 ---
 

docs/customizations/developing-prometheus-rules-and-grafana-dashboards.md

@@ -1,15 +1,14 @@
 ---
-weight: 650
+weight: 307
 toc: true
 title: Prometheus Rules and Grafana Dashboards
 menu:
     docs:
         parent: kube
-lead: Create Prometheus Rules and Grafana Dashboards on top of kube-prometheus
+lead: This guide will help you adding Prometheus Rules and Grafana Dashboards on top of kube-prometheus
 images: []
 draft: false
-description: Create Prometheus Rules and Grafana Dashboards on top of kube-prometheus
-date: "2021-03-08T23:04:32+01:00"
+description: This guide will help you adding Prometheus Rules and Grafana Dashboards on top of kube-prometheus
 ---
 
 `kube-prometheus` ships with a set of default [Prometheus rules](https://prometheus.io/docs/prometheus/latest/configuration/recording_rules/) and [Grafana](http://grafana.com/) dashboards. At some point one might like to extend them, the purpose of this document is to explain how to do this.

docs/customizations/exposing-prometheus-alertmanager-grafana-ingress.md

@@ -1,15 +1,14 @@
 ---
-weight: 500
+weight: 303
 toc: true
 title: Expose via Ingress
 menu:
     docs:
         parent: kube
-lead: How to setup a Kubernetes Ingress to expose the Prometheus, Alertmanager and Grafana.
+lead: This guide will help you deploying a Kubernetes Ingress to expose Prometheus, Alertmanager and Grafana.
 images: []
 draft: false
-description: How to setup a Kubernetes Ingress to expose the Prometheus, Alertmanager and Grafana.
-date: "2021-03-08T23:04:32+01:00"
+description: This guide will help you deploying a Kubernetes Ingress to expose Prometheus, Alertmanager and Grafana.
 ---
 
 In order to access the web interfaces via the Internet [Kubernetes Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/) is a popular option. This guide explains, how Kubernetes Ingress can be setup, in order to expose the Prometheus, Alertmanager and Grafana UIs, that are included in the [kube-prometheus](https://github.com/prometheus-operator/kube-prometheus) project.

docs/deploy-kind.md

@@ -1,17 +1,14 @@
 ---
-weight: 500
+weight: 301
 toc: true
 title: Deploy to kind
 menu:
     docs:
         parent: kube
-lead: Deploy kube-prometheus to Kubernets kind.
+lead: This guide will help you deploying kube-prometheus on Kubernetes kind.
 images: []
 draft: false
-description: Deploy kube-prometheus to Kubernets kind.
-date: "2021-03-08T23:04:32+01:00"
----
-
+description: This guide will help you deploying kube-prometheus on Kubernetes kind.
 ---
 
 Time to explain how!

docs/kube-prometheus-on-kubeadm.md

@@ -1,15 +1,14 @@
 ---
-weight: 500
+weight: 302
 toc: true
 title: Deploy to kubeadm
 menu:
     docs:
         parent: kube
-lead: Deploy kube-prometheus to Kubernets kubeadm.
+lead: This guide will help you deploying kube-prometheus on Kubernetes kubeadm.
 images: []
 draft: false
-description: Deploy kube-prometheus to Kubernets kubeadm.
-date: "2021-03-08T23:04:32+01:00"
+description: This guide will help you deploying kube-prometheus on Kubernetes kubeadm.
 ---
 
 The [kubeadm](https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/) tool is linked by Kubernetes as the offical way to deploy and manage self-hosted clusters. kubeadm does a lot of heavy lifting by automatically configuring your Kubernetes cluster with some common options. This guide is intended to show you how to deploy Prometheus, Prometheus Operator and Kube Prometheus to get you started monitoring your cluster that was deployed with kubeadm.

docs/monitoring-external-etcd.md

@@ -1,15 +1,14 @@
 ---
-weight: 640
+weight: 305
 toc: true
 title: Monitoring external etcd
 menu:
     docs:
         parent: kube
-lead: This guide will help you monitor an external etcd cluster.
+lead: This guide will help you monitoring an external etcd cluster.
 images: []
 draft: false
-description: This guide will help you monitor an external etcd cluster.
-date: "2021-03-08T23:04:32+01:00"
+description: This guide will help you monitoring an external etcd cluster.
 ---
 
 When the etcd cluster is not hosted inside Kubernetes.

docs/monitoring-other-namespaces.md

@@ -1,22 +1,21 @@
 ---
-weight: 640
+weight: 306
 toc: true
 title: Monitoring other Namespaces
 menu:
     docs:
         parent: kube
-lead: This guide will help you monitor applications in other Namespaces.
+lead: This guide will help you monitoring applications in other namespaces.
 images: []
 draft: false
-description: This guide will help you monitor applications in other Namespaces.
-date: "2021-03-08T23:04:32+01:00"
+description: This guide will help you monitoring applications in other namespaces.
 ---
 
-This guide will help you monitor applications in other Namespaces. By default the RBAC rules are only enabled for the `Default` and `kube-system` Namespace during Install.
+By default the RBAC rules are only enabled for the `Default` and `kube-system` namespaces.
 
 # Setup
 
-You have to give the list of the Namespaces that you want to be able to monitor.
+You have to give the list of the namespaces that you want to be able to monitor.
 This is done in the variable `prometheus.roleSpecificNamespaces`. You usually set this in your `.jsonnet` file when building the manifests.
 
 Example to create the needed `Role` and `RoleBinding` for the Namespace `foo` :