Skip to content
GitHub Actions / vale succeeded Aug 21, 2023 in 1s

reviewdog [vale] report

reported by reviewdog 🐶

Findings (0)
Filtered Findings (237)

docs/getting-started.md|19 col 91| [base.accessibilityVision] Don't use vision-based terms. Use something inclusive like 'visit', 'find', or 'check' instead of 'See'.
docs/contributing.md|7 col 4| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'you'd'
docs/commands/serve.md|19 col 97| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "production'
docs/commands/serve.md|19 col 99| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'production"'
docs/commands/serve.md|19 col 111| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "deploy'
docs/commands/serve.md|19 col 120| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'preview"'
docs/commands/serve.md|19 col 129| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "branch'
docs/commands/serve.md|19 col 138| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'deploy"'
docs/commands/serve.md|19 col 146| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "dev'
docs/commands/serve.md|19 col 148| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'dev"'
docs/commands/open.md|23 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/commands/api.md|21 col 3| [base.spelling] Spellcheck: did you really mean 'apiMethod'?
docs/commands/deploy.md|11 col 80| [base.spelling] Spellcheck: did you really mean 'lookups'?
docs/commands/deploy.md|33 col 94| [base.spelling] Spellcheck: did you really mean 'browserify'?
docs/commands/deploy.md|44 col 64| [base.spelling] Spellcheck: did you really mean 'node_modules'?
docs/commands/deploy.md|75 col 21| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'json's'
docs/commands/addons.md|7 col 5| [base.spelling] Spellcheck: did you really mean 'addons'?
docs/commands/addons.md|7 col 40| [base.spelling] Spellcheck: did you really mean 'addons'?
docs/commands/addons.md|9 col 33| [base.accessibilityVision] Don't use vision-based terms. Use something inclusive like 'visit', 'find', or 'check' instead of 'see'.
docs/commands/addons.md|27 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/commands/addons.md|79 col 17| [base.spelling] Spellcheck: did you really mean 'namespace'?
docs/commands/addons.md|100 col 17| [base.spelling] Spellcheck: did you really mean 'namespace'?
docs/commands/addons.md|121 col 17| [base.spelling] Spellcheck: did you really mean 'namespace'?
docs/commands/sites.md|23 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/commands/sites.md|42 col 26| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'isn't'
docs/commands/sites.md|107 col 3| [base.spelling] Spellcheck: did you really mean 'siteId'?
docs/commands/build.md|18 col 70| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "production'
docs/commands/build.md|18 col 72| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'production"'
docs/commands/build.md|18 col 84| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "deploy'
docs/commands/build.md|18 col 93| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'preview"'
docs/commands/build.md|18 col 102| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "branch'
docs/commands/build.md|18 col 111| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'deploy"'
docs/commands/build.md|18 col 119| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "dev'
docs/commands/build.md|18 col 121| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'dev"'
docs/commands/index.md|23 col 6| [base.spelling] Spellcheck: did you really mean 'addons'?
docs/commands/index.md|27 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/commands/index.md|48 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/commands/index.md|61 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/commands/index.md|66 col 6| [base.spelling] Spellcheck: did you really mean 'env'?
docs/commands/index.md|70 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/commands/index.md|84 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/commands/index.md|88 col 174| [base.spelling] Spellcheck: did you really mean 'Netlify's'?
docs/commands/index.md|88 col 174| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'Netlify's'
docs/commands/index.md|105 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/commands/index.md|107 col 51| [netlify-terms.featureCapitalization] This feature name is a proper noun. Use 'Large Media' instead of 'large media'.
docs/commands/index.md|120 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/commands/index.md|130 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/commands/index.md|143 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/commands/index.md|155 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/commands/completion.md|10 col 21| [base.accessibilityVision] Don't use vision-based terms. Use something inclusive like 'visit', 'find', or 'check' instead of 'see'.
docs/commands/completion.md|22 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/commands/env.md|22 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/commands/env.md|85 col 71| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "production'
docs/commands/env.md|85 col 73| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'production"'
docs/commands/env.md|85 col 85| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "deploy'
docs/commands/env.md|85 col 94| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'preview"'
docs/commands/env.md|85 col 103| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "branch'
docs/commands/env.md|85 col 112| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'deploy"'
docs/commands/env.md|85 col 120| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "dev'
docs/commands/env.md|85 col 122| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'dev"'
docs/commands/env.md|133 col 71| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "production'
docs/commands/env.md|133 col 73| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'production"'
docs/commands/env.md|133 col 85| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "deploy'
docs/commands/env.md|133 col 94| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'preview"'
docs/commands/env.md|133 col 103| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "branch'
docs/commands/env.md|133 col 112| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'deploy"'
docs/commands/env.md|133 col 120| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "dev'
docs/commands/env.md|133 col 122| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'dev"'
docs/commands/env.md|136 col 57| [base.spelling] Spellcheck: did you really mean 'plaintext'?
docs/commands/env.md|168 col 71| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "production'
docs/commands/env.md|168 col 73| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'production"'
docs/commands/env.md|168 col 85| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "deploy'
docs/commands/env.md|168 col 94| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'preview"'
docs/commands/env.md|168 col 103| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "branch'
docs/commands/env.md|168 col 112| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'deploy"'
docs/commands/env.md|168 col 120| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "dev'
docs/commands/env.md|168 col 122| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'dev"'
docs/commands/env.md|203 col 71| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "production'
docs/commands/env.md|203 col 73| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'production"'
docs/commands/env.md|203 col 85| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "deploy'
docs/commands/env.md|203 col 94| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'preview"'
docs/commands/env.md|203 col 103| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "branch'
docs/commands/env.md|203 col 112| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'deploy"'
docs/commands/env.md|203 col 120| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "dev'
docs/commands/env.md|203 col 122| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'dev"'
docs/commands/lm.md|11 col 37| [netlify-terms.featureCapitalization] This feature name is a proper noun. Use 'Large Media' instead of 'large media'.
docs/commands/lm.md|23 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/commands/lm.md|25 col 51| [netlify-terms.featureCapitalization] This feature name is a proper noun. Use 'Large Media' instead of 'large media'.
docs/commands/lm.md|41 col 6| [netlify-terms.featureCapitalization] This feature name is a proper noun. Use 'Large Media' instead of 'large media'.
docs/commands/link.md|20 col 65| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "origin'
docs/commands/link.md|20 col 67| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'origin"'
docs/commands/dev.md|10 col 50| [base.spelling] Spellcheck: did you really mean 'Netlify's'?
docs/commands/dev.md|10 col 50| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'Netlify's'
docs/commands/dev.md|21 col 97| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "production'
docs/commands/dev.md|21 col 99| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'production"'
docs/commands/dev.md|21 col 111| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "deploy'
docs/commands/dev.md|21 col 120| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'preview"'
docs/commands/dev.md|21 col 129| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "branch'
docs/commands/dev.md|21 col 138| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'deploy"'
docs/commands/dev.md|21 col 146| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "dev'
docs/commands/dev.md|21 col 148| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'dev"'
docs/commands/dev.md|38 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/commands/dev.md|61 col 62| [base.spelling] Spellcheck: did you really mean 'env'?
docs/commands/dev.md|61 col 95| [base.spelling] Spellcheck: did you really mean 'addons'?
docs/commands/dev.md|75 col 97| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "production'
docs/commands/dev.md|75 col 99| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'production"'
docs/commands/dev.md|75 col 111| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "deploy'
docs/commands/dev.md|75 col 120| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'preview"'
docs/commands/dev.md|75 col 129| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "branch'
docs/commands/dev.md|75 col 138| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'deploy"'
docs/commands/dev.md|75 col 146| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "dev'
docs/commands/dev.md|75 col 148| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'dev"'
docs/commands/functions.md|23 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/commands/functions.md|27 col 174| [base.spelling] Spellcheck: did you really mean 'Netlify's'?
docs/commands/functions.md|27 col 174| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'Netlify's'
docs/commands/functions.md|91 col 104| [base.spelling] Spellcheck: did you really mean 'Netlify's'?
docs/commands/functions.md|91 col 104| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'Netlify's'
docs/commands/functions.md|110 col 49| [base.spelling] Spellcheck: did you really mean 'stringified'?
docs/commands/functions.md|112 col 30| [base.spelling] Spellcheck: did you really mean 'Querystring'?
docs/commands/init.md|21 col 65| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "origin'
docs/commands/init.md|21 col 67| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'origin"'
docs/commands/status.md|22 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/functions-dev.md|8 col 106| [base.spelling] Spellcheck: did you really mean 'addons'?
docs/functions-dev.md|11 col 34| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'doesn't'
docs/functions-dev.md|44 col 112| [base.accessibilityVision] Don't use vision-based terms. Use something inclusive like 'visit', 'find', or 'check' instead of 'see'.
docs/vscode.md|7 col 46| [base.spelling] Spellcheck: did you really mean 'VScode'?
docs/vscode.md|24 col 8| [base.spelling] Spellcheck: did you really mean 'VSCode'?
docs/vscode.md|64 col 4| [base.accessibilityMouse] Don't use mouse-specific terms. Use something inclusive like 'select' instead of 'Click'.
docs/vscode.md|64 col 35| [base.spelling] Spellcheck: did you really mean 'VSCode'?
docs/vscode.md|64 col 62| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "Caught'
docs/vscode.md|64 col 71| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'Exceptions"'
docs/vscode.md|65 col 11| [base.accessibilityVision] Don't use vision-based terms. Use something inclusive like 'menu' instead of 'dropdown'.
docs/README.md|9 col 15| [base.accessibilityVision] Don't use vision-based terms. Use something inclusive like 'visit', 'find', or 'check' instead of 'see'.
docs/README.md|24 col 91| [base.accessibilityVision] Don't use vision-based terms. Use something inclusive like 'visit', 'find', or 'check' instead of 'See'.
docs/README.md|44 col 6| [base.spelling] Spellcheck: did you really mean 'addons'?
docs/README.md|48 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/README.md|69 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/README.md|82 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/README.md|87 col 6| [base.spelling] Spellcheck: did you really mean 'env'?
docs/README.md|91 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/README.md|105 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/README.md|109 col 174| [base.spelling] Spellcheck: did you really mean 'Netlify's'?
docs/README.md|109 col 174| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'Netlify's'
docs/README.md|126 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/README.md|128 col 51| [netlify-terms.featureCapitalization] This feature name is a proper noun. Use 'Large Media' instead of 'large media'.
docs/README.md|141 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/README.md|151 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/README.md|164 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/README.md|176 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
docs/netlify-dev.md|10 col 33| [base.spelling] Spellcheck: did you really mean 'Netlify's'?
docs/netlify-dev.md|10 col 33| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'Netlify's'
docs/netlify-dev.md|11 col 67| [base.spelling] Spellcheck: did you really mean 'Netlify's'?
docs/netlify-dev.md|11 col 67| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'Netlify's'
docs/netlify-dev.md|35 col 13| [base.spelling] Spellcheck: did you really mean 'config'?
docs/netlify-dev.md|48 col 75| [base.spelling] Spellcheck: did you really mean 'addons'?
docs/netlify-dev.md|63 col 2| [base.spelling] Spellcheck: did you really mean 'zsh'?
docs/netlify-dev.md|64 col 2| [base.spelling] Spellcheck: did you really mean 'doskey'?
docs/netlify-dev.md|123 col 40| [base.spelling] Spellcheck: did you really mean 'config'?
docs/netlify-dev.md|194 col 58| [base.spelling] Spellcheck: did you really mean 'hardcode'?
docs/netlify-dev.md|194 col 99| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'don't'
docs/netlify-dev.md|195 col 58| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'we'll'
docs/netlify-dev.md|212 col 90| [base.spelling] Spellcheck: did you really mean 'config'?
docs/netlify-dev.md|216 col 56| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'you'll'
docs/netlify-dev.md|231 col 30| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'project's'
docs/netlify-dev.md|232 col 32| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'project's'
docs/netlify-dev.md|233 col 32| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'project's'
docs/netlify-dev.md|235 col 1| [base.accessibilityVision] Don't use vision-based terms. Use something inclusive like 'visit', 'find', or 'check' instead of 'See'.
docs/netlify-dev.md|235 col 104| [base.spelling] Spellcheck: did you really mean 'Netlify's'?
docs/netlify-dev.md|235 col 104| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'Netlify's'
docs/netlify-dev.md|244 col 94| [base.accessibilityVision] Don't use vision-based terms. Use something inclusive like 'check', 'search', or 'examine' instead of 'look'.
docs/netlify-dev.md|250 col 91| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'you've'
docs/netlify-dev.md|272 col 98| [base.spelling] Spellcheck: did you really mean 'gitignored'?
docs/netlify-dev.md|326 col 16| [base.spelling] Spellcheck: did you really mean 'addons'?
docs/netlify-dev.md|354 col 113| [base.spelling] Spellcheck: did you really mean 'eg'?
docs/netlify-dev.md|358 col 58| [base.spelling] Spellcheck: did you really mean 'PR's'?
docs/netlify-dev.md|358 col 58| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'PR's'
docs/netlify-dev.md|374 col 60| [base.spelling] Spellcheck: did you really mean 'transpilation'?
docs/netlify-dev.md|374 col 79| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'TypeScript's'
docs/netlify-dev.md|377 col 1| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'We'll'
docs/netlify-dev.md|384 col 4| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'don't'
docs/netlify-dev.md|384 col 118| [smart-marks.smartQuotesBegin] Use a smart opening quote (“) instead of a straight quote for ' "just'
docs/netlify-dev.md|385 col 7| [smart-marks.smartQuotesEnd] Use a smart closing quote (”) instead of a straight quote for 'work"'
docs/netlify-dev.md|386 col 1| [base.accessibilityVision] Don't use vision-based terms. Use something inclusive like 'check', 'search', or 'examine' instead of 'look'.
docs/netlify-dev.md|393 col 42| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'don't'
docs/netlify-dev.md|413 col 48| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'site's'
docs/netlify-dev.md|415 col 22| [base.accessibilityMouse] Don't use mouse-specific terms. Use something inclusive like 'select' instead of 'click'.
docs/netlify-dev.md|417 col 107| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'site's'
docs/netlify-dev.md|418 col 82| [base.spelling] Spellcheck: did you really mean 'addon'?
docs/netlify-dev.md|420 col 60| [base.spelling] Spellcheck: did you really mean 'addons'?
docs/netlify-dev.md|421 col 9| [base.spelling] Spellcheck: did you really mean 'addons'?
docs/netlify-dev.md|441 col 26| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'You'll'
docs/netlify-dev.md|444 col 22| [base.spelling] Spellcheck: did you really mean 'deps'?
docs/netlify-dev.md|448 col 79| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'we'll'
README.md|9 col 1| [base.accessibilityVision] Don't use vision-based terms. Use something inclusive like 'visit', 'find', or 'check' instead of 'See'.
README.md|14 col 67| [base.accessibilityMouse] Don't use mouse-specific terms. Use something inclusive like 'select' instead of 'Click'.
README.md|22 col 6| [base.spelling] Spellcheck: did you really mean 'addons'?
README.md|28 col 6| [base.spelling] Spellcheck: did you really mean 'env'?
README.md|65 col 65| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'you're'
README.md|90 col 31| [base.accessibilityVision] Don't use vision-based terms. Use something inclusive like 'visit', 'find', or 'check' instead of 'see'.
README.md|95 col 6| [base.spelling] Spellcheck: did you really mean 'addons'?
README.md|99 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
README.md|120 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
README.md|133 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
README.md|138 col 6| [base.spelling] Spellcheck: did you really mean 'env'?
README.md|142 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
README.md|156 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
README.md|160 col 174| [base.spelling] Spellcheck: did you really mean 'Netlify's'?
README.md|160 col 174| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'Netlify's'
README.md|177 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
README.md|179 col 51| [netlify-terms.featureCapitalization] This feature name is a proper noun. Use 'Large Media' instead of 'large media'.
README.md|192 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
README.md|202 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
README.md|215 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
README.md|227 col 3| [base.spelling] Spellcheck: did you really mean 'Subcommand'?
README.md|249 col 1| [base.accessibilityVision] Don't use vision-based terms. Use something inclusive like 'visit', 'find', or 'check' instead of 'See'.
README.md|253 col 1| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'You'll'
README.md|259 col 5| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'you're'
README.md|263 col 6| [base.accessibilityVision] Don't use vision-based terms. Use something inclusive like 'visit', 'find', or 'check' instead of 'See'.
CODE_OF_CONDUCT.md|29 col 13| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in ' others' '
CODE_OF_CONDUCT.md|66 col 16| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'project's'
CONTRIBUTING.md|60 col 1| [base.spelling] Spellcheck: did you really mean 'ESLint'?
CONTRIBUTING.md|61 col 8| [base.spelling] Spellcheck: did you really mean 'ESLint'?
CONTRIBUTING.md|67 col 71| [base.spelling] Spellcheck: did you really mean 'ESLint'?
CONTRIBUTING.md|84 col 13| [base.spelling] Spellcheck: did you really mean 'cli'?
CONTRIBUTING.md|87 col 52| [base.spelling] Spellcheck: did you really mean 'config'?
CONTRIBUTING.md|97 col 17| [base.spelling] Spellcheck: did you really mean 'vitest'?
CONTRIBUTING.md|122 col 47| [base.spelling] Spellcheck: did you really mean 'subprocess'?
CONTRIBUTING.md|123 col 56| [base.spelling] Spellcheck: did you really mean 'subprocess'?
CONTRIBUTING.md|123 col 116| [base.spelling] Spellcheck: did you really mean 'cli'?
CONTRIBUTING.md|125 col 1| [base.spelling] Spellcheck: did you really mean 'subprocess'?
CONTRIBUTING.md|125 col 22| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'it's'
CONTRIBUTING.md|125 col 65| [base.accessibilityVision] Don't use vision-based terms. Use something inclusive like 'visit', 'find', or 'check' instead of 'see'.
CONTRIBUTING.md|127 col 31| [base.spelling] Spellcheck: did you really mean 'vitest'?
CONTRIBUTING.md|127 col 87| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'won't'
CONTRIBUTING.md|137 col 4| [smart-marks.smartApostrophes] Use a smart apostrophe (’) instead of a straight single quote mark in 'you're'
CONTRIBUTING.md|153 col 6| [base.spelling] Spellcheck: did you really mean 'autogenerate'?
CONTRIBUTING.md|168 col 22| [base.spelling] Spellcheck: did you really mean 'APIs'?