Fix spelling errors found in the documentation (#1073)

website/content/docs/api-clients/api.mdx

@@ -7,7 +7,7 @@ description: |-
 
 # API
 
-Boundary's API is a a JSON-based HTTP API that adheres to a set of standards that are rigidly followed. At its core, it is a standards-compliant JSON API for both input and output.
+Boundary's API is a JSON-based HTTP API that adheres to a set of standards that are rigidly followed. At its core, it is a standards-compliant JSON API for both input and output.
 
 Before reading this page, it is useful to understand Boundary's [domain model](/docs/concepts/domain-model) to be aware of the terminology used here.
 
@@ -64,7 +64,7 @@ The following method conventions are used within Boundary's API:
 
 ### POST
 
-`POST` is used for creating a resource or performing custom actions against a resoruce. When creating a resource, `POST` is used against a collection (`/roles`). When performing a custom action, `POST` is used against a particular resource (`/roles/r_1234567890:set-principals`).
+`POST` is used for creating a resource or performing custom actions against a resource. When creating a resource, `POST` is used against a collection (`/roles`). When performing a custom action, `POST` is used against a particular resource (`/roles/r_1234567890:set-principals`).
 
 ### PATCH
 

website/content/docs/api-clients/cli.mdx

@@ -8,7 +8,7 @@ description: |-
 # CLI
 
 Boundary's CLI has predictable behavior throughout its various commands. This
-page details the common patterns in used in order to help users make better use
+page details the common patterns used in order to help users make better use
 of the CLI.
 
 ## Completion