fix(gen): fixed some small issues (#4348)

* fix(gen): fixed some small issues

* Apply suggestions from code review

* Apply suggestions from code review

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

* fix(k8s): fix link to scw website

---------

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

Author: bene2k1

menu/navigation.json

@@ -2904,6 +2904,16 @@
                 ],
                 "label": "How to",
                 "slug": "how-to"
+              },
+              {
+                "items": [
+                  {
+                    "label": "Troubleshooting Distributed Data Lab execution issues",
+                    "slug": "cannot-run-data-lab"
+                  }
+                ],
+                "label": "Troubleshooting",
+                "slug": "troubleshooting"
               }
             ],
             "label": "Distributed Data Lab",

pages/data-lab/troubleshooting/index.mdx

@@ -0,0 +1,8 @@
+---
+meta:
+  title: Distributed Data Lab Troubleshooting
+  description: Troubleshoot common issues with Scaleway Distributed Data Lab.
+content:
+  h1: Distributed Data Lab Troubleshooting
+  paragraph: Troubleshoot common issues with Scaleway Distributed Data Lab.
+---

pages/kubernetes/how-to/monitor-cluster.mdx

@@ -24,7 +24,7 @@ Grafana's rich visualizations and ease of use make it an ideal choice. Cockpit o
 * Achieve a better understanding of your infrastructure by analyzing data on your API server, system applications and up/down scaling behavior
 
 <Message type="important">
-  **Control Plane monitoring**: Scaleway Kapsule natively provides monitoring for the control plane, free of charge. Additionally, monitoring of the data plane is possible. To monitor the data plane, refer to [How to monitor your Kubernetes Kapsule data plane with Cockpit](/kubernetes/how-to/monitor-data-plane-with-cockpit/). For detailed observability, refer to the [documentation on how to send logs from your Kubernetes cluster to your Cockpit](/cockpit/how-to/send-log-from-k8s-to-cockpit/).
+  **Control plane monitoring**: Scaleway Kapsule natively provides monitoring for the control plane, free of charge. Additionally, monitoring of the data plane is possible. To monitor the data plane, refer to [How to monitor your Kubernetes Kapsule data plane with Cockpit](/kubernetes/how-to/monitor-data-plane-with-cockpit/). For detailed observability, refer to the [documentation on how to send logs from your Kubernetes cluster to your Cockpit](/cockpit/how-to/send-logs-from-k8s-to-cockpit/).
 
   **Control plane vs. data plane**: The control plane is responsible for managing the Kubernetes cluster’s state and orchestrating workloads, while the data plane consists of the nodes that execute the workloads.
 

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

@@ -13,7 +13,7 @@ dates:
   posted: 2025-01-17
 ---
 
