Apply suggestions from code review

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

Author: bene2k1

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

@@ -29,7 +29,7 @@ Key components of RBAC in Kubernetes include:
 - **Subjects:**  A subject in RBAC can be a user, a group, or a service account to which roles or cluster roles are bound.
 - **Rules:** Rules are sets of permissions associated with roles or cluster roles. They specify what actions are allowed or denied on specific resources.
 
-RBAC works seamlessly with Scaleway's IAM (Identity and Access Maanagement) system. [Identity and Access Management (IAM)](/iam/concepts/#iam) provides control over resource access. IAM policies enable the configuration of permissions for Kubernetes Kapsule clusters at the Project level.
+RBAC works seamlessly with Scaleway's IAM (Identity and Access Management) system. [Identity and Access Management (IAM)](/iam/concepts/#iam) provides control over resource access. IAM policies enable the configuration of permissions for Kubernetes Kapsule clusters at the Project level.
 
 An [IAM policy](/iam/concepts/#policy) defines the permissions for users, groups, and applications within an Organization. It consists of a [principal](/iam/concepts/#principal) (the user, group, or application to which it applies) and IAM rules that specify permission sets and their scope.
 
@@ -40,7 +40,7 @@ The combination of IAM and Kubernetes RBAC allows you to define fine-grained acc
 
 The following IAM permission sets are mapped to Kubernetes groups:
 
-| IAM Permission Set             | Kubernetes Group            | Notes                    |
+| IAM permission set             | Kubernetes group            | Notes                    |
 |----------------------------------|-----------------------------|--------------------------|
 | `KubernetesFullAccess`           | `scaleway:cluster-write`      |                          |
 |                                  | `scaleway:cluster-read`       |                          |
@@ -137,7 +137,7 @@ 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: