Apply batch suggestions from code review

Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com>

website/content/docs/configuration/identity-access-management/index.mdx

@@ -2,7 +2,7 @@
 layout: docs
 page_title: Permissions index
 description: >-
-  Learn about Boundary's RBAC, allow-only permissions model. Understand how permissions are configured using grant strings and roles.
+  Learn about Boundary's RBAC (Role-based access control), allow-only permissions model. Understand how permissions are configured using grant strings and roles.
 ---
 
 # Permissions in Boundary

website/content/docs/configuration/identity-access-management/permission-grant-formats.mdx

@@ -2,7 +2,7 @@
 layout: docs
 page_title: Permission grant formats
 description: >-
-  Learn how to construct grant strings that map resources and permissions. Understand ID, Type, Pinned, and Wildcard grant formats.View possible grant templates.
+  Learn how to construct grant strings that map resources and permissions. Understand ID, Type, Pinned, and Wildcard grant formats. View possible grant templates.
 ---
 
 # Permission grant formats

website/content/docs/configuration/session-recording/enable-session-recording.mdx

@@ -2,7 +2,7 @@
 layout: docs
 page_title: Enable session recording on a target
 description: >-
-  Enable session recording for targets so that any user sessions connecting to them are recorded for compliance and threat management.
+  Enable session recording for targets so that user sessions are recorded for compliance and threat management.
 ---
 
 # Enable session recording on a target

website/content/docs/configuration/session-recording/storage-providers/configure-minio.mdx

@@ -1,7 +1,7 @@
 ---
 layout: docs
 page_title: Configure MinIO storage
-description: |-
+description: >-
   Configure MinIO as a storage provider for recorded sessions. Understand session recording and MinIO requirements. View an example configuration.
 ---
 

website/content/docs/configuration/worker/index.mdx

@@ -11,14 +11,14 @@ The `worker` stanza configures Boundary worker-specific parameters.
 
 All workers within Boundary use certificates and encryption keys to identify
 themselves and protect data in transit. However, there are three different
-ways to register them so that registration of workers can fit into any workflow; controller-led, worker-led, and via external KMS.
+ways to register them so that registration of workers can fit into any workflow: controller-led, worker-led, and via external KMS.
 
 The differences in how they are configured are in the sub-pages linked at the
 bottom of this page.
 
-Workers registered via the worker-led or controller-led methods must be registered in
-the system via an API call, and require storage on disk to store the current set
-of credentials. Workers registering via an external KMS auto-register after successful authentication, making them an easy mechanism to
+Workers registered using the worker-led or controller-led methods must be registered in
+the system using an API call, and require storage on disk to store the current set
+of credentials. Workers registering using an external KMS auto-register after successful authentication, making them an easy mechanism to
 use for automatic scaling. This also means they are not required to store
 credentials locally; each time they connect the KMS is used to reauthenticate
 them.

website/content/docs/configuration/worker/worker-configuration.mdx

@@ -2,7 +2,7 @@
 layout: docs
 page_title: Worker configuration
 description: >-
-  Learn about authorizing workers to the cluster and configuring workers for session recording storage. View a complete worker configuration example.
+  Learn about authorizing workers to the controller and configuring workers for session recording storage. View a complete worker configuration example.
 ---
 
 # Worker configuration