diff --git a/website/content/docs/concepts/host-discovery/aws.mdx b/website/content/docs/concepts/host-discovery/aws.mdx
index 96e342d763..ca819f8530 100644
--- a/website/content/docs/concepts/host-discovery/aws.mdx
+++ b/website/content/docs/concepts/host-discovery/aws.mdx
@@ -15,10 +15,10 @@ fields needed for Boundary to authenticate with AWS.
 
 Boundary supports two methods of authenticating to AWS:
 
-1. **Static credentials** using an IAM user and its access key.
-1. **Dynamic credentials** using credentials generated by `AssumeRole`.
+1. **Static credentials** using an IAM user and its access key
+1. **Dynamic credentials** using credentials generated by `AssumeRole`
 
-HashiCorp recommends using dynamic credentials when possible. Select a credential type to continue.
+HashiCorp recommends using dynamic credentials when possible. Select a credential type to continue:
 
 <Tabs>
 <Tab heading="Static credentials" group="static">
@@ -74,7 +74,7 @@ To enable allow for static credential rotation, add the `iam:GetUser`, `iam:Crea
 
 </Note>
 
-To set up a dynamic host catalog using an AWS role, a self-managed worker must assume the role. You must assign the role to the self-managed worker AWS instance, and then supply a worker filter that matches the AWS worker when setting up the dynamic host catalog.
+To set up a dynamic host catalog using an AWS role, a self-managed worker must assume the role. You must assign the role to the self-managed worker AWS instance, and then supply a worker filter that matches the AWS worker when you set up the dynamic host catalog.
 
 Perform the following steps to set up a host catalog using [AssumeRole](https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html):