feat(k8s): update docs kubectl

Author: bene2k1

containers/kubernetes/how-to/connect-cluster-kubectl.mdx

@@ -15,13 +15,12 @@ categories:
 
 Once your [cluster is created](/containers/kubernetes/how-to/create-cluster/), you can install a `kubeconfig` file unsing Scaleway's command-line tool on your local machine to manage your Kubernetes cluster.
 
-You can use this with `kubectl`, the Kubernetes command-line tool, to run commands against your Kubernetes cluster. This enables you to deploy applications, inspect and manage cluster resources, and view logs directly from your local machine.
-
+You can use this with `kubectl`, the Kubernetes command-line tool, allowing you to run commands against your Kubernetes cluster. This enables you to deploy applications, inspect and manage cluster resources, and view logs directly from your local machine.
 <Macro id="requirements" />
 
 - A [Scaleway account](https://console.scaleway.com) logged into the console.
 - [Owner status](https://console.scaleway.com) or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) to perform actions in the intended Organization.
-- Created a [Kubernetes Kapsule cluster](/containers/kubernetes/how-to/create-cluster/)
+- Created a [Kubernetes Kapsule cluster](/containers/kubernetes/how-to/create-cluster/).
 - [kubectl](https://kubernetes.io/docs/tasks/tools/) installed locally.
 - The [Scaleway CLI](/developer-tools/scaleway-cli/quickstart/) installed locally.
 
@@ -44,8 +43,9 @@ To create a new policy with the correct permission sets, follow these steps:
      - `KubernetesFullAccess` for full cluster management.
      - `KubernetesReadOnly` for read-only access.
 4. Click **Validate** and then **Create Policy**.
-
-Refer to our [policy and permission sets documentation](/identity-and-access-management/iam/reference-content/permission-sets/) for more details.
+    <Message type="tip">
+      Refer to our [policy and permission sets documentation](/identity-and-access-management/iam/reference-content/permission-sets/) for more details.
+    </Message>
 
 ## Accessing the cluster
 
@@ -60,7 +60,8 @@ If you have not set up the Scaleway CLI yet:
    ```bash
    scw init
    ```
-   You will need your [API Key](https://identity-and-access-management/iam/how-to/#creating-API-keys) (access key and secret key).
+   You will need your [API Key](https://identity-and-access-management/iam/how-to/#creating-API-keys) (access key & secret key).
+
 
 ### Retrieve and install the kubeconfig using `scw`
 
@@ -70,10 +71,14 @@ If you have not set up the Scaleway CLI yet:
    ```
    This command will:
    - Download the `kubeconfig` for the specified cluster.
-   - Merge it into your existing kubeconfig file (default location: `~/.kube/config`).
+   - Merge it into your existing `kubeconfig` file (default location: `~/.kube/config`).
 
 2. Verify the installation:
    ```bash
    kubectl get nodes
    ```
    A list of nodes from your Kapsule cluster should appear. If not, review the troubleshooting section.
+
+<Message type="tip">
+  Refer to our complete [Documentation for `scw k8s`](https://github.com/scaleway/scaleway-cli/blob/master/docs/commands/k8s.md) to learn more about all available commands to manage your Kubernetes cluster using `scw`.
+</Message>