Update Orchestrator plugin permissions

Author: GitHub Actions

modules/orchestrator/proc-managing-orchestrator-plugin-permissions-using-rbac-policies.adoc

@@ -46,7 +46,7 @@ p, role:default/workflowAdmin, orchestrator.instanceAdminView, read, allow
 # Assign users to the roles
 g, user:default/example_user, role:default/workflowUser
 ----
-. In your {product-very-short} `{my-app-config-file}` file, enable permissions by adding the `orchestrator` plugin to the `rbac` section and setting `policyFileReload` to true.
+. In your {product-very-short} `{my-app-config-file}` file, enable permissions by adding the `orchestrator` plugin to the `rbac` section and setting `policyFileReload` to `true`.
 +
 [source,yaml,subs="+attributes,+quotes"]
 ----

modules/orchestrator/ref-orchestrator-plugin-permissions.adoc

@@ -3,8 +3,7 @@
 [id="ref-orchestrator-plugin-permissions_{context}"]
 = Orchestrator plugin permissions
 
-The Orchestrator plugin uses the {product} permission mechanism and the Role-Based Access Control (RBAC) plugin to restrict access to backend endpoints.
-Orchestrator supports decoupling visibility (read) from running (update) using specific workflow IDs instead of generic permissions.
+The Orchestrator plugin uses the {product} permission mechanism and the Role-Based Access Control (RBAC) plugin to restrict access to backend endpoints. Orchestrator supports decoupling visibility (read) from running (update) using specific workflow IDs instead of generic permissions.
 
 [cols="20%,15%,15,50%", frame="all", options="header"]
 |===