diff --git a/changelog/2026-06-29-browser-extension-0-13-0.mdx b/changelog/2026-06-29-browser-extension-0-13-0.mdx
index 3debfadb..ac51204e 100644
--- a/changelog/2026-06-29-browser-extension-0-13-0.mdx
+++ b/changelog/2026-06-29-browser-extension-0-13-0.mdx
@@ -1,9 +1,9 @@
 ---
-title: "Browser Extension : Performance and bug fixes"
+title: "Browser Extension: Performance and bug fixes"
 description: "The Trunk browser extension 0.13.0 ships performance improvements and bug fixes."
-date: "null"
-category: "Browser Extension"
-type: "update"
+date: 2026-06-29
+category: Browser Extension
+type: update
 ---
 
 **Version 0.13.0 of the Trunk browser extension is now available with performance improvements and bug fixes.**
diff --git a/docs.json b/docs.json
index 641ccd6e..37e3fce6 100644
--- a/docs.json
+++ b/docs.json
@@ -624,7 +624,7 @@
               {
                 "group": "June",
                 "pages": [
-                  "changelog/2026-06-29-browser-extension-0-13-0.mdx",
+                  "changelog/2026-06-29-browser-extension-0-13-0",
                   "changelog/2026-06-18-merge-queue-stale-tab-refresh-fix",
                   "changelog/2026-06-17-flaky-tests-browser-extension-failure-details",
                   "changelog/2026-06-17-merge-queue-metrics-and-extension-updates",
diff --git a/flaky-tests/get-started/ci-providers/github-actions.mdx b/flaky-tests/get-started/ci-providers/github-actions.mdx
index 015edba4..9e69bef9 100644
--- a/flaky-tests/get-started/ci-providers/github-actions.mdx
+++ b/flaky-tests/get-started/ci-providers/github-actions.mdx
@@ -132,7 +132,7 @@ You can quarantine flaky tests by wrapping the test command or as a follow-up st
 <Tabs>
 <Tab title="GitHub Actions Workflow">
 <Note>
-Using the Trunk Analytics Uploader Action in your GitHub Actions Workflow files, may need modifications to your workflow files to support quarantining.
+Using the Trunk Analytics Uploader Action in your GitHub Actions Workflow files may need modifications to your workflow files to support quarantining.
 
 If you upload your test results as a second step after you run your tests, **you need to add** `continue-on-error: true` **on your test step so your CI** job will continue even on failures.
 </Note>
diff --git a/merge-queue/getting-started/configure-branch-protection.mdx b/merge-queue/getting-started/configure-branch-protection.mdx
index 273291ef..1b7be8c4 100644
--- a/merge-queue/getting-started/configure-branch-protection.mdx
+++ b/merge-queue/getting-started/configure-branch-protection.mdx
@@ -42,7 +42,7 @@ When a pull request enters the queue, Trunk creates a draft pull request to test
 Things to look out for:
 
 * This mode also creates a `trunk-merge/` branch
-* Trunk automatically closes the draft PRs and merge the original PRs
+* Trunk automatically closes the draft PRs and merges the original PRs
 
 **When to use a different approach:** If you have expensive preview deployments, review-only workflows, or security scans that you don't want running during merge queue testing, consider Push-triggered mode instead.