feat(rbac): clean up

Signed-off-by: Oleksandr Andriienko <[email protected]>

Author: AndrienkoAleksandr

plugins/rbac-backend/docs/conditions.md

@@ -293,29 +293,30 @@ The RBAC-backend plugin allows for the use of aliases in the conditional policy
 
 This condition should allow members of the `role:default/developer` to delete only their own catalogs and no others:
 
-````json
+```json
 {
   "result": "CONDITIONAL",
   "roleEntityRef": "role:default/developer",
   "pluginId": "catalog",
   "resourceType": "catalog-entity",
   "permissionMapping": ["delete"],
   "conditions": {
-     "rule": "IS_ENTITY_OWNER",
-     "resourceType": "catalog-entity",
-     "params": {
-       "claims": ["$currentUser"]
-     }
-   }
+    "rule": "IS_ENTITY_OWNER",
+    "resourceType": "catalog-entity",
+    "params": {
+      "claims": ["$currentUser"]
+    }
+  }
 }
+```
 
 ## Examples of Conditional Policies
 
 Below are a few examples that can be used on some of the Janus IDP plugins. These can help in determining how based to define conditional policies
 
 ### Keycloak plugin
 
-```JSON
+```json
 {
   "result": "CONDITIONAL",
   "roleEntityRef": "role:default/developer",
@@ -330,15 +331,15 @@ Below are a few examples that can be used on some of the Janus IDP plugins. Thes
     }
   }
 }
-````
+```
 
 This example will prevent users in the role `role:default/developer` from updating or deleting users that ingested into the catalog from the Keycloak plugin.
 
 Notice the use of the annotation `keycloak.org/realm` requires the value of `<YOUR_REALM>`
 
 ### Quay Actions
 
-```JSON
+```json
 {
   "result": "CONDITIONAL",
   "roleEntityRef": "role:default/developer",