From 8389d7951973ffc6086e68bdc605b40f6d907e32 Mon Sep 17 00:00:00 2001 From: kazuto Date: Sun, 25 Oct 2026 17:03:37 +0900 Subject: [PATCH] docs: fix inconsistent casing in "See [...]" section links --- docs/config/fmt.md | 2 +- docs/config/lint.md | 2 +- docs/config/staged.md | 2 +- docs/guide/check.md | 2 +- docs/guide/create.md | 2 +- docs/guide/migrate.md | 6 +++--- docs/guide/troubleshooting.md | 2 +- 7 files changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/config/fmt.md b/docs/config/fmt.md index fbc1c2402a..435ad462bd 100644 --- a/docs/config/fmt.md +++ b/docs/config/fmt.md @@ -21,4 +21,4 @@ export default defineConfig({ For file- or package-specific formatting settings, use [`fmt.overrides`](/guide/monorepo#format-overrides) from the root `vite.config.ts`. -Oxfmt disables nested configs in Vite+ mode, so nested format configs do not override settings for individual files. See [troubleshooting](/guide/troubleshooting#nested-lint-or-format-config-is-not-applied) for details. +Oxfmt disables nested configs in Vite+ mode, so nested format configs do not override settings for individual files. See [Troubleshooting](/guide/troubleshooting#nested-lint-or-format-config-is-not-applied) for details. diff --git a/docs/config/lint.md b/docs/config/lint.md index 02bb85cb7c..7cff8b16bc 100644 --- a/docs/config/lint.md +++ b/docs/config/lint.md @@ -27,4 +27,4 @@ We recommend enabling both `options.typeAware` and `options.typeCheck` so `vp li For file- or package-specific lint rules, use [`lint.overrides`](/guide/monorepo#root-config-with-overrides) from the root `vite.config.ts`. -Oxlint disables nested configs in Vite+ mode, so nested lint configs do not override settings for individual files. See [troubleshooting](/guide/troubleshooting#nested-lint-or-format-config-is-not-applied) for details. +Oxlint disables nested configs in Vite+ mode, so nested lint configs do not override settings for individual files. See [Troubleshooting](/guide/troubleshooting#nested-lint-or-format-config-is-not-applied) for details. diff --git a/docs/config/staged.md b/docs/config/staged.md index 85c83bb089..f2c6f970b7 100644 --- a/docs/config/staged.md +++ b/docs/config/staged.md @@ -1,6 +1,6 @@ # Staged Config -`vp staged` reads staged-file rules from the `staged` block in `vite.config.ts`. See the [Commit hooks guide](/guide/commit-hooks). +`vp staged` reads staged-file rules from the `staged` block in `vite.config.ts`. See the [Commit Hooks](/guide/commit-hooks). ## Example diff --git a/docs/guide/check.md b/docs/guide/check.md index 4d08e42ee1..41397d3478 100644 --- a/docs/guide/check.md +++ b/docs/guide/check.md @@ -61,4 +61,4 @@ export default defineConfig({ }); ``` -These options only affect `vp check`; standalone `vp fmt` and `vp lint` still run normally. A step is skipped if it is disabled in config or the matching `--no-fmt` / `--no-lint` flag is passed. Because the defaults apply to every `vp check` run, a pre-commit hook that calls `vp check` will skip the disabled step too. See [Check config](/config/check) for the full reference. +These options only affect `vp check`; standalone `vp fmt` and `vp lint` still run normally. A step is skipped if it is disabled in config or the matching `--no-fmt` / `--no-lint` flag is passed. Because the defaults apply to every `vp check` run, a pre-commit hook that calls `vp check` will skip the disabled step too. See [Check Config](/config/check) for the full reference. diff --git a/docs/guide/create.md b/docs/guide/create.md index cf0f7499e4..1e3c258f74 100644 --- a/docs/guide/create.md +++ b/docs/guide/create.md @@ -95,7 +95,7 @@ Run `vp create --list` to see the built-in templates and the common shorthand te `--git` and `--no-git` are not available when adding a package to an existing monorepo. ::: -After create, manage the dispatcher with `vp hooks status`, `vp hooks disable`, and `vp hooks enable`. See the [Commit hooks guide](/guide/commit-hooks). +After create, manage the dispatcher with `vp hooks status`, `vp hooks disable`, and `vp hooks enable`. See the [Commit Hooks](/guide/commit-hooks). ### Dependency build scripts diff --git a/docs/guide/migrate.md b/docs/guide/migrate.md index fb2c37af05..ba33245053 100644 --- a/docs/guide/migrate.md +++ b/docs/guide/migrate.md @@ -234,11 +234,11 @@ export default defineConfig({ }); ``` -When no existing hook policy owns the workflow, `vp migrate` can move supported lint-staged rules and remove the old configuration and dependency. If an existing hook tool is preserved, keep lint-staged in place until you convert that hook policy manually. See the [Commit hooks guide](/guide/commit-hooks) and [Staged config reference](/config/staged) for details. +When no existing hook policy owns the workflow, `vp migrate` can move supported lint-staged rules and remove the old configuration and dependency. If an existing hook tool is preserved, keep lint-staged in place until you convert that hook policy manually. See the [Commit Hooks](/guide/commit-hooks) and [Staged Config](/config/staged) for details. ### Git hook tools -The `vp migrate` command does not automatically convert Husky setups. When Husky is detected, Vite+ leaves its hooks, lifecycle scripts, configuration, and dependencies unchanged and shows a warning. You can migrate the project manually using the [Commit hooks guide](/guide/commit-hooks). +The `vp migrate` command does not automatically convert Husky setups. When Husky is detected, Vite+ leaves its hooks, lifecycle scripts, configuration, and dependencies unchanged and shows a warning. You can migrate the project manually using the [Commit Hooks](/guide/commit-hooks). Existing project-owned Vite+ hooks are also preserved. The default staged workflow is introduced only when no existing hook policy is found. @@ -246,7 +246,7 @@ If your project currently uses `lefthook`, `simple-git-hooks`, or `yorkie`, `vp If you want to move one of those tools over to Vite+ manually, you can follow these steps. First, move your staged-file commands into the `staged` block within `vite.config.ts`. Then, update your lifecycle script so it runs `vp config`. You will also need to create a Vite+ hook at `.vite-hooks/pre-commit` that runs `vp staged`. Run `vp hooks enable` (or `vp config`) to install the dispatcher and set `core.hooksPath`. Finally, once you have confirmed that the Vite+ hook is working as expected, you can remove the old tool's configuration and dependency. -Use `vp hooks status` to verify the dispatcher is active, and `vp hooks disable` if you need to turn it off again in this clone. You can find more details about the full Vite+ hook setup in the [Commit hooks guide](/guide/commit-hooks). +Use `vp hooks status` to verify the dispatcher is active, and `vp hooks disable` if you need to turn it off again in this clone. You can find more details about the full Vite+ hook setup in the [Commit Hooks](/guide/commit-hooks). ## Examples diff --git a/docs/guide/troubleshooting.md b/docs/guide/troubleshooting.md index 9af2cb8475..7da1d862a6 100644 --- a/docs/guide/troubleshooting.md +++ b/docs/guide/troubleshooting.md @@ -72,7 +72,7 @@ If `vp staged` fails or your pre-commit hook does not run: - if status shows `Preference: disabled (local)`, re-enable with `vp hooks enable` - check whether hooks were skipped intentionally through `VP_GIT_HOOKS=0` -To stop hooks in this clone without deleting project policy files, run `vp hooks disable`. See the [Commit hooks guide](/guide/commit-hooks) for the full workflow. +To stop hooks in this clone without deleting project policy files, run `vp hooks disable`. See the [Commit Hooks](/guide/commit-hooks) for the full workflow. A minimal staged config looks like this: