diff --git a/packages/docs/docs/getting-started/quickstart.md b/packages/docs/docs/getting-started/quickstart.md
index b6627b5..b0c1de3 100644
--- a/packages/docs/docs/getting-started/quickstart.md
+++ b/packages/docs/docs/getting-started/quickstart.md
@@ -49,9 +49,7 @@ For custom query logic, attach a [Lua script](../guides/scripting.md).
 
 ## Next steps
 
-Here's where to go from here:
-
-- [**Statusphere tutorial**](../tutorials/statusphere.md): end-to-end walkthrough building a complete AppView with record, query, and procedure lexicons
+- [**Statusphere tutorial**](../tutorials/statusphere.md): full walkthrough building a complete AppView with record, query, and procedure lexicons
 - [**Lexicons guide**](../guides/lexicons.md): target collections, backfill flag, network lexicons
 - [**Lua Scripting**](../guides/scripting.md): custom query and procedure logic
 - [**Configuration**](configuration.md): environment variables and tuning
diff --git a/packages/docs/docs/guides/backfill.md b/packages/docs/docs/guides/backfill.md
index 062d2ec..746aab8 100644
--- a/packages/docs/docs/guides/backfill.md
+++ b/packages/docs/docs/guides/backfill.md
@@ -19,7 +19,7 @@ See the [admin API](../reference/admin/backfill.md) for endpoint details.
 
 ## Job lifecycle
 
-A backfill job moves through `pending → running → completed` (or `failed`). Unlike earlier versions of HappyView that relied on Tap, the job is only marked `completed` once every discovered repo has been processed end-to-end — there is no separate downstream queue. Progress is visible in real time on the dashboard's Backfill page.
+A backfill job moves through `pending → running → completed` (or `failed`). Unlike earlier versions of HappyView that relied on Tap, the job is only marked `completed` once every discovered repo has been fully processed — there is no separate downstream queue. Progress is visible in real time on the dashboard's Backfill page.
 
 If a job fails midway, the `error` field contains the failure reason. Re-running the backfill resumes from scratch but is idempotent (records are upserted by URI).
 
diff --git a/packages/docs/docs/reference/scripts/paginated-list.md b/packages/docs/docs/reference/scripts/paginated-list.md
index 5a54b64..cdf6358 100644
--- a/packages/docs/docs/reference/scripts/paginated-list.md
+++ b/packages/docs/docs/reference/scripts/paginated-list.md
@@ -37,4 +37,4 @@ GET /xrpc/xyz.statusphere.listStatuses?cursor=<opaque>&limit=20
 
 ## Use case
 
-A straightforward list endpoint for feeds, timelines, or browsing records by collection. The `cursor` value returned by `db.query` is an opaque string. Clients pass it back as the `cursor` parameter to fetch the next page — don't parse or modify it.
+A list endpoint for feeds, timelines, or browsing records by collection. The `cursor` value returned by `db.query` is an opaque string. Clients pass it back as the `cursor` parameter to fetch the next page — don't parse or modify it.
diff --git a/packages/docs/docs/tutorials/statusphere.md b/packages/docs/docs/tutorials/statusphere.md
index 3791471..daba446 100644
--- a/packages/docs/docs/tutorials/statusphere.md
+++ b/packages/docs/docs/tutorials/statusphere.md
@@ -108,7 +108,7 @@ curl "http://localhost:3000/xrpc/xyz.statusphere.listStatuses?limit=5" \
 
 See [XRPC API](../reference/xrpc-api.md) for the full default query behavior.
 
-## Step 4: Enhance the query with a Lua script
+## Step 4: Customize the query with a Lua script
 
 The default query behavior works, but let's customize it with a [Lua script](../guides/scripting.md). The script will handle single-record lookups by URI and paginated listing with an optional DID filter.
 
@@ -216,4 +216,4 @@ Everything was done through the dashboard — no server restarts, no config file
 - [XRPC API](../reference/xrpc-api.md): Understand how the generated endpoints behave
 - [Admin API](../reference/admin-api.md): Automate lexicon management via the API
 - [Statusphere example app](https://github.com/bluesky-social/statusphere-example-app): See the full Statusphere frontend
-- [ATProto Statusphere guide](https://atproto.com/guides/applications): Deep dive into how the app works at the protocol level
+- [ATProto Statusphere guide](https://atproto.com/guides/applications): How the app works at the protocol level