Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft : Add Versioning tutorial for Cellar with AWS CLI #516

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Add Versioning tutorial for Cellr with AWS CLI

9233626
Select commit
Loading
Failed to load commit list.
Sign in for the full log view
Draft

Draft : Add Versioning tutorial for Cellar with AWS CLI #516

Add Versioning tutorial for Cellr with AWS CLI
9233626
Select commit
Loading
Failed to load commit list.
GitHub Actions / vale completed Jan 31, 2025 in 0s

reviewdog [vale] report

reported by reviewdog 🐶

Findings (15)

content/doc/addons/cellar.md|551 col 5| [Google.Contractions] Use 'what's' instead of 'What is'.
content/doc/addons/cellar.md|555 col 88| [Google.Passive] In general, use active voice instead of passive voice ('is hidden').
content/doc/addons/cellar.md|560 col 18| [Google.Passive] In general, use active voice instead of passive voice ('be enabled').
content/doc/addons/cellar.md|560 col 51| [Google.Passive] In general, use active voice instead of passive voice ('be enabled').
content/doc/addons/cellar.md|563 col 4| [Vale.Spelling] Did you really mean 'Unversioned'?
content/doc/addons/cellar.md|567 col 117| [Vale.Spelling] Did you really mean 'unversioned'?
content/doc/addons/cellar.md|568 col 17| [Google.Passive] In general, use active voice instead of passive voice ('is enabled').
content/doc/addons/cellar.md|570 col 30| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
content/doc/addons/cellar.md|572 col 37| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
content/doc/addons/cellar.md|572 col 72| [Vale.Spelling] Did you really mean 'commande'?
content/doc/addons/cellar.md|580 col 31| [Google.Passive] In general, use active voice instead of passive voice ('is enabled').
content/doc/addons/cellar.md|588 col 17| [Google.Passive] In general, use active voice instead of passive voice ('is enabled').
content/doc/addons/cellar.md|588 col 46| [Google.Will] Avoid using 'will'.
content/doc/addons/cellar.md|600 col 113| [Google.We] Try to avoid using first-person plural like 'we'.
content/doc/addons/cellar.md|621 col 83| [Google.Passive] In general, use active voice instead of passive voice ('are stored').

Filtered Findings (4747)