-You can now send **data plane** logs from your [Kapsule or Kosmos](https://www.scaleway.com/en/kubernetes) clusters to [Cockpit](https://www.scaleway.com/en/cockpit/), providing centralized, real-time access to application and system logs. Reduce complexity and manual work thanks to this integration, powered by a **Promtail** deployment via [Easy Deploy](/kubernetes/how-to/enable-easy-deploy/).
+You can now send **data plane** logs from your [Kapsule](https://www.scaleway.com/en/kubernetes-kapsule/) or [Kosmos](https://www.scaleway.com/en/kubernetes-kosmos/) clusters to [Cockpit](https://www.scaleway.com/en/cockpit/), providing centralized, real-time access to application and system logs. Reduce complexity and manual work thanks to this integration, powered by a **Promtail** deployment via [Easy Deploy](/kubernetes/how-to/enable-easy-deploy/).
 
 This feature allows you to:
 
@@ -168,8 +168,7 @@ Key points include:
 
 - [Observability Cockpit Overview](/cockpit/)
 - [Push logs to Cockpit (How-To)](/cockpit/how-to/send-metrics-logs-to-cockpit/)
-- [Send logs from your Kubernetes cluster to your Cockpit (How-To)](/cockpit/how-to/send-log-from-k8s-to-cockpit/)
+- [Send logs from your Kubernetes cluster to your Cockpit (How-To)](/cockpit/how-to/send-logs-from-k8s-to-cockpit/)
 - [Send metrics from your Kubernetes cluster to your Cockpit (How-To)](/cockpit/how-to/send-metrics-from-k8s-to-cockpit/)
 - [Promtail Documentation](https://grafana.com/docs/loki/latest/clients/promtail/)
-- [Scaleway Kapsule Documentation](/kubernetes/kapsule/quickstart/)
-- [Scaleway Kosmos Documentation](/kubernetes/kosmos/quickstart/)
+- [Scaleway Kubernetes Kapsule and Kosmos Documentation](/kubernetes/quickstart/)

pages/messaging/concepts.mdx

@@ -27,7 +27,7 @@ Credentials give services and platforms access to Scaleway NATS, Queues, and Top
 
 ## Dead Letter Queue
 
-A **D**ead **L**etter **Q**ueue (DLQ), or **undelivered-message queue**, receives and holds messages that cannot be delivered to their destination queues. If you designate a queue as a DLQ and its [storage quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#queues) is reached, messages won't be redriven to the DLQ until enough free space is available again. If your DLQ is at its full quota, free up space by receiving and deleting messages from any queue in your Project.
+A **D**ead **L**etter **Q**ueue (DLQ), or **undelivered-message queue**, receives and holds messages that cannot be delivered to their destination queues. If you designate a queue as a DLQ and its [storage quota](/organizations-and-projects/additional-content/organization-quotas/#queues) is reached, messages won't be redriven to the DLQ until enough free space is available again. If your DLQ is at its full quota, free up space by receiving and deleting messages from any queue in your Project.
 
 ## Fanout
 

pages/organizations-and-projects/additional-content/organization-quotas.mdx

@@ -265,7 +265,7 @@ For example, if you choose to create a container with 512 MB of memory and a max
 
 Scaleway NATS is a message broker tool based on the NATS protocol, that allows you to transfer messages between different microservices and platforms.
 
-The following usage limits are enforced as Organization quotas when using Scaleway [NATS](/serverless/messaging/concepts/#nats):
+The following usage limits are enforced as Organization quotas when using Scaleway [NATS](/messaging/concepts/#nats):
 
 **NATS**
 

pages/serverless-containers/concepts.mdx

@@ -154,7 +154,7 @@ A container's privacy policy defines whether a container may be invoked anonymou
 
 ## Queue trigger
 
-A queue trigger is a mechanism that connects a container to a queue created with [Scaleway Queues](/serverless/messaging/concepts/#queues), and invokes the container automatically whenever a message is added to the queue.
+A queue trigger is a mechanism that connects a container to a queue created with [Scaleway Queues](/messaging/concepts/#queues), and invokes the container automatically whenever a message is added to the queue.
 
 For each message that is sent to a queue, the trigger reads the message and invokes the associated container with the message as the input parameter.
 The container can then process the message and perform any required actions, such as updating a database or sending a notification.

pages/serverless-functions/how-to/create-a-function.mdx

@@ -31,7 +31,7 @@ This page shows you how to deploy a [function](/serverless-functions/concepts/#f
 
 ### Function configuration
 
-1. Select a runtime for your function. For more information on runtimes configuration and lifecycle, refer to the [dedicated documentation](/serverless/functions/reference-content/functions-runtimes/).
+1. Select a runtime for your function. For more information on runtimes configuration and lifecycle, refer to the [dedicated documentation](/serverless-functions/reference-content/functions-runtimes/).
 
 2. Select a function code option:
 
@@ -53,7 +53,7 @@ This page shows you how to deploy a [function](/serverless-functions/concepts/#f
 
 2. Configure the **scaling** of your function.
     <Message type="tip">
-      Define a minimum of **one instance** or more to avoid [cold starts](/serverless/functions/concepts/#cold-start).
+      Define a minimum of **one instance** or more to avoid [cold starts](/serverless-functions/concepts/#cold-start).
     </Message>
 
 ### Function advanced options (optional)