Apply suggestions from code review

Co-authored-by: Rowena Jones <[email protected]>

Author: bene2k1

menu/navigation.json

@@ -2000,7 +2000,7 @@
                     "slug": "exposing-services"
                   },
                   {
-                    "label": "Setting IAM permissions and implement RBAC on a cluster",
+                    "label": "Setting IAM permissions and implementing RBAC on a cluster",
                     "slug": "set-iam-permissions-and-implement-rbac"
                   },
                   {

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

@@ -1,9 +1,9 @@
 ---
 meta:
-  title: Setting IAM permissions and implement RBAC on a cluster
+  title: Setting IAM permissions and implementing RBAC on a cluster
   description: This page explains how to set IAM permissions and implement RBAC on a Scaleway Kubernetes cluster
 content:
-  h1: Setting IAM permissions and implement RBAC on a cluster
+  h1: Setting IAM permissions and implementing RBAC on a cluster
   paragraph: This page explains how to set IAM permissions and implement RBAC on a Scaleway Kubernetes cluster
 tags: kubernetes kapsule-cluser
 dates:
@@ -14,15 +14,15 @@ categories:
 ---
 
 Role-based access control (RBAC) is a native feature of Kubernetes and a method of regulating access to compute or network resources based on the roles of individual users within your Organization.
-The feature is activated on Scaleway Kubernetes Kapsule and Kosmos by default and is compatible with Scaleway's IAM service.
-IAM and RBAC work together by integrating Scaleway’s Identity and Access Management with Kubernetes' native RBAC system. This integration ensures that access permissions are consistent across both the cloud infrastructure and the Kubernetes cluster, providing a secure access control mechanism.
+The feature is activated on Scaleway Kubernetes Kapsule and Kosmos by default and is compatible with Scaleway's Identity and Access Management (IAM) service.
+IAM and RBAC work together by integrating Scaleway’s IAM with Kubernetes' native RBAC system. This integration ensures that access permissions are consistent across both the cloud infrastructure and the Kubernetes cluster, providing a secure access control mechanism.
 It allows you to assign roles to users, groups or `ServicesAccount` via `RoleBindings` and `ClusterRoleBindings`.
 
 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).
-   - `ClusterRoles`: These are similar to roles but apply cluster-wide, spanning across all namespaces.
+   - `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.
    - `ClusterRoleBindings`: These associate a set of permissions defined in a ClusterRole with a user, group, or service account across the entire cluster.
@@ -77,7 +77,7 @@ Groups      [scaleway:group:55eb7ac5-9afe-4e40-8d54-4fbb232cac21 scaleway:cluste
    - Note the group ID, as it will be needed later.
 
 2. Create namespaces and roles:
-   As a user/app with `KubernetesFullAccess` or `KubernetesSystemMastersGroupAccess`, create the following manifests:
+   As a user or application with `KubernetesFullAccess` or `KubernetesSystemMastersGroupAccess`, create the following manifests:
 
     Namespace creation:
 
@@ -128,7 +128,7 @@ Groups      [scaleway:group:55eb7ac5-9afe-4e40-8d54-4fbb232cac21 scaleway:cluste
 
     Repeat the same operation for the staging namespace.
 
-3. Apply the Manifests:
+3. Apply the manifests:
     ```bash
     kubectl apply -f filename.yaml
     ```
@@ -137,9 +137,9 @@ After these steps, members of the IAM group will have read access to the cluster
 
 ## Assigning permissions to a specific user without using a group
 
-1. Assign the `KubernetesReadOnly` Permission Set to the User.
+1. Assign the `KubernetesReadOnly` Permission Set to the user.
 2. Retrieve the **IAM user ID** and note it.
-3. Create the following Manifests:
+3. Create the following manifests:
 
     Namespace creation:
 
@@ -191,7 +191,7 @@ After these steps, members of the IAM group will have read access to the cluster
 
     The user "demo" now has full rights in the `example-sandbox` namespace.
 
-## Limiting cluster-read Access
+## Limiting cluster-read access
 
 To modify the `scaleway:cluster-read` permissions, use the following command: