diff --git a/blueprints/staging-prod-isolation.html.md b/blueprints/staging-prod-isolation.html.md
index 982d2658c3..8e40e08f25 100644
--- a/blueprints/staging-prod-isolation.html.md
+++ b/blueprints/staging-prod-isolation.html.md
@@ -17,7 +17,7 @@ All Fly.io accounts start with a "personal" organization. You can create as many
 
 Before you create a new organization, here's what you need to know:
 
-- You can consolidate billing for multiple organizations under a a single parent organization, or you can create regular organizations with separate payment methods and billing. Learn more about [unified billing](/docs/about/billing/#unified-billing).
+- You can consolidate billing for multiple organizations under a single parent organization, or you can create regular organizations with separate payment methods and billing. Learn more about [unified billing](/docs/about/billing/#unified-billing).
 - You invite or remove members in each organization separately.
 - An organization can have multiple apps and those apps can communicate with each other securely over the org's private network.
 
diff --git a/js/prisma/postgres.html.md b/js/prisma/postgres.html.md
index 5a6a67ccda..8bf2c33d96 100644
--- a/js/prisma/postgres.html.md
+++ b/js/prisma/postgres.html.md
@@ -57,7 +57,7 @@ npx prisma migrate dev --name init
 
 Remove the `[processes]` and `[mounts]` sections from the `fly.toml` and add the `[deploy]` section you see above.
 
-Download your existing SQLite database and use [pgloader](https://pgloader.readthedocs.io/en/latest/ref/sqlite.html) to covert it to to postgres:
+Download your existing SQLite database and use [pgloader](https://pgloader.readthedocs.io/en/latest/ref/sqlite.html) to covert it to postgres:
 
 ```bash
 fly sftp get /data/dev.db
diff --git a/js/prisma/sqlite.html.md b/js/prisma/sqlite.html.md
index 70a395ac13..f740ddf351 100644
--- a/js/prisma/sqlite.html.md
+++ b/js/prisma/sqlite.html.md
@@ -121,7 +121,7 @@ Depending on whether or not we generate a `Dockerfile` for you, an `ENTRYPOINT`
 * Restore your database from LiteStream if it doesn't currently exist.
 * Run database migrations
 * Run your seed command if the database doesn't exist
-* Run [`litestream replicate`](https://litestream.io/reference/replicate/) to to monitor & continuously replicate SQLite database.
+* Run [`litestream replicate`](https://litestream.io/reference/replicate/) to monitor & continuously replicate SQLite database.
 * Launch your application
 
 Depending on your application and what framework it uses, this script may perform other functions.
diff --git a/reference/extensions_api.html.md b/reference/extensions_api.html.md
index 1f6dd5113b..8a373813c5 100644
--- a/reference/extensions_api.html.md
+++ b/reference/extensions_api.html.md
@@ -115,7 +115,7 @@ These parameters are sent with every provisioning request.
 | **read_regions** | array | An array of Fly.io region codes where read replicas should be provisioned | `["mad", "ord"]` |
 | **ip_address** | string | An IPv6 address on the customer network assigned to this extension | `fdaa:0:47fb:0:1::1d` |
 
-Your response should must contain a list of key/value pairs of secrets that that should be set on the associated Fly.io application. These secrets are available as environment variables. They aren't visible outside of an application VM.
+Your response must contain a list of key/value pairs of secrets that should be set on the associated Fly.io application. These secrets are available as environment variables. They aren't visible outside of an application VM.
 
 If your service is deployed on Fly, the response should also contain details about the target Fly.io application for the private IP address. See the following section for details about this.