changelog: images updates, 2026W8 #879
reviewdog [vale] report
reported by reviewdog 🐶
Findings (28)
content/changelog/2025/07-17-request-flow.md|15 col 385| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2025/07-17-request-flow.md|15 col 405| [Google.We] Try to avoid using first-person plural like 'we'.
content/changelog/2026/01-28-images-update.md|48 col 1| [Google.OxfordComma] Use the Oxford comma in 'Request Flow is now available in .NET, Elixir, Haskell and'.
content/changelog/2026/01-28-images-update.md|48 col 79| [Google.We] Try to avoid using first-person plural like 'We'.
content/changelog/2026/02-18-images-update.md|3 col 84| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2026/02-18-images-update.md|15 col 1| [Google.We] Try to avoid using first-person plural like 'We'.
content/changelog/2026/02-18-images-update.md|15 col 16| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2026/02-18-images-update.md|15 col 62| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2026/02-18-images-update.md|21 col 5| [Vale.Spelling] Did you really mean 'Otoroshictl'?
content/changelog/2026/02-18-images-update.md|41 col 1| [Google.OxfordComma] Use the Oxford comma in 'Request Flow is now available in Go, Java/Scala, Meteor, Node.js & Bun, PHP and'.
content/changelog/2026/02-18-images-update.md|41 col 126| [Vale.Spelling] Did you really mean 'uv'?
content/changelog/2026/02-18-images-update.md|41 col 286| [Google.Will] Avoid using 'will'.
content/changelog/2026/02-12-images-update.md|2 col 68| [Vale.Spelling] Did you really mean 'uv'?
content/doc/applications/static.md|32 col 1| [Google.OxfordComma] Use the Oxford comma in 'Static is a flexible, light and'.
content/doc/applications/static.md|32 col 86| [Google.Acronyms] Spell out 'SSG', if it's unfamiliar to the audience.
content/doc/develop/request-flow.md|74 col 114| [Google.Passive] In general, use active voice instead of passive voice ('is handled').
content/doc/develop/varnish.md|21 col 258| [Vale.Spelling] Did you really mean 'runtime_version'?
content/doc/develop/varnish.md|24 col 248| [Vale.Spelling] Did you really mean 'Vlang'?
content/doc/develop/varnish.md|28 col 307| [Google.Contractions] Use 'doesn't' instead of 'does not'.
content/doc/develop/varnish.md|32 col 48| [Google.Contractions] Use 'aren't' instead of 'are not'.
content/doc/develop/varnish.md|32 col 69| [Google.Contractions] Use 'they're' instead of 'they are'.
content/doc/develop/varnish.md|32 col 138| [Google.Passive] In general, use active voice instead of passive voice ('is stored').
content/doc/develop/varnish.md|36 col 9| [Google.Passive] In general, use active voice instead of passive voice ('is managed').
content/doc/develop/varnish.md|36 col 85| [Google.Passive] In general, use active voice instead of passive voice ('is enabled').
content/doc/develop/varnish.md|36 col 218| [Vale.Spelling] Did you really mean 'middleware'?
content/doc/develop/varnish.md|36 col 385| [Google.Passive] In general, use active voice instead of passive voice ('is handled').
content/doc/develop/varnish.md|67 col 65| [Google.Contractions] Use 'won't' instead of 'will not'.
content/doc/develop/varnish.md|67 col 65| [Google.Will] Avoid using 'will'.
Filtered Findings (6404)
.github/pull_request_template.md|3 col 40| [Google.Contractions] Use 'they're' instead of 'they are'.
.github/pull_request_template.md|3 col 45| [Google.Passive] In general, use active voice instead of passive voice ('are needed').
.github/pull_request_template.md|25 col 7| [Google.FirstPerson] Avoid first-person pronouns such as 'I '.
archetypes/applications.md|3 col 24| [Google.Spacing] 'e.C' should have one space.
archetypes/applications.md|12 col 16| [Google.Acronyms] Spell out 'XXX', if it's unfamiliar to the audience.
archetypes/applications.md|14 col 17| [Google.Acronyms] Spell out 'XXX', if it's unfamiliar to the audience.
archetypes/applications.md|22 col 19| [Google.Acronyms] Spell out 'XXX', if it's unfamiliar to the audience.
archetypes/applications.md|26 col 1| [Google.Acronyms] Spell out 'XXX', if it's unfamiliar to the audience.
archetypes/applications.md|36 col 5| [Google.Acronyms] Spell out 'XXX', if it's unfamiliar to the audience.
archetypes/default.md|3 col 24| [Google.Spacing] 'e.C' should have one space.
archetypes/guides.md|3 col 24| [Google.Spacing] 'e.C' should have one space.
archetypes/guides.md|17 col 32| [Guides.ellipsis] Include the framework in the title!
content/_index.md|47 col 100| [Google.Semicolons] Use semicolons judiciously.
content/_index.md|81 col 27| [Vale.Avoid] Avoid using 'addons'.
CONTRIBUTING.md|14 col 106| [Google.Passive] In general, use active voice instead of passive voice ('be merged').
CONTRIBUTING.md|26 col 43| [Google.Passive] In general, use active voice instead of passive voice ('being updated').
CONTRIBUTING.md|43 col 8| [Vale.Spelling] Did you really mean 'Shortcodes'?
CONTRIBUTING.md|45 col 104| [Vale.Spelling] Did you really mean 'shortcodes'?
CONTRIBUTING.md|49 col 4| [Vale.Spelling] Did you really mean 'Callouts'?
CONTRIBUTING.md|49 col 175| [Vale.Spelling] Did you really mean 'callouts'?
CONTRIBUTING.md|49 col 238| [Vale.Spelling] Did you really mean 'callouts'?
content/api/_index.md|5 col 63| [Google.We] Try to avoid using first-person plural like 'our'.
CLAUDE.md|20 col 13| [Clever.organisation] Use 'organisation' instead of 'organization'
CLAUDE.md|24 col 58| [Vale.Avoid] Avoid using 'addons'.
CLAUDE.md|24 col 58| [Vale.Spelling] Did you really mean 'addons'?
CLAUDE.md|34 col 50| [Vale.Spelling] Did you really mean 'favicon'?
CLAUDE.md|35 col 40| [Vale.Spelling] Did you really mean 'shortcodes'?
CLAUDE.md|42 col 19| [Google.Acronyms] Spell out 'SEO', if it's unfamiliar to the audience.
CLAUDE.md|43 col 25| [Google.Acronyms] Spell out 'SEO', if it's unfamiliar to the audience.
CLAUDE.md|55 col 31| [Vale.Spelling] Did you really mean 'shortcodes'?
CLAUDE.md|56 col 16| [Google.Contractions] Use 'shouldn't' instead of 'should not'.
CLAUDE.md|63 col 45| [Clever.organisation] Use 'organisation' instead of 'organization'
CLAUDE.md|69 col 25| [Google.FirstPerson] Avoid first-person pronouns such as ' I, '.
CLAUDE.md|69 col 29| [Google.FirstPerson] Avoid first-person pronouns such as 'me'.
CLAUDE.md|69 col 33| [Google.FirstPerson] Avoid first-person pronouns such as 'my'.
CLAUDE.md|69 col 37| [Google.We] Try to avoid using first-person plural like 'we'.
CLAUDE.md|69 col 41| [Google.We] Try to avoid using first-person plural like 'us'.
CLAUDE.md|69 col 45| [Google.We] Try to avoid using first-person plural like 'our'.
CLAUDE.md|69 col 50| [Google.We] Try to avoid using first-person plural like 'let's'.
CLAUDE.md|70 col 24| [Google.Quotes] Commas and periods go inside quotation marks.
CLAUDE.md|70 col 39| [Google.Quotes] Commas and periods go inside quotation marks.
CLAUDE.md|70 col 66| [Google.Passive] In general, use active voice instead of passive voice ('be noted').
CLAUDE.md|71 col 25| [Google.Quotes] Commas and periods go inside quotation marks.
CLAUDE.md|71 col 35| [Google.Quotes] Commas and periods go inside quotation marks.
CLAUDE.md|71 col 43| [Google.Quotes] Commas and periods go inside quotation marks.
CLAUDE.md|71 col 53| [Google.Quotes] Commas and periods go inside quotation marks.
CLAUDE.md|72 col 28| [Google.Quotes] Commas and periods go inside quotation marks.
CLAUDE.md|72 col 36| [Google.Quotes] Commas and periods go inside quotation marks.
CLAUDE.md|85 col 34| [Google.Quotes] Commas and periods go inside quotation marks.
CLAUDE.md|85 col 41| [Google.Quotes] Commas and periods go inside quotation marks.
CLAUDE.md|89 col 10| [Google.Passive] In general, use active voice instead of passive voice ('is configured').
CLAUDE.md|96 col 57| [Google.Passive] In general, use active voice instead of passive voice ('is maintained').
CLAUDE.md|96 col 114| [Google.Passive] In general, use active voice instead of passive voice ('be kept').
CLAUDE.md|96 col 238| [Google.Acronyms] Spell out 'LLMS', if it's unfamiliar to the audience.
CLAUDE.md|98 col 9| [Vale.Spelling] Did you really mean 'Shortcodes'?
CLAUDE.md|100 col 13| [Vale.Spelling] Did you really mean 'Shortcodes'?
CLAUDE.md|102 col 72| [Vale.Spelling] Did you really mean 'shortcodes'?
CLAUDE.md|106 col 49| [Vale.Spelling] Did you really mean 'callouts'?
CLAUDE.md|120 col 62| [Google.WordList] Use 'capability' or 'feature' instead of 'functionality'.
CLAUDE.md|123 col 78| [Google.Acronyms] Spell out 'POSIX', if it's unfamiliar to the audience.
content/changelog/2023/11-10-healthcheck-for-java.md|11 col 45| [Google.Passive] In general, use active voice instead of passive voice ('be deployed').
content/changelog/2023/11-10-healthcheck-for-java.md|11 col 85| [Vale.Spelling] Did you really mean 'healtchecks'?
content/changelog/2023/11-10-healthcheck-for-java.md|17 col 52| [Google.Will] Avoid using 'will'.
content/changelog/2023/11-10-healthcheck-for-java.md|19 col 156| [Google.Passive] In general, use active voice instead of passive voice ('been validated').
content/changelog/2023/11-10-healthcheck-for-java.md|20 col 81| [Google.Passive] In general, use active voice instead of passive voice ('is considered').
content/changelog/2023/11-10-healthcheck-for-java.md|22 col 101| [Google.Contractions] Use 'doesn't' instead of 'does not'.
content/changelog/2023/11-29-api-update.md|19 col 155| [Google.Will] Avoid using 'will'.
content/changelog/2023/11-29-api-update.md|19 col 202| [Google.Passive] In general, use active voice instead of passive voice ('been updated').
content/changelog/2023/12-13-cellar-migration-tool-update.md|17 col 77| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2023/12-15-sozu-0.15.18.md|16 col 1| [Google.We] Try to avoid using first-person plural like 'Our'.
content/changelog/2023/12-15-sozu-0.15.18.md|18 col 53| [Google.Contractions] Use 'doesn't' instead of 'does not'.
content/changelog/2023/12-15-sozu-0.15.18.md|19 col 57| [Google.WordList] Use 'HTTPS' instead of 'HTTPs'.
content/changelog/2023/12-15-sozu-0.15.18.md|19 col 66| [Vale.Spelling] Did you really mean 'WSs'?
content/changelog/2023/12-15-sozu-0.15.18.md|20 col 60| [Vale.Spelling] Did you really mean 'Rustls'?
README.md|3 col 14| [Google.Passive] In general, use active voice instead of passive voice ('is based').
README.md|3 col 226| [Google.Acronyms] Spell out 'SEO', if it's unfamiliar to the audience.
README.md|6 col 13| [Vale.Spelling] Did you really mean 'shortcodes'?
README.md|31 col 18| [Google.Passive] In general, use active voice instead of passive voice ('is set').
README.md|47 col 10| [Google.Passive] In general, use active voice instead of passive voice ('is configured').
README.md|59 col 5| [Google.Acronyms] Spell out 'TIP', if it's unfamiliar to the audience.
README.md|82 col 41| [Google.Passive] In general, use active voice instead of passive voice ('is set').
README.md|84 col 5| [Google.Acronyms] Spell out 'TIP', if it's unfamiliar to the audience.
README.md|89 col 86| [Google.Passive] In general, use active voice instead of passive voice ('is created').
README.md|91 col 21| [Google.Passive] In general, use active voice instead of passive voice ('be made').
README.md|101 col 125| [Google.WordList] Use 'media type' instead of 'content type'.
README.md|101 col 138| [Google.Latin] Use 'that is' instead of 'i.e.'.
README.md|101 col 176| [Google.We] Try to avoid using first-person plural like 'We'.
README.md|116 col 55| [Google.Acronyms] Spell out 'SEO', if it's unfamiliar to the audience.
README.md|119 col 39| [Google.Passive] In general, use active voice instead of passive voice ('be indexed').
README.md|119 col 81| [Google.We] Try to avoid using first-person plural like 'we'.
README.md|128 col 116| [Google.Contractions] Use 'isn't' instead of 'is not'.
README.md|131 col 14| [Google.Passive] In general, use active voice instead of passive voice ('are used').
README.md|131 col 27| [Google.Acronyms] Spell out 'SEO', if it's unfamiliar to the audience.
README.md|134 col 10| [Google.Passive] In general, use active voice instead of passive voice ('are recommended').
README.md|134 col 77| [Google.Contractions] Use 'they're' instead of 'They are'.
README.md|134 col 82| [Google.Passive] In general, use active voice instead of passive voice ('are written').
README.md|137 col 9| [Google.Passive] In general, use active voice instead of passive voice ('be set').
README.md|137 col 67| [Google.Passive] In general, use active voice instead of passive voice ('are defined').
README.md|137 col 111| [Vale.Spelling] Did you really mean 'Github'?
README.md|137 col 211| [Google.Passive] In general, use active voice instead of passive voice ('be set').
README.md|140 col 19| [Google.Will] Avoid using 'will'.
README.md|140 col 24| [Google.Passive] In general, use active voice instead of passive voice ('be displayed').
README.md|140 col 75| [Google.Acronyms] Spell out 'ISO', if it's unfamiliar to the audience.
README.md|173 col 26| [Vale.Spelling] Did you really mean 'shortcodes'?
README.md|182 col 5| [Google.Acronyms] Spell out 'TIP', if it's unfamiliar to the audience.
README.md|183 col 53| [Vale.Spelling] Did you really mean 'shortcodes'?
README.md|183 col 178| [Google.Passive] In general, use active voice instead of passive voice ('be rendered').
README.md|193 col 12| [Vale.Spelling] Did you really mean 'Goldmark'?
README.md|193 col 245| [Google.Passive] In general, use active voice instead of passive voice ('are linted').
README.md|193 col 331| [Google.We] Try to avoid using first-person plural like 'We'.
README.md|195 col 17| [Google.Passive] In general, use active voice instead of passive voice ('be downloaded').
README.md|200 col 28| [Google.Passive] In general, use active voice instead of passive voice ('are listed').
README.md|201 col 70| [Google.Passive] In general, use active voice instead of passive voice ('are configured').
content/changelog/2023/12-18-new-par-ip-console.md|2 col 36| [Google.Acronyms] Spell out 'PAR', if it's unfamiliar to the audience.
content/changelog/2023/12-18-new-par-ip-console.md|11 col 50| [Google.Acronyms] Spell out 'PAR', if it's unfamiliar to the audience.
content/changelog/2023/12-18-new-par-ip-console.md|17 col 10| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2023/12-18-new-par-ip-console.md|17 col 79| [Google.Passive] In general, use active voice instead of passive voice ('be used').
content/changelog/2023/12-18-new-par-ip-console.md|17 col 104| [Google.Contractions] Use 'they're' instead of 'They are'.
.github/copilot-instructions.md|20 col 13| [Clever.organisation] Use 'organisation' instead of 'organization'
.github/copilot-instructions.md|21 col 48| [Vale.Spelling] Did you really mean 'addons'?
.github/copilot-instructions.md|21 col 48| [Vale.Avoid] Avoid using 'addons'.
.github/copilot-instructions.md|66 col 52| [Clever.organisation] Use 'organisation' instead of 'organization'
.github/copilot-instructions.md|67 col 35| [Google.FirstPerson] Avoid first-person pronouns such as ' I, '.
.github/copilot-instructions.md|67 col 39| [Google.FirstPerson] Avoid first-person pronouns such as 'me'.
.github/copilot-instructions.md|67 col 43| [Google.FirstPerson] Avoid first-person pronouns such as 'my'.
.github/copilot-instructions.md|67 col 47| [Google.We] Try to avoid using first-person plural like 'we'.
.github/copilot-instructions.md|67 col 51| [Google.We] Try to avoid using first-person plural like 'us'.
.github/copilot-instructions.md|67 col 55| [Google.We] Try to avoid using first-person plural like 'our'.
.github/copilot-instructions.md|67 col 60| [Google.We] Try to avoid using first-person plural like 'let's'.
.github/copilot-instructions.md|72 col 24| [Google.Quotes] Commas and periods go inside quotation marks.
.github/copilot-instructions.md|72 col 39| [Google.Quotes] Commas and periods go inside quotation marks.
.github/copilot-instructions.md|72 col 66| [Google.Passive] In general, use active voice instead of passive voice ('be noted').
.github/copilot-instructions.md|73 col 25| [Google.Quotes] Commas and periods go inside quotation marks.
.github/copilot-instructions.md|73 col 35| [Google.Quotes] Commas and periods go inside quotation marks.
.github/copilot-instructions.md|73 col 43| [Google.Quotes] Commas and periods go inside quotation marks.
.github/copilot-instructions.md|73 col 53| [Google.Quotes] Commas and periods go inside quotation marks.
.github/copilot-instructions.md|74 col 28| [Google.Quotes] Commas and periods go inside quotation marks.
.github/copilot-instructions.md|74 col 36| [Google.Quotes] Commas and periods go inside quotation marks.
.github/copilot-instructions.md|97 col 14| [Clever.organisation] Use 'organisation' instead of 'organization'
.github/copilot-instructions.md|108 col 9| [Vale.Spelling] Did you really mean 'callouts'?
.github/copilot-instructions.md|119 col 16| [Vale.Spelling] Did you really mean 'shortcodes'?
.github/copilot-instructions.md|200 col 35| [Google.Quotes] Commas and periods go inside quotation marks.
.github/copilot-instructions.md|200 col 42| [Google.Quotes] Commas and periods go inside quotation marks.
.github/copilot-instructions.md|224 col 36| [Google.We] Try to avoid using first-person plural like 'we'.
.github/copilot-instructions.md|224 col 40| [Google.We] Try to avoid using first-person plural like 'us'.
.github/copilot-instructions.md|224 col 44| [Google.We] Try to avoid using first-person plural like 'our'.
.github/copilot-instructions.md|226 col 14| [Vale.Spelling] Did you really mean 'callouts'?
.github/copilot-instructions.md|241 col 14| [Vale.Spelling] Did you really mean 'shortcodes'?
.github/copilot-instructions.md|248 col 63| [Vale.Spelling] Did you really mean 'shortcodes'?
.github/copilot-instructions.md|261 col 29| [Google.Passive] In general, use active voice instead of passive voice ('be verified').
.github/copilot-instructions.md|272 col 10| [Google.Passive] In general, use active voice instead of passive voice ('is configured').
.github/copilot-instructions.md|284 col 78| [Google.Acronyms] Spell out 'POSIX', if it's unfamiliar to the audience.
.github/copilot-instructions.md|291 col 1| [Google.Spelling] In general, use American spelling instead of 'Organise'.
.github/copilot-instructions.md|292 col 34| [Google.Passive] In general, use active voice instead of passive voice ('is included').
content/changelog/2023/12-18-java-21-default.md|19 col 8| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2023/12-18-php-8-default.md|22 col 8| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2024/01-02-pulsar-update.md|11 col 48| [Google.Passive] In general, use active voice instead of passive voice ('been updated').
content/changelog/2024/01-02-pulsar-update.md|17 col 1| [Google.We] Try to avoid using first-person plural like 'We'.
content/changelog/2024/01-02-pulsar-update.md|17 col 50| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2024/01-02-pulsar-update.md|17 col 64| [Google.We] Try to avoid using first-person plural like 'Our'.
content/changelog/2023/12-19-console-web-components-v12.md|17 col 37| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2023/12-19-console-web-components-v12.md|17 col 165| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2023/12-19-console-web-components-v12.md|17 col 191| [Google.OxfordComma] Use the Oxford comma in 'It also gives multiple new features with some bug fixes, refactoring and'.
content/changelog/2023/12-19-console-web-components-v12.md|21 col 115| [Google.Latin] Use 'for example' instead of 'e.g.'.
content/changelog/2024/01-10-documentation-changelog.md|17 col 61| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2024/01-10-documentation-changelog.md|23 col 1| [Google.Passive] In general, use active voice instead of passive voice ('been added').
content/changelog/2024/01-10-documentation-changelog.md|23 col 45| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2024/01-10-documentation-changelog.md|23 col 74| [Google.Will] Avoid using 'will'.
content/changelog/2024/01-10-documentation-changelog.md|23 col 153| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2023/12-22-sozu-wider-usage.md|10 col 39| [Google.Passive] In general, use active voice instead of passive voice ('be used').
content/changelog/2023/12-22-sozu-wider-usage.md|18 col 1| [Google.We] Try to avoid using first-person plural like 'Our'.
content/changelog/2023/12-22-sozu-wider-usage.md|18 col 44| [Google.Passive] In general, use active voice instead of passive voice ('be used').
content/changelog/2024/01-15-go-sdk-v0.0.8.md|15 col 45| [Google.Passive] In general, use active voice instead of passive voice ('been updated').
content/changelog/2024/01-15-go-sdk-v0.0.8.md|21 col 20| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2024/01-15-go-sdk-v0.0.8.md|21 col 61| [Google.We] Try to avoid using first-person plural like 'we'.
content/changelog/2024/01-15-go-sdk-v0.0.8.md|21 col 107| [Google.OxfordComma] Use the Oxford comma in 'It has just been updated to version 0.0.8 with updated dependencies, fixes and'.
content/changelog/2024/01-15-go-sdk-v0.0.8.md|21 col 119| [Google.Passive] In general, use active voice instead of passive voice ('been updated').
content/changelog/2024/01-22-matomo-5.0.1.md|20 col 35| [Google.Passive] In general, use active voice instead of passive voice ('was released').
content/changelog/2024/01-22-matomo-5.0.1.md|20 col 106| [Google.We] Try to avoid using first-person plural like 'we'.
content/changelog/2024/01-22-matomo-5.0.1.md|20 col 175| [Google.Exclamation] Don't use exclamation points in text.
content/changelog/2024/01-22-matomo-5.0.1.md|20 col 231| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2024/01-22-matomo-5.0.1.md|22 col 40| [Clever.hyphens] Write 'up-to-date' with hyphens when used as an adjective before a noun, but as separate words when it appears as a noun phrase or after a verb
content/changelog/2024/01-24-ruby-3.3.0.md|17 col 115| [Google.Passive] In general, use active voice instead of passive voice ('be set').
content/api/howto.md|16 col 262| [Google.Will] Avoid using 'will'.
content/api/howto.md|25 col 16| [Google.Acronyms] Spell out 'REST', if it's unfamiliar to the audience.
content/api/howto.md|27 col 158| [Google.Passive] In general, use active voice instead of passive voice ('be handled').
content/api/howto.md|29 col 15| [Google.Passive] In general, use active voice instead of passive voice ('is designed').
content/api/howto.md|29 col 266| [Google.Passive] In general, use active voice instead of passive voice ('is recommended').
content/api/howto.md|29 col 397| [Google.Passive] In general, use active voice instead of passive voice ('is required').
content/api/howto.md|39 col 127| [Google.Passive] In general, use active voice instead of passive voice ('be enabled').
content/api/howto.md|54 col 31| [Google.Passive] In general, use active voice instead of passive voice ('be used').
content/api/howto.md|62 col 304| [Google.Passive] In general, use active voice instead of passive voice ('are installed').
content/api/howto.md|74 col 70| [Google.We] Try to avoid using first-person plural like 'our'.
content/api/howto.md|85 col 79| [Google.Passive] In general, use active voice instead of passive voice ('be done').
content/api/howto.md|85 col 177| [Google.WordList] Use 'click' or 'click in' instead of 'click on'.
content/api/howto.md|85 col 252| [Google.Will] Avoid using 'will'.
content/api/howto.md|93 col 9| [Google.Will] Avoid using 'will'.
content/api/howto.md|96 col 19| [Google.Passive] In general, use active voice instead of passive voice ('is logged').
content/api/howto.md|96 col 45| [Google.Will] Avoid using 'will'.
content/api/howto.md|96 col 50| [Google.Passive] In general, use active voice instead of passive voice ('be redirected').
content/api/howto.md|96 col 99| [Vale.Spelling] Did you really mean 'params'?
content/api/howto.md|100 col 9| [Google.Will] Avoid using 'will'.
content/changelog/2024/01-30-js-client-8.0.3.md|15 col 45| [Google.Passive] In general, use active voice instead of passive voice ('been updated').
content/changelog/2024/01-30-js-client-8.0.3.md|21 col 20| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2024/01-30-js-client-8.0.3.md|21 col 69| [Google.We] Try to avoid using first-person plural like 'we'.
content/changelog/2024/01-30-js-client-8.0.3.md|21 col 208| [Google.Passive] In general, use active voice instead of passive voice ('been updated').
content/changelog/2024/01-30-js-client-8.0.3.md|21 col 347| [Vale.Spelling] Did you really mean 'param'?
content/changelog/2024/01-30-js-client-8.0.3.md|21 col 428| [Google.Acronyms] Spell out 'SSE', if it's unfamiliar to the audience.
content/changelog/2024/01-30-js-client-8.0.3.md|21 col 468| [Google.Acronyms] Spell out 'SSE', if it's unfamiliar to the audience.
content/changelog/2024/01-25-clever-tools-3.1.0.md|14 col 14| [Google.Passive] In general, use active voice instead of passive voice ('Be prepared').
content/changelog/2024/01-25-clever-tools-3.1.0.md|14 col 83| [Google.Exclamation] Don't use exclamation points in text.
content/changelog/2024/01-25-clever-tools-3.1.0.md|20 col 21| [Google.We] Try to avoid using first-person plural like 'we'.
content/changelog/2024/01-25-clever-tools-3.1.0.md|20 col 39| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2024/01-25-clever-tools-3.1.0.md|23 col 39| [Google.Exclamation] Don't use exclamation points in text.
content/changelog/2024/01-25-clever-tools-3.1.0.md|27 col 25| [Google.Passive] In general, use active voice instead of passive voice ('be used').
content/changelog/2024/01-25-clever-tools-3.1.0.md|29 col 47| [Google.Passive] In general, use active voice instead of passive voice ('be prepared').
content/changelog/2024/01-25-clever-tools-3.1.0.md|29 col 89| [Google.Exclamation] Don't use exclamation points in text.
content/api/v4.md|14 col 32| [Google.Acronyms] Spell out 'REST', if it's unfamiliar to the audience.
content/api/v4.md|15 col 4| [Google.We] Try to avoid using first-person plural like 'our'.
content/api/v4.md|15 col 26| [Google.We] Try to avoid using first-person plural like 'we'.
content/api/v4.md|23 col 65| [Google.We] Try to avoid using first-person plural like 'our'.
content/api/v4.md|37 col 44| [Google.Acronyms] Spell out 'ISO', if it's unfamiliar to the audience.
content/api/v4.md|38 col 44| [Google.Acronyms] Spell out 'ISO', if it's unfamiliar to the audience.
content/api/v4.md|146 col 44| [Google.Acronyms] Spell out 'ISO', if it's unfamiliar to the audience.
content/api/v4.md|147 col 44| [Google.Acronyms] Spell out 'ISO', if it's unfamiliar to the audience.
content/api/v4.md|202 col 24| [Google.Acronyms] Spell out 'SSE', if it's unfamiliar to the audience.
content/api/v4.md|208 col 44| [Google.Acronyms] Spell out 'ISO', if it's unfamiliar to the audience.
content/api/v4.md|209 col 44| [Google.Acronyms] Spell out 'ISO', if it's unfamiliar to the audience.
content/api/v4.md|213 col 44| [Vale.Spelling] Did you really mean 'systemd'?
content/api/v4.md|240 col 50| [Vale.Spelling] Did you really mean 'OVHcloud'?
content/api/v4.md|241 col 50| [Vale.Spelling] Did you really mean 'OVHcloud'?
content/api/v4.md|241 col 59| [Google.Acronyms] Spell out 'RFC', if it's unfamiliar to the audience.
content/api/v4.md|301 col 65| [Google.Passive] In general, use active voice instead of passive voice ('be used').
content/api/v4.md|319 col 21| [Google.Passive] In general, use active voice instead of passive voice ('is found').
content/api/v4.md|355 col 115| [Google.Passive] In general, use active voice instead of passive voice ('are kept').
content/api/v4.md|355 col 167| [Google.Passive] In general, use active voice instead of passive voice ('are kept').
content/api/v4.md|355 col 196| [Vale.Spelling] Did you really mean 'NVMe'?
content/api/v4.md|355 col 201| [Google.Acronyms] Spell out 'SSD', if it's unfamiliar to the audience.
content/api/v4.md|355 col 213| [Google.Passive] In general, use active voice instead of passive voice ('being moved').
content/api/v4.md|355 col 266| [Google.Acronyms] Spell out 'HDD', if it's unfamiliar to the audience.
content/changelog/2024/02-02-images-update.md|18 col 27| [Google.We] Try to avoid using first-person plural like 'we'.
content/changelog/2024/02-02-images-update.md|18 col 52| [Google.We] Try to avoid using first-person plural like 'we'.
content/changelog/2024/02-02-images-update.md|18 col 61| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2024/02-02-images-update.md|18 col 132| [Google.We] Try to avoid using first-person plural like 'We'.
content/changelog/2024/02-02-images-update.md|18 col 201| [Google.Will] Avoid using 'will'.
content/changelog/2024/02-02-images-update.md|18 col 212| [Google.We] Try to avoid using first-person plural like 'us'.
content/changelog/2024/02-02-images-update.md|20 col 1| [Google.OxfordComma] Use the Oxford comma in 'In the meantime, we've updated Docker, Elixir, Go, Haskell, Ruby and'.
content/changelog/2024/02-02-images-update.md|20 col 18| [Google.We] Try to avoid using first-person plural like 'we'.
content/changelog/2024/02-02-images-update.md|20 col 117| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2024/02-02-images-update.md|24 col 5| [Vale.Spelling] Did you really mean 'runc'?
content/changelog/2024/02-02-images-update.md|25 col 5| [Vale.Spelling] Did you really mean 'containerd'?
... (Too many findings. Dropped some findings)
Annotations
Check warning on line 15 in content/changelog/2025/07-17-request-flow.md
github-actions / vale
[vale] content/changelog/2025/07-17-request-flow.md#L15
[Google.We] Try to avoid using first-person plural like 'our'.
Raw output
{"message": "[Google.We] Try to avoid using first-person plural like 'our'.", "location": {"path": "content/changelog/2025/07-17-request-flow.md", "range": {"start": {"line": 15, "column": 385}}}, "severity": "WARNING"}
Check warning on line 15 in content/changelog/2025/07-17-request-flow.md
github-actions / vale
[vale] content/changelog/2025/07-17-request-flow.md#L15
[Google.We] Try to avoid using first-person plural like 'we'.
Raw output
{"message": "[Google.We] Try to avoid using first-person plural like 'we'.", "location": {"path": "content/changelog/2025/07-17-request-flow.md", "range": {"start": {"line": 15, "column": 405}}}, "severity": "WARNING"}
Check warning on line 48 in content/changelog/2026/01-28-images-update.md
github-actions / vale
[vale] content/changelog/2026/01-28-images-update.md#L48
[Google.OxfordComma] Use the Oxford comma in 'Request Flow is now available in .NET, Elixir, Haskell and'.
Raw output
{"message": "[Google.OxfordComma] Use the Oxford comma in 'Request Flow is now available in .NET, Elixir, Haskell and'.", "location": {"path": "content/changelog/2026/01-28-images-update.md", "range": {"start": {"line": 48, "column": 1}}}, "severity": "WARNING"}
Check warning on line 48 in content/changelog/2026/01-28-images-update.md
github-actions / vale
[vale] content/changelog/2026/01-28-images-update.md#L48
[Google.We] Try to avoid using first-person plural like 'We'.
Raw output
{"message": "[Google.We] Try to avoid using first-person plural like 'We'.", "location": {"path": "content/changelog/2026/01-28-images-update.md", "range": {"start": {"line": 48, "column": 79}}}, "severity": "WARNING"}
Check warning on line 3 in content/changelog/2026/02-18-images-update.md
github-actions / vale
[vale] content/changelog/2026/02-18-images-update.md#L3
[Google.We] Try to avoid using first-person plural like 'our'.
Raw output
{"message": "[Google.We] Try to avoid using first-person plural like 'our'.", "location": {"path": "content/changelog/2026/02-18-images-update.md", "range": {"start": {"line": 3, "column": 84}}}, "severity": "WARNING"}
Check warning on line 15 in content/changelog/2026/02-18-images-update.md
github-actions / vale
[vale] content/changelog/2026/02-18-images-update.md#L15
[Google.We] Try to avoid using first-person plural like 'We'.
Raw output
{"message": "[Google.We] Try to avoid using first-person plural like 'We'.", "location": {"path": "content/changelog/2026/02-18-images-update.md", "range": {"start": {"line": 15, "column": 1}}}, "severity": "WARNING"}
Check warning on line 15 in content/changelog/2026/02-18-images-update.md
github-actions / vale
[vale] content/changelog/2026/02-18-images-update.md#L15
[Google.We] Try to avoid using first-person plural like 'our'.
Raw output
{"message": "[Google.We] Try to avoid using first-person plural like 'our'.", "location": {"path": "content/changelog/2026/02-18-images-update.md", "range": {"start": {"line": 15, "column": 16}}}, "severity": "WARNING"}
Check warning on line 15 in content/changelog/2026/02-18-images-update.md
github-actions / vale
[vale] content/changelog/2026/02-18-images-update.md#L15
[Google.We] Try to avoid using first-person plural like 'our'.
Raw output
{"message": "[Google.We] Try to avoid using first-person plural like 'our'.", "location": {"path": "content/changelog/2026/02-18-images-update.md", "range": {"start": {"line": 15, "column": 62}}}, "severity": "WARNING"}
Check failure on line 21 in content/changelog/2026/02-18-images-update.md
github-actions / vale
[vale] content/changelog/2026/02-18-images-update.md#L21
[Vale.Spelling] Did you really mean 'Otoroshictl'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'Otoroshictl'?", "location": {"path": "content/changelog/2026/02-18-images-update.md", "range": {"start": {"line": 21, "column": 5}}}, "severity": "ERROR"}
Check warning on line 41 in content/changelog/2026/02-18-images-update.md
github-actions / vale
[vale] content/changelog/2026/02-18-images-update.md#L41
[Google.OxfordComma] Use the Oxford comma in 'Request Flow is now available in Go, Java/Scala, Meteor, Node.js & Bun, PHP and'.
Raw output
{"message": "[Google.OxfordComma] Use the Oxford comma in 'Request Flow is now available in Go, Java/Scala, Meteor, Node.js \u0026 Bun, PHP and'.", "location": {"path": "content/changelog/2026/02-18-images-update.md", "range": {"start": {"line": 41, "column": 1}}}, "severity": "WARNING"}
Check failure on line 41 in content/changelog/2026/02-18-images-update.md
github-actions / vale
[vale] content/changelog/2026/02-18-images-update.md#L41
[Vale.Spelling] Did you really mean 'uv'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'uv'?", "location": {"path": "content/changelog/2026/02-18-images-update.md", "range": {"start": {"line": 41, "column": 126}}}, "severity": "ERROR"}
Check warning on line 41 in content/changelog/2026/02-18-images-update.md
github-actions / vale
[vale] content/changelog/2026/02-18-images-update.md#L41
[Google.Will] Avoid using 'will'.
Raw output
{"message": "[Google.Will] Avoid using 'will'.", "location": {"path": "content/changelog/2026/02-18-images-update.md", "range": {"start": {"line": 41, "column": 286}}}, "severity": "WARNING"}
Check failure on line 2 in content/changelog/2026/02-12-images-update.md
github-actions / vale
[vale] content/changelog/2026/02-12-images-update.md#L2
[Vale.Spelling] Did you really mean 'uv'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'uv'?", "location": {"path": "content/changelog/2026/02-12-images-update.md", "range": {"start": {"line": 2, "column": 68}}}, "severity": "ERROR"}
Check warning on line 32 in content/doc/applications/static.md
github-actions / vale
[vale] content/doc/applications/static.md#L32
[Google.OxfordComma] Use the Oxford comma in 'Static is a flexible, light and'.
Raw output
{"message": "[Google.OxfordComma] Use the Oxford comma in 'Static is a flexible, light and'.", "location": {"path": "content/doc/applications/static.md", "range": {"start": {"line": 32, "column": 1}}}, "severity": "WARNING"}
Check notice on line 32 in content/doc/applications/static.md
github-actions / vale
[vale] content/doc/applications/static.md#L32
[Google.Acronyms] Spell out 'SSG', if it's unfamiliar to the audience.
Raw output
{"message": "[Google.Acronyms] Spell out 'SSG', if it's unfamiliar to the audience.", "location": {"path": "content/doc/applications/static.md", "range": {"start": {"line": 32, "column": 86}}}, "severity": "INFO"}
Check notice on line 74 in content/doc/develop/request-flow.md
github-actions / vale
[vale] content/doc/develop/request-flow.md#L74
[Google.Passive] In general, use active voice instead of passive voice ('is handled').Raw output
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('is handled').", "location": {"path": "content/doc/develop/request-flow.md", "range": {"start": {"line": 74, "column": 114}}}, "severity": "INFO"}
Check failure on line 21 in content/doc/develop/varnish.md
github-actions / vale
[vale] content/doc/develop/varnish.md#L21
[Vale.Spelling] Did you really mean 'runtime_version'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'runtime_version'?", "location": {"path": "content/doc/develop/varnish.md", "range": {"start": {"line": 21, "column": 258}}}, "severity": "ERROR"}
Check failure on line 24 in content/doc/develop/varnish.md
github-actions / vale
[vale] content/doc/develop/varnish.md#L24
[Vale.Spelling] Did you really mean 'Vlang'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'Vlang'?", "location": {"path": "content/doc/develop/varnish.md", "range": {"start": {"line": 24, "column": 248}}}, "severity": "ERROR"}
Check notice on line 28 in content/doc/develop/varnish.md
github-actions / vale
[vale] content/doc/develop/varnish.md#L28
[Google.Contractions] Use 'doesn't' instead of 'does not'.
Raw output
{"message": "[Google.Contractions] Use 'doesn't' instead of 'does not'.", "location": {"path": "content/doc/develop/varnish.md", "range": {"start": {"line": 28, "column": 307}}}, "severity": "INFO"}
Check notice on line 32 in content/doc/develop/varnish.md
github-actions / vale
[vale] content/doc/develop/varnish.md#L32
[Google.Contractions] Use 'aren't' instead of 'are not'.
Raw output
{"message": "[Google.Contractions] Use 'aren't' instead of 'are not'.", "location": {"path": "content/doc/develop/varnish.md", "range": {"start": {"line": 32, "column": 48}}}, "severity": "INFO"}
Check notice on line 32 in content/doc/develop/varnish.md
github-actions / vale
[vale] content/doc/develop/varnish.md#L32
[Google.Contractions] Use 'they're' instead of 'they are'.
Raw output
{"message": "[Google.Contractions] Use 'they're' instead of 'they are'.", "location": {"path": "content/doc/develop/varnish.md", "range": {"start": {"line": 32, "column": 69}}}, "severity": "INFO"}
Check notice on line 32 in content/doc/develop/varnish.md
github-actions / vale
[vale] content/doc/develop/varnish.md#L32
[Google.Passive] In general, use active voice instead of passive voice ('is stored').Raw output
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('is stored').", "location": {"path": "content/doc/develop/varnish.md", "range": {"start": {"line": 32, "column": 138}}}, "severity": "INFO"}
Check notice on line 36 in content/doc/develop/varnish.md
github-actions / vale
[vale] content/doc/develop/varnish.md#L36
[Google.Passive] In general, use active voice instead of passive voice ('is managed').Raw output
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('is managed').", "location": {"path": "content/doc/develop/varnish.md", "range": {"start": {"line": 36, "column": 9}}}, "severity": "INFO"}
Check notice on line 36 in content/doc/develop/varnish.md
github-actions / vale
[vale] content/doc/develop/varnish.md#L36
[Google.Passive] In general, use active voice instead of passive voice ('is enabled').Raw output
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('is enabled').", "location": {"path": "content/doc/develop/varnish.md", "range": {"start": {"line": 36, "column": 85}}}, "severity": "INFO"}
Check failure on line 36 in content/doc/develop/varnish.md
github-actions / vale
[vale] content/doc/develop/varnish.md#L36
[Vale.Spelling] Did you really mean 'middleware'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'middleware'?", "location": {"path": "content/doc/develop/varnish.md", "range": {"start": {"line": 36, "column": 218}}}, "severity": "ERROR"}