diff --git a/docs/docs-content/user-management/palette-rbac/assign-a-role.md b/docs/docs-content/user-management/palette-rbac/assign-a-role.md
index faab2155ff..5a0df5b242 100644
--- a/docs/docs-content/user-management/palette-rbac/assign-a-role.md
+++ b/docs/docs-content/user-management/palette-rbac/assign-a-role.md
@@ -156,8 +156,8 @@ Use the following steps to remove a role from a user.
 1. Have the user log in to [Palette](https://console.spectrocloud.com). If a self-hosted Palette instance is used, have
    the user log in to Palette using the instance URL.
 
-2. Verify that the user can no longer access the resources and perform the actions associated with the removed role in the projects
-   you assigned them to.
+2. Verify that the user can no longer access the resources and perform the actions associated with the removed role in
+   the projects you assigned them to.
 
 ## Remove a Role From a Team
 
@@ -194,5 +194,5 @@ Use the following steps to remove a role from a team.
 1. Have a member of the team log in to [Palette](https://console.spectrocloud.com). If a self-hosted Palette instance is
    used, have the team member log in to Palette using the instance URL.
 
-2. Verify that the team member can no longer access the resources and perform the actions associated with the removed role in the
-   projects you assigned them to.
+2. Verify that the team member can no longer access the resources and perform the actions associated with the removed
+   role in the projects you assigned them to.
diff --git a/docs/docs-content/user-management/palette-rbac/create-custom-role.md b/docs/docs-content/user-management/palette-rbac/create-custom-role.md
index 118d0bd1bb..dc696689bb 100644
--- a/docs/docs-content/user-management/palette-rbac/create-custom-role.md
+++ b/docs/docs-content/user-management/palette-rbac/create-custom-role.md
@@ -8,8 +8,8 @@ sidebar_position: 5
 tags: ["user-management", "role", "rbac"]
 ---
 
-For each role type in Palette, you can create a custom role with specific permissions. This allows you to create
-roles that are tailored to your organization's needs.
+For each role type in Palette, you can create a custom role with specific permissions. This allows you to create roles
+that are tailored to your organization's needs.
 
 :::tip
 
diff --git a/docs/docs-content/user-management/palette-rbac/palette-rbac.md b/docs/docs-content/user-management/palette-rbac/palette-rbac.md
index 1016303ab2..f6d0ce27d4 100644
--- a/docs/docs-content/user-management/palette-rbac/palette-rbac.md
+++ b/docs/docs-content/user-management/palette-rbac/palette-rbac.md
@@ -51,14 +51,14 @@ tenant scope can conduct actions across all projects within the tenant.
 :::info
 
 Self-hosted Palette and VerteX instances have an additional scope called the System Scope. The system scope applies to
-the entire system. Only users with the system
-administrator role can perform actions in the system scope. System administrator access is only available to self-hosted
-instances.
+the entire system. Only users with the system administrator role can perform actions in the system scope. System
+administrator access is only available to self-hosted instances.
 
 :::
 
 Scopes are organized hierarchically, with each level becoming more specific. Roles can be assigned at different scope
-levels, and the level you choose determines the role's range of influence. Use the scope to control the visibility of resources and to reduce the number of resources a role has access to.
+levels, and the level you choose determines the role's range of influence. Use the scope to control the visibility of
+resources and to reduce the number of resources a role has access to.
 
 ![palette-rbac-scope.webp](/user-management_palette-rbac_palette-rbac_scope-overview.webp)
 
@@ -70,8 +70,8 @@ Key points to remember about scopes:
 
 - Resource isolation is achieved by creating resources in the lower scope.
 
-- Resources with the same name may co-exist across different project scopes and will be distinguished with a scope icon in the context
-  column.
+- Resources with the same name may co-exist across different project scopes and will be distinguished with a scope icon
+  in the context column.
 
 - In Terraform, when using the Spectro Cloud provider, the term context is used instead of scope. Refer to the
   [Spectro Cloud provider](https://registry.terraform.io/providers/spectrocloud/spectrocloud/latest/docs) for more
@@ -146,8 +146,8 @@ cluster profiles that have the tag `prodAllowed`.
 
 :::info
 
-In the example provided, assume the user with the Resource role assigned has other permissions required to view
-projects and list cluster profiles. For brevity, these permissions are not listed.
+In the example provided, assume the user with the Resource role assigned has other permissions required to view projects
+and list cluster profiles. For brevity, these permissions are not listed.
 
 :::