Apply suggestions from code review

Co-authored-by: Nox <[email protected]>

Author: bene2k1

pages/cockpit/how-to/configure-alerts-for-scw-resources.mdx

@@ -110,10 +110,10 @@ Switch between the tabs below to create alerts for a Scaleway Instance, an Objec
 
     1. In the query field next to the **Loading metrics... >** button, paste the following query. Make sure that the values for the labels you have selected (for example, `resource_name`) correspond to those of the target resource.
         ```bash
-        rate(kubernetes_cluster_k8s_shoot_nodes_Pods_usage_total{resource_name="k8s-par-quizzical-chatelet"}[15m]) == 0
+        rate(kubernetes_cluster_k8s_shoot_nodes_pods_usage_total{resource_name="k8s-par-quizzical-chatelet"}[15m]) == 0
         ```
         <Message type="tip">
-         The `kubernetes_cluster_k8s_shoot_nodes_Pods_usage_total` metric represents the total number of Pods currently running across all nodes in your Kubernetes cluster. It is helpful to monitor current Pod consumption per node pool or cluster, and help track resource saturation or unexpected workload spikes.
+         The `kubernetes_cluster_k8s_shoot_nodes_pods_usage_total` metric represents the total number of Pods currently running across all nodes in your Kubernetes cluster. It is helpful to monitor current Pod consumption per node pool or cluster, and help track resource saturation or unexpected workload spikes.
         </Message>
     2. In the **Set alert evaluation behavior** field, specify how long the condition must be true before triggering the alert.
     3. Enter a name in the **Namespace** and **Group** fields to categorize and manage your alert rules. Rules that share the same group will use the same configuration, including the evaluation interval which determines how often the rule is evaluated (by default: every 1 minute). You can modify this interval later in the group settings.

pages/cockpit/how-to/send-logs-from-k8s-to-cockpit.mdx

@@ -58,7 +58,7 @@ nodeLogs:
     enabled: true
     destinations: ["my-cockpit-logs"]
 # -- Pod logs.
-PodLogs:
+podLogs:
   enabled: true
   destinations: ["my-cockpit-logs"]
   volumeGatherSettings:

pages/gpu/how-to/use-mig-with-kubernetes.mdx

@@ -359,14 +359,14 @@ In this guide, we will explore the capabilities of NVIDIA MIG within a Kubernete
 4. Clean the deployment:
     ```
     % kubectl delete -f deploy-mig.yaml
-    Pod "test-1" deleted
-    Pod "test-2" deleted
-    Pod "test-3" deleted
-    Pod "test-4" deleted
-    Pod "test-5" deleted
-    Pod "test-6" deleted
-    Pod "test-7" deleted
-    Pod "test-8" deleted
+    pod "test-1" deleted
+    pod "test-2" deleted
+    pod "test-3" deleted
+    pod "test-4" deleted
+    pod "test-5" deleted
+    pod "test-6" deleted
+    pod "test-7" deleted
+    pod "test-8" deleted
     ```
 
 ## Disable MIG inside a Kubernetes cluster

pages/kubernetes/concepts.mdx

@@ -1,7 +1,7 @@
 ---
 title: Kubernetes - Concepts
 description: This page explains all the concepts related to Kubernetes Kapsule
-tags: kubernetes autoheal autoscale auto-upgrade container-runtime cni control-plane kubeconfi kubectl Pods replicaset
+tags: kubernetes autoheal autoscale auto-upgrade container-runtime cni control-plane kubeconfi kubectl pods replicaset
 dates:
   validation: 2025-09-03
 ---

pages/kubernetes/how-to/monitor-data-plane-with-cockpit.mdx

@@ -69,7 +69,7 @@ You can use Scaleway’s **[Easy Deploy](/kubernetes/how-to/enable-easy-deploy/)
     <Message type="note">
       You can edit the default deployment configuration to filter logs by source (under `config.snippets.scrapeConfigs` in the YAML file). For example:
       ```yaml
-      cockpit_promtail_scrape_config_Pods: "namespace1,namespace2"
+      cockpit_promtail_scrape_config_pods: "namespace1,namespace2"
       cockpit_promtail_scrape_config_journal: "kubelet.service,kube-proxy.service"
       ```
     </Message>
@@ -84,7 +84,7 @@ config:
 
   snippets:
     scrapeConfigs: |
-      {{{- cockpit_promtail_scrape_config_Pods }}} # Default: log all Pods
+      {{{- cockpit_promtail_scrape_config_pods }}} # Default: log all Pods
       {{{- cockpit_promtail_scrape_config_journal }}} # Default: log all system components
 extraVolumeMounts:
   - mountPath: /var/log/journal
@@ -109,7 +109,7 @@ Once Promtail is running:
 4. **Filter Pod logs** by:
    - `Datasource` which is automatically created upon deployment and visible in the Cockpit console
    - `Cluster Name` ( e.g. `my-kapsule-cluster`)
-   - `namespace`, `Pod`, or `container` labels to isolate specific workloads
+   - `namespace`, `pod`, or `container` labels to isolate specific workloads
    - `Time range` to limit how far back in history you want to query
 5. Alternatively, in Grafana's menu, navigate to **Dashboards** and select **Kubernetes Cluster Node Logs** to view system logs collected from nodes in your clusters.
 6. **Filter node logs** by:

pages/kubernetes/how-to/recover-space-etcd.mdx

@@ -27,7 +27,7 @@ Kind: endpoints, Size: 82063
 Kind: events, Size: 375065
 Kind: limitranges, Size: 68
 Kind: persistentvolumeclaims, Size: 68
-Kind: Pods, Size: 3326153
+Kind: pods, Size: 3326153
 [...]
 ```
 

pages/kubernetes/reference-content/introduction-to-kubernetes.mdx

@@ -103,7 +103,7 @@ The `kube-proxy` is a network proxy running on each node in the cluster. It main
 #### Container runtime
 
 Kubernetes is able to manage containers, but is not capable of running them. Therefore, a container runtime is required that is responsible for running containers.
-Kubernetes Kapsule supports the `containerd` container runtimes as well as any implementation of the [Kubernetes CRI (Container Runtime Interface)](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/container-runtime-interface.md).
+Kubernetes Kapsule provides the `containerd` container runtime.
 
 ## Kubernetes objects
 
@@ -115,7 +115,7 @@ A **Pod** is the smallest and simplest unit in the Kubernetes object model. Cont
 
 ### Services
 
-A **service** is an abstraction which defines a logical group of Pods that perform the same function and a policy on how to access them. The service provides a stable endpoint (IP address) and acts like a Load Balancer by redirecting requests to the different Pods in the service. The service abstraction allows scaling out or replacing dead Pods without making changes in the configuration of an application.
+A **Service** is an abstraction which defines a logical group of Pods that perform the same function and a policy on how to access them. The service provides a stable endpoint (IP address) and acts like a Load Balancer by redirecting requests to the different Pods in the service. The service abstraction allows scaling out or replacing dead Pods without making changes in the configuration of an application.
 
 By default, services are only available using internally routable IP addresses, but can be exposed publicly.
 

pages/kubernetes/reference-content/kubernetes-load-balancer.mdx

@@ -156,10 +156,10 @@ For full details on how to use Load Balancer annotations when creating your Load
 If your Load Balancer is configured for [SSL offload](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/#configuring-a-load-balancer-for-ssl-offloading), and you have several services behind the same Load Balancer, you will encounter an SSL error when trying to reach the other services using HTTPS.
 
 Example:
-- PodA
-- PodB (`https://serviceB.example.com`)
+- podA
+- podB (`https://serviceB.example.com`)
 
-From PodA, a curl to `https://serviceB.example.com` will result in an SSL error.
+From podA, a curl to `https://serviceB.example.com` will result in an SSL error.
 
 To force the Load Balancer to handle all requests using the SSL offload, enable the [use hostname annotations](https://github.com/scaleway/scaleway-cloud-controller-manager/blob/master/docs/loadbalancer-annotations.md#servicebetakubernetesioscw-loadbalancer-use-hostname) on your Load Balancer service.
 

pages/kubernetes/reference-content/set-iam-permissions-and-implement-rbac.mdx

@@ -15,7 +15,7 @@ It allows you to assign roles to users, groups or `ServicesAccount` via `RoleBin
 Key components of RBAC in Kubernetes include:
 
 - **Roles and ClusterRoles:**
-   - `Roles`: These are specific to a namespace, and define a set of permissions for resources within that namespace (e.g., Pods, services).
+   - `Roles`: These are specific to a namespace, and define a set of permissions for resources within that namespace (e.g., Pods, Services).
    - `ClusterRoles`: These are similar to roles but apply cluster-wide, spanning all namespaces.
 - **RoleBindings and ClusterRoleBindings:**
    - `RoleBindings`: These associate a set of permissions defined in a role with a user, group, or service account within a specific namespace.
@@ -238,9 +238,9 @@ rules:
      - nodes
      - persistentvolumeclaims
      - persistentvolumeclaims/status
-     - Pods
-     - Pods/log
-     - Pods/status
+     - pods
+     - pods/log
+     - pods/status
      - replicationcontrollers
      - replicationcontrollers/scale
      - replicationcontrollers/status
@@ -258,7 +258,7 @@ rules:
    apiGroups:
      - metrics.k8s.io
    resources:
-     - Pods
+     - pods
      - nodes
 
 
@@ -290,8 +290,8 @@ rules:
    apiGroups:
      - autoscaling
    resources:
-     - horizontalPodautoscalers
-     - horizontalPodautoscalers/status
+     - horizontalpodautoscalers
+     - horizontalpodautoscalers/status
 
 
  - verbs:
@@ -335,8 +335,8 @@ rules:
    apiGroups:
      - policy
    resources:
-     - Poddisruptionbudgets
-     - Poddisruptionbudgets/status
+     - poddisruptionbudgets
+     - poddisruptionbudgets/status
 
 
  - verbs:

tutorials/deploy-istio-kapsule-proxy-protocol/index.mdx

@@ -338,5 +338,5 @@ Once you have added the configurations, you may need to restart the IngressGatew
 
 Run the following command to delete the existing Pods using `kubectl`. Kubernetes will spin up new ones automatically after you launch the command:
 ```bash
-kubectl delete Pod -n istio-system -l istio=ingressgateway
+kubectl delete pod -n istio-system -l istio=ingressgateway
 ```