.github/pull_request_template.md|3 col 66| [Vale.Spelling] Did you really mean 'explicict'?
.github/pull_request_template.md|3 col 107| [Google.Passive] In general, use active voice instead of passive voice ('are needed').
.github/pull_request_template.md|8 col 7| [Google.FirstPerson] Avoid first-person pronouns such as 'My'.
.github/pull_request_template.md|8 col 13| [Google.Passive] In general, use active voice instead of passive voice ('is related').
archetypes/guides.md|17 col 32| [Guides.ellipsis] Include the framework in the title!
content/README.md|4 col 6| [Vale.Spelling] Did you really mean 'repo'?
content/README.md|6 col 6| [Vale.Spelling] Did you really mean 'repo'?
content/README.md|8 col 22| [Vale.Spelling] Did you really mean 'contibuting'?
content/README.md|8 col 57| [Vale.Spelling] Did you really mean 'repo'?
content/_index.md|45 col 100| [Google.Semicolons] Use semicolons judiciously.
content/_index.md|79 col 15| [Vale.Avoid] Avoid using 'addons'.
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 38| [Google.Acronyms] Spell out 'TLS', if it's unfamiliar to the audience.
content/changelog/2023/12-15-sozu-0.15.18.md|20 col 60| [Vale.Spelling] Did you really mean 'Rustls'?
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-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 91| [Google.Acronyms] Spell out 'DNS', if it's unfamiliar to the audience.
content/changelog/2023/12-18-new-par-ip-console.md|17 col 104| [Google.Contractions] Use 'they're' instead of 'They are'.
content/changelog/2023/12-18-php-8-default.md|22 col 8| [Google.We] Try to avoid using first-person plural like 'our'.
content/api/v4.md|12 col 32| [Google.Acronyms] Spell out 'REST', if it's unfamiliar to the audience.
content/api/v4.md|13 col 4| [Google.We] Try to avoid using first-person plural like 'our'.
content/api/v4.md|13 col 26| [Google.We] Try to avoid using first-person plural like 'we'.
content/api/v4.md|21 col 65| [Google.We] Try to avoid using first-person plural like 'our'.
content/api/v4.md|35 col 44| [Google.Acronyms] Spell out 'ISO', if it's unfamiliar to the audience.
content/api/v4.md|36 col 44| [Google.Acronyms] Spell out 'ISO', if it's unfamiliar to the audience.
content/api/v4.md|144 col 44| [Google.Acronyms] Spell out 'ISO', if it's unfamiliar to the audience.
content/api/v4.md|145 col 44| [Google.Acronyms] Spell out 'ISO', if it's unfamiliar to the audience.
content/api/v4.md|197 col 24| [Google.Acronyms] Spell out 'SSE', if it's unfamiliar to the audience.
content/api/v4.md|203 col 44| [Google.Acronyms] Spell out 'ISO', if it's unfamiliar to the audience.
content/api/v4.md|204 col 44| [Google.Acronyms] Spell out 'ISO', if it's unfamiliar to the audience.
content/api/v4.md|208 col 44| [Vale.Spelling] Did you really mean 'systemd'?
content/api/v4.md|240 col 129| [Google.Passive] In general, use active voice instead of passive voice ('are kept').
content/api/v4.md|240 col 181| [Google.Passive] In general, use active voice instead of passive voice ('are kept').
content/api/v4.md|240 col 210| [Vale.Spelling] Did you really mean 'NVMe'?
content/api/v4.md|240 col 215| [Google.Acronyms] Spell out 'SSD', if it's unfamiliar to the audience.
content/api/v4.md|240 col 227| [Google.Passive] In general, use active voice instead of passive voice ('being moved').
content/api/v4.md|240 col 280| [Google.Acronyms] Spell out 'HDD', if it's unfamiliar to the audience.
CONTRIBUTING.md|11 col 106| [Google.Passive] In general, use active voice instead of passive voice ('be merged').
CONTRIBUTING.md|23 col 43| [Google.Passive] In general, use active voice instead of passive voice ('being updated').
CONTRIBUTING.md|40 col 8| [Vale.Spelling] Did you really mean 'Shortcodes'?
CONTRIBUTING.md|42 col 104| [Vale.Spelling] Did you really mean 'shortcodes'?
CONTRIBUTING.md|46 col 4| [Vale.Spelling] Did you really mean 'Callouts'?
CONTRIBUTING.md|46 col 175| [Vale.Spelling] Did you really mean 'callouts'?
CONTRIBUTING.md|46 col 238| [Vale.Spelling] Did you really mean 'callouts'?
CONTRIBUTING.md|53 col 29| [Google.Acronyms] Spell out 'CDN', if it's unfamiliar to the audience.
CONTRIBUTING.md|53 col 97| [Google.Acronyms] Spell out 'CDN', if it's unfamiliar to the audience.
content/api/howto.md|14 col 43| [Google.Passive] In general, use active voice instead of passive voice ('are built').
content/api/howto.md|15 col 62| [Google.Will] Avoid using 'will'.
content/api/howto.md|28 col 1| [Google.We] Try to avoid using first-person plural like 'We'.
content/api/howto.md|28 col 1| [Google.Contractions] Use 'we've' instead of 'We have'.
content/api/howto.md|28 col 118| [Vale.Spelling] Did you really mean 'informations'?
content/api/howto.md|31 col 16| [Google.Passive] In general, use active voice instead of passive voice ('being used').
content/api/howto.md|31 col 30| [Google.We] Try to avoid using first-person plural like 'our'.
content/api/howto.md|31 col 134| [Vale.Spelling] Did you really mean 'devtools'?
content/api/howto.md|47 col 23| [Google.Will] Avoid using 'will'.
content/api/howto.md|49 col 85| [Google.Will] Avoid using 'will'.
content/api/howto.md|54 col 45| [Google.WordList] Use 'URL' instead of 'url'.
content/api/howto.md|54 col 45| [Vale.Spelling] Did you really mean 'url'?
content/api/howto.md|54 col 59| [Google.Will] Avoid using 'will'.
content/api/howto.md|54 col 64| [Google.Passive] In general, use active voice instead of passive voice ('be redirected').
content/api/howto.md|54 col 94| [Google.Passive] In general, use active voice instead of passive voice ('been authenticated').
content/api/howto.md|62 col 150| [Google.Will] Avoid using 'will'.
content/api/howto.md|81 col 25| [Google.Passive] In general, use active voice instead of passive voice ('be complicated').
content/api/howto.md|81 col 41| [Google.We] Try to avoid using first-person plural like 'we'.
content/api/howto.md|81 col 112| [Google.Will] Avoid using 'will'.
content/api/howto.md|87 col 23| [Google.Passive] In general, use active voice instead of passive voice ('are referenced').
content/api/howto.md|110 col 31| [Google.Passive] In general, use active voice instead of passive voice ('is opened').
content/api/howto.md|133 col 1| [Google.OxfordComma] Use the Oxford comma in 'Events like git push, add or'.
[content/changelog/2023/12-22-sozu-wider usage.md|16 col 1|](https://github.com/CleverCloud/documentation/blob/92336265dac6ac68b10d05c421b7f42d193fa534/content/changelog/2023/12-22-sozu-wider usage.md#L16) [Google.We] Try to avoid using first-person plural like 'Our'.
[content/changelog/2023/12-22-sozu-wider usage.md|16 col 44|](https://github.com/CleverCloud/documentation/blob/92336265dac6ac68b10d05c421b7f42d193fa534/content/changelog/2023/12-22-sozu-wider usage.md#L16) [Google.Passive] In general, use active voice instead of passive voice ('be used').
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-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/2024/01-02-pulsar-update.md|17 col 134| [Vale.Spelling] Did you really mean 'namespaces'?
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 56| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2024/01-10-documentation-changelog.md|23 col 96| [Google.Will] Avoid using 'will'.
content/changelog/2024/01-10-documentation-changelog.md|23 col 175| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2024/01-11-redis-7.2.4.md|21 col 4| [Google.Acronyms] Spell out 'CVE', if it's unfamiliar to the audience.
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-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-24-ruby-3.3.0.md|17 col 115| [Google.Passive] In general, use active voice instead of passive voice ('be set').
content/changelog/2024/01-24-ruby-3.3.0.md|22 col 83| [Google.Acronyms] Spell out 'LTS', if it's unfamiliar to the audience.
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/changelog/2024/02-07-clever-tools-3.2.0.md|20 col 188| [Google.We] Try to avoid using first-person plural like 'We'.
content/changelog/2024/02-07-clever-tools-3.2.0.md|22 col 5| [Vale.Spelling] Did you really mean 'api'?
content/changelog/2024/02-07-clever-tools-3.2.0.md|24 col 52| [Google.Units] Put a nonbreaking space between the number and the unit in '28d'.
content/changelog/2024/02-07-clever-tools-3.2.0.md|26 col 24| [Google.Acronyms] Spell out 'SSE', if it's unfamiliar to the audience.
content/changelog/2024/02-07-clever-tools-3.2.0.md|26 col 62| [Google.Passive] In general, use active voice instead of passive voice ('is enabled').
content/changelog/2024/02-08-sozu-0.15.19.md|19 col 1| [Google.We] Try to avoid using first-person plural like 'Our'.
content/changelog/2024/02-08-sozu-0.15.19.md|19 col 78| [Google.We] Try to avoid using first-person plural like 'We'.
content/changelog/2024/02-08-sozu-0.15.19.md|19 col 127| [Vale.Spelling] Did you really mean 'pipelining'?
content/changelog/2024/02-08-sozu-0.15.19.md|19 col 217| [Google.We] Try to avoid using first-person plural like 'We'.
content/changelog/2024/02-08-sozu-0.15.19.md|23 col 1| [Google.We] Try to avoid using first-person plural like 'We'.
content/changelog/2024/02-08-sozu-0.15.19.md|23 col 45| [Vale.Spelling] Did you really mean 'protobuf'?
content/changelog/2024/02-08-sozu-0.15.19.md|23 col 114| [Google.We] Try to avoid using first-person plural like 'We'.
content/changelog/2024/02-08-sozu-0.15.19.md|23 col 225| [Vale.Spelling] Did you really mean 'threadpools'?
content/changelog/2024/02-08-sozu-0.15.19.md|23 col 265| [Google.Passive] In general, use active voice instead of passive voice ('be released').
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, Erlang, 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'?
content/changelog/2024/02-02-images-update.md|28 col 20| [Vale.Spelling] Did you really mean 'erlang'?
content/changelog/2024/02-02-images-update.md|29 col 20| [Vale.Spelling] Did you really mean 'erlang'?
content/changelog/2024/02-02-images-update.md|37 col 14| [Google.Will] Avoid using 'will'.
content/changelog/2024/02-02-images-update.md|37 col 19| [Google.Passive] In general, use active voice instead of passive voice ('be updated').
README.md|10 col 14| [Vale.Spelling] Did you really mean 'Environnement'?
README.md|15 col 38| [Vale.Spelling] Did you really mean 'Nextra'?
README.md|16 col 85| [Google.WordList] Use 'device' instead of 'tablet'.
README.md|16 col 135| [Vale.Spelling] Did you really mean 'accomodate'?
README.md|17 col 157| [Vale.Spelling] Did you really mean 'Javascript'?
README.md|17 col 179| [Google.Passive] In general, use active voice instead of passive voice ('are needed').
README.md|19 col 91| [Vale.Spelling] Did you really mean 'Shortcodes'?
README.md|19 col 155| [Vale.Spelling] Did you really mean 'breadcumbs'?
README.md|20 col 24| [Google.Acronyms] Spell out 'SEO', if it's unfamiliar to the audience.
README.md|20 col 123| [Google.Passive] In general, use active voice instead of passive voice ('is included').
README.md|20 col 139| [Google.Acronyms] Spell out 'SEO', if it's unfamiliar to the audience.
README.md|24 col 16| [Vale.Spelling] Did you really mean 'repo'?
README.md|26 col 83| [Vale.Spelling] Did you really mean 'repo'?
README.md|28 col 38| [Google.WordList] Use 'preceding' instead of 'above'.
README.md|32 col 154| [Vale.Spelling] Did you really mean 'projet's'?
README.md|54 col 21| [Google.Passive] In general, use active voice instead of passive voice ('is called').
README.md|66 col 15| [Vale.Spelling] Did you really mean 'repo'?
README.md|67 col 14| [Vale.Spelling] Did you really mean 'repo'?
README.md|71 col 12| [Google.Passive] In general, use active voice instead of passive voice ('is displayed').
README.md|75 col 12| [Vale.Spelling] Did you really mean 'Goldmak'?
README.md|77 col 88| [Google.Passive] In general, use active voice instead of passive voice ('are linted').
README.md|78 col 1| [Google.We] Try to avoid using first-person plural like 'We'.
README.md|80 col 17| [Google.Passive] In general, use active voice instead of passive voice ('be downloaded').
README.md|83 col 58| [Google.Acronyms] Spell out 'NPM', if it's unfamiliar to the audience.
README.md|87 col 28| [Google.Passive] In general, use active voice instead of passive voice ('are listed').
README.md|88 col 70| [Google.Passive] In general, use active voice instead of passive voice ('are configured').
README.md|99 col 86| [Google.Passive] In general, use active voice instead of passive voice ('is created').
README.md|101 col 21| [Google.Passive] In general, use active voice instead of passive voice ('be made').
README.md|105 col 68| [Google.Passive] In general, use active voice instead of passive voice ('be avoided').
README.md|109 col 14| [Google.Contractions] Use 'isn't' instead of 'is not'.
README.md|109 col 87| [Google.Will] Avoid using 'will'.
README.md|109 col 162| [Google.Acronyms] Spell out 'ISO', if it's unfamiliar to the audience.
README.md|109 col 251| [Google.Passive] In general, use active voice instead of passive voice ('be sorted').
README.md|111 col 44| [Vale.Spelling] Did you really mean 'extention'?
README.md|119 col 125| [Google.WordList] Use 'media type' instead of 'content type'.
README.md|119 col 138| [Google.Latin] Use 'that is' instead of 'i.e.'.
README.md|119 col 176| [Google.We] Try to avoid using first-person plural like 'We'.
README.md|122 col 20| [Google.Will] Avoid using 'will'.
README.md|122 col 25| [Google.Passive] In general, use active voice instead of passive voice ('be displayed').
README.md|125 col 19| [Google.Will] Avoid using 'will'.
README.md|125 col 24| [Google.Passive] In general, use active voice instead of passive voice ('be displayed').
README.md|125 col 75| [Google.Acronyms] Spell out 'ISO', if it's unfamiliar to the audience.
README.md|128 col 26| [Google.Will] Avoid using 'will'.
README.md|128 col 31| [Google.Passive] In general, use active voice instead of passive voice ('be displayed').
README.md|128 col 68| [Google.Acronyms] Spell out 'SEO', if it's unfamiliar to the audience.
README.md|131 col 10| [Google.Passive] In general, use active voice instead of passive voice ('are recommended').
README.md|131 col 59| [Google.Contractions] Use 'they're' instead of 'They are'.
README.md|131 col 64| [Google.Passive] In general, use active voice instead of passive voice ('are written').
README.md|134 col 18| [Google.Passive] In general, use active voice instead of passive voice ('is used').
README.md|134 col 129| [Google.Passive] In general, use active voice instead of passive voice ('be highlighted').
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|137 col 227| [Vale.Spelling] Did you really mean 'Github'?
README.md|140 col 37| [Google.Will] Avoid using 'will'.
README.md|140 col 42| [Google.Passive] In general, use active voice instead of passive voice ('be indexed').
README.md|140 col 71| [Google.Passive] In general, use active voice instead of passive voice ('be activated').
README.md|140 col 130| [Google.Passive] In general, use active voice instead of passive voice ('be set').
README.md|161 col 15| [Google.We] Try to avoid using first-person plural like 'we'.
README.md|161 col 15| [Google.Contractions] Use 'we're' instead of 'we are'.
README.md|163 col 20| [Google.Passive] In general, use active voice instead of passive voice ('be modified').
content/changelog/2024/02-26-healthcheck-for-everyone.md|18 col 52| [Google.Will] Avoid using 'will'.
content/changelog/2024/02-26-healthcheck-for-everyone.md|20 col 156| [Google.Passive] In general, use active voice instead of passive voice ('been validated').
content/changelog/2024/02-26-healthcheck-for-everyone.md|21 col 69| [Google.Passive] In general, use active voice instead of passive voice ('is considered').
content/changelog/2024/02-22-postgresql-pgvector-support.md|23 col 252| [Google.We] Try to avoid using first-person plural like 'we'.
content/changelog/2024/02-22-postgresql-pgvector-support.md|25 col 1| [Google.We] Try to avoid using first-person plural like 'We'.
content/changelog/2024/02-22-postgresql-pgvector-support.md|25 col 48| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2024/02-22-postgresql-pgvector-support.md|25 col 159| [Google.We] Try to avoid using first-person plural like 'we'.
content/changelog/2024/02-22-postgresql-pgvector-support.md|27 col 42| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2024/02-22-postgresql-pgvector-support.md|27 col 202| [Google.We] Try to avoid using first-person plural like 'we'.
content/changelog/2024/02-22-postgresql-pgvector-support.md|27 col 205| [Google.Will] Avoid using 'will'.
content/changelog/2024/02-22-postgresql-pgvector-support.md|27 col 214| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2024/02-22-postgresql-pgvector-support.md|29 col 91| [Vale.Spelling] Did you really mean 'github'?
content/changelog/2024/02-16-clever-tools-3.4.0.md|20 col 12| [Google.We] Try to avoid using first-person plural like 'we'.
content/changelog/2024/02-16-clever-tools-3.4.0.md|20 col 84| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2024/02-16-clever-tools-3.4.0.md|20 col 92| [Vale.Spelling] Did you really mean 'Gravelines'?
content/changelog/2024/02-16-clever-tools-3.4.0.md|20 col 103| [Google.Acronyms] Spell out 'HDS', if it's unfamiliar to the audience.
content/changelog/2024/02-16-clever-tools-3.4.0.md|20 col 172| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2024/02-16-clever-tools-3.4.0.md|22 col 361| [Google.Passive] In general, use active voice instead of passive voice ('is provided').
content/changelog/2024/02-16-clever-tools-3.4.0.md|30 col 62| [Vale.Spelling] Did you really mean 'Gravelines'?
content/changelog/2024/02-16-clever-tools-3.4.0.md|30 col 73| [Google.Acronyms] Spell out 'HDS', if it's unfamiliar to the audience.
content/changelog/2024/02-12-new-grahds-region.md|18 col 146| [Vale.Spelling] Did you really mean 'OVHcloud'?
content/changelog/2024/02-12-new-grahds-region.md|18 col 167| [Google.We] Try to avoid using first-person plural like 'We'.
content/changelog/2024/02-12-new-grahds-region.md|18 col 271| [Vale.Spelling] Did you really mean 'Gravelines'?
content/changelog/2024/02-12-new-grahds-region.md|20 col 22| [Google.We] Try to avoid using first-person plural like 'us'.
content/changelog/2024/02-12-new-grahds-region.md|20 col 37| [Vale.Spelling] Did you really mean 'Gravelines'?
content/changelog/2024/02-12-new-grahds-region.md|20 col 113| [Google.We] Try to avoid using first-person plural like 'we'.
content/changelog/2024/02-12-new-grahds-region.md|22 col 75| [Google.Acronyms] Spell out 'ISO', if it's unfamiliar to the audience.
content/changelog/2024/02-12-new-grahds-region.md|22 col 109| [Google.We] Try to avoid using first-person plural like 'we'.
content/changelog/2024/02-12-new-grahds-region.md|22 col 154| [Google.Acronyms] Spell out 'ISO', if it's unfamiliar to the audience.
content/changelog/2024/02-12-new-grahds-region.md|22 col 204| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2024/02-27-js-client-8.2.0.md|20 col 133| [Google.We] Try to avoid using first-person plural like 'we'.
content/changelog/2024/02-26-mtl-iplb-update.md|21 col 4| [Google.We] Try to avoid using first-person plural like 'we'.
content/changelog/2024/02-26-mtl-iplb-update.md|21 col 20| [Google.We] Try to avoid using first-person plural like 'our'.
content/changelog/2024/02-26-mtl-iplb-update.md|21 col 71| [Google.We] Try to avoid using first-person plural like 'we'.
content/changelog/2024/02-26-mtl-iplb-update.md|21 col 96| [Vale.Spelling] Did you really mean 'IPs'?
content/changelog/2024/02-26-mtl-iplb-update.md|23 col 39| [Google.Acronyms] Spell out 'CNAME', if it's unfamiliar to the audience.
content/changelog/2024/02-26-mtl-iplb-update.md|23 col 66| [Google.Will] Avoid using 'will'.
content/changelog/2024/02-26-mtl-iplb-update.md|23 col 123| [Google.Acronyms] Spell out 'CNAME', if it's unfamiliar to the audience.
content/changelog/2024/02-26-mtl-iplb-update.md|23 col 145| [Google.Acronyms] Spell out 'DNS', if it's unfamiliar to the audience.
content/changelog/2024/02-26-mtl-iplb-update.md|23 col 213| [Vale.Spelling] Did you really mean 'IPs'?
content/changelog/2024/02-26-mtl-iplb-update.md|23 col 217| [Google.Will] Avoid using 'will'.
content/changelog/2024/02-26-mtl-iplb-update.md|23 col 256| [Google.We] Try to avoid using first-person plural like 'we'.
content/changelog/2024/02-26-mtl-iplb-update.md|23 col 288| [Google.Acronyms] Spell out 'DNS', if it's unfamiliar to the audience.
content/changelog/2024/02-26-mtl-iplb-update.md|29 col 3| [Google.Acronyms] Spell out 'CNAME', if it's unfamiliar to the audience.
content/changelog/2024/02-26-mtl-iplb-update.md|30 col 16| [Google.Acronyms] Spell out 'CNAME', if it's unfamiliar to the audience.
content/changelog/2024/02-26-mtl-iplb-update.md|30 col 22| [Google.Contractions] Use 'isn't' instead of 'is not'.
content/changelog/2024/02-26-mtl-iplb-update.md|36 col 3| [Google.Acronyms] Spell out 'CNAME', if it's unfamiliar to the audience.
content/changelog/2024/02-26-mtl-iplb-update.md|37 col 16| [Google.Acronyms] Spell out 'CNAME', if it's unfamiliar to the audience.
... (Too many findings. Dropped some findings)