docs: automated nav-standard formatting fixes

changelog/2026-05-18-flaky-tests-fork-pr-uploads.mdx

@@ -8,7 +8,7 @@ type: new-feature
 
 **You can now accept test result uploads from fork pull requests without exposing your organization API token to fork workflows.**
 
-Fork PRs are a long-standing gap for open-source repos: GitHub doesn't pass repository secrets to workflows triggered by `pull_request` from a fork, so the analytics CLI has no org token to authenticate with, and those contributors lose flake detection. The new **Fork PR Uploads** toggle at **Settings > Repositories > [repo] > Flaky Tests** closes that gap. Enabling it mints a non-secret, 8-character public repo identifier that fork workflows send on the `X-Trunk-Public-Repo-Id` header instead of a token.
+Fork PRs are a long-standing gap for open-source repos: GitHub doesn't pass repository secrets to workflows triggered by `pull_request` from a fork, so the analytics CLI has no org token to authenticate with, and those contributors lose flake detection. The new **Fork PR Uploads** toggle at **Settings** → **Repositories** → **[repo]** → **Flaky Tests** closes that gap. Enabling it mints a non-secret, 8-character public repo identifier that fork workflows send on the `X-Trunk-Public-Repo-Id` header instead of a token.
 
 The identifier is a routing key, not a credential: it tells Trunk which repository an upload belongs to and only authorizes uploads to that repository. Fork PR uploads are opt-in per repository, and toggling the setting is admin-only.
 

changelog/2026-06-08-flaky-tests-monitor-history-swimlane.mdx

@@ -17,4 +17,4 @@ Additional controls make it easier to focus on what matters:
 
 The swimlane sits above the monitors table on the Monitors tab, giving you a timeline-first view before drilling into per-monitor event counts.
 
-[Open any test case](https://app.trunk.io) and go to the **Monitors** tab to see the swimlane.
+[Open any test case](https://app.trunk.io) and open the **Monitors** tab to see the swimlane.

changelog/2026-06-09-flaky-tests-multiple-por-monitors.mdx

@@ -16,6 +16,6 @@ Common uses:
 - **Different actions by scope.** Classify tests as flaky on stable branches while only applying labels on PR branches.
 - **Targeted detection.** Scope one monitor tightly to a branch pattern where pass-on-retry noise is high, while leaving a broader monitor in place for everything else.
 
-To add a monitor, go to **Settings** in the Trunk web app, open the repository, and navigate to the **Monitors** tab. Each monitor appears as a separate row and can be individually enabled, disabled, or deleted.
+To add a monitor, navigate to **Settings** in the Trunk web app, open the repository, and open the **Monitors** tab. Each monitor appears as a separate row and can be individually enabled, disabled, or deleted.
 
 [Read the docs](https://docs.trunk.io/flaky-tests/detection/pass-on-retry-monitor) to learn more.

changelog/2026-06-10-merge-queue-state-labels-setting.mdx

@@ -10,7 +10,7 @@ type: update
 
 A new **State Labels** toggle in Merge Queue Settings controls whether Trunk applies labels to pull requests as they move through the queue. When enabled, PRs receive labels such as `trunk:queued`, `trunk:testing`, and `trunk:failed` that are visible directly in GitHub's pull request list without opening the Trunk dashboard.
 
-- **Disabled by default.** Enable the toggle in **Merge Queue** -> **[your repository]** -> **Settings** -> **State Labels**.
+- **Disabled by default.** Enable the toggle in **Merge Queue** → **[your repository]** → **Settings** → **State Labels**.
 - **Admin-only.** Only organization admins can change this setting.
 
 See [State Labels](https://docs.trunk.io/merge-queue/administration/advanced-settings#state-labels) in the settings reference for details.

flaky-tests/detection/pass-on-retry-monitor.mdx

@@ -49,7 +49,7 @@ You can create more than one pass-on-retry monitor for the same repository. Each
 
 A common pattern is to run one monitor scoped to stable branches (like `main`) with a shorter recovery period for fast feedback, and a second monitor scoped to `release/*` branches with a longer recovery period for builds where intermittent failures are more expensive to re-investigate.
 
-To add a monitor, go to **Settings** in the Trunk web app, open the repository, navigate to the **Monitors** tab, and click **Add monitor**. Each monitor you create appears as a separate row in the monitors table and can be individually enabled, disabled, or deleted.
+To add a monitor, navigate to **Settings** in the Trunk web app, open the repository, open the **Monitors** tab, and click **Add monitor**. Each monitor you create appears as a separate row in the monitors table and can be individually enabled, disabled, or deleted.
 
 ### What Recovery Days Controls