Skip to content

PBM-1198 Introduced design changes according to the UX prototype #77

PBM-1198 Introduced design changes according to the UX prototype

PBM-1198 Introduced design changes according to the UX prototype #77

GitHub Actions / vale completed Oct 26, 2023 in 1s

reviewdog [vale] report

reported by reviewdog 🐶

Findings (9)

docs/manage/overview.md|3 col 149| [Vale.Spelling] Did you really mean 'followng'?
docs/manage/overview.md|6 col 42| [Google.Parens] Use parentheses judiciously.
docs/404.md|3 col 1| [Google.We] Try to avoid using first-person plural like 'We'.
docs/index.md|21 col 4| [Google.Headings] ':material-progress-download: Installation guides { .title }' should use sentence-style capitalization.
docs/index.md|29 col 5| [Google.Headings] ':material-backup-restore: Backup management { .title }' should use sentence-style capitalization.
docs/index.md|37 col 5| [Google.Headings] ':fontawesome-solid-gears: Administration { .title }' should use sentence-style capitalization.
docs/index.md|44 col 5| [Google.Headings] ':material-frequently-asked-questions: Diagnostics and FAQ { .title }' should use sentence-style capitalization.
docs/index.md|46 col 1| [Google.We] Try to avoid using first-person plural like 'Our'.
docs/index.md|46 col 29| [Google.Will] Avoid using 'will'.

Filtered Findings (1156)

snippets/services-banner.md|7 col 109| [Google.We] Try to avoid using first-person plural like 'our'.
snippets/services-banner.md|11 col 25| [Google.Colons] ': C' should be in lowercase.
snippets/services-banner.md|11 col 151| [Google.Colons] ': G' should be in lowercase.
docs/manage/configure-remotely.md|1 col 3| [Google.Headings] 'Percona Backup for MongoDB configuration via pipelines' should use sentence-style capitalization.
docs/manage/configure-remotely.md|5 col 140| [Google.Parens] Use parentheses judiciously.
docs/manage/configure-remotely.md|7 col 101| [Google.Acronyms] Spell out 'UNIX', if it's unfamiliar to the audience.
docs/manage/configure-remotely.md|11 col 1| [Google.Parens] Use parentheses judiciously.
docs/manage/configure-remotely.md|34 col 98| [Google.Will] Avoid using 'will'.
docs/manage/configure-remotely.md|36 col 19| [Vale.Spelling] Did you really mean 'DBAs'?
docs/manage/uninstalling.md|9 col 70| [Google.Contractions] Use 'it's' instead of 'it is'.
docs/manage/uninstalling.md|9 col 114| [Google.Will] Avoid using 'will'.
docs/manage/uninstalling.md|9 col 159| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/manage/uninstalling.md|9 col 166| [Vale.Spelling] Did you really mean 'aws'?
docs/manage/uninstalling.md|9 col 197| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/manage/uninstalling.md|9 col 269| [Google.Passive] In general, use active voice instead of passive voice ('is uninstalled').
docs/manage/uninstalling.md|9 col 340| [Google.Contractions] Use 'they're' instead of 'they are'.
docs/manage/uninstalling.md|9 col 345| [Google.Passive] In general, use active voice instead of passive voice ('are deleted').
docs/manage/uninstalling.md|16 col 77| [Google.Will] Avoid using 'will'.
docs/manage/uninstalling.md|17 col 9| [Google.Passive] In general, use active voice instead of passive voice ('be run').
docs/manage/uninstalling.md|19 col 4| [Google.Parens] Use parentheses judiciously.
docs/install/repos.md|21 col 69| [Google.Passive] In general, use active voice instead of passive voice ('are stored').
docs/manage/upgrading.md|7 col 59| [Google.Passive] In general, use active voice instead of passive voice ('is supported').
docs/manage/upgrading.md|7 col 259| [Google.We] Try to avoid using first-person plural like 'we'.
docs/manage/upgrading.md|11 col 67| [Google.Passive] In general, use active voice instead of passive voice ('is changed').
docs/manage/upgrading.md|11 col 107| [Google.Passive] In general, use active voice instead of passive voice ('is done').
docs/manage/upgrading.md|17 col 69| [Google.Passive] In general, use active voice instead of passive voice ('are stored').
docs/manage/upgrading.md|19 col 58| [Google.Contractions] Use 'it's' instead of 'it is'.
docs/manage/upgrading.md|19 col 61| [Google.Passive] In general, use active voice instead of passive voice ('is installed').
docs/install/source.md|7 col 14| [Google.WordList] Use 'preceding' instead of 'above'.
docs/install/source.md|10 col 105| [Google.Passive] In general, use active voice instead of passive voice ('is required').
docs/install/source.md|41 col 45| [Google.Passive] In general, use active voice instead of passive voice ('been built').
docs/install/cloud.md|1 col 3| [Google.Headings] 'Deploy Percona Backup for MongoDB on Kubernetes' should use sentence-style capitalization.
docs/manage/automate-s3-access.md|3 col 59| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|3 col 73| [Google.Parens] Use parentheses judiciously.
docs/manage/automate-s3-access.md|3 col 100| [Google.Acronyms] Spell out 'EKS', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|3 col 133| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|3 col 216| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|5 col 4| [Google.Headings] 'IAM instance profile' should use sentence-style capitalization.
docs/manage/automate-s3-access.md|5 col 4| [Google.Acronyms] Spell out 'IAM', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|9 col 1| [Google.Acronyms] Spell out 'IAM', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|9 col 5| [Google.Parens] Use parentheses judiciously.
docs/manage/automate-s3-access.md|9 col 41| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|9 col 99| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|11 col 11| [Google.Acronyms] Spell out 'IAM', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|13 col 16| [Google.Acronyms] Spell out 'IAM', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|15 col 15| [Google.Acronyms] Spell out 'IAM', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|41 col 4| [Google.Headings] 'IAM Roles for Service Accounts (IRSA)' should use sentence-style capitalization.
docs/manage/automate-s3-access.md|41 col 4| [Google.Acronyms] Spell out 'IAM', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|41 col 35| [Google.Parens] Use parentheses judiciously.
docs/manage/automate-s3-access.md|45 col 116| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|45 col 120| [Google.Acronyms] Spell out 'EKS', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|45 col 124| [Google.Parens] Use parentheses judiciously.
docs/manage/automate-s3-access.md|45 col 193| [Google.Acronyms] Spell out 'EKS', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|45 col 216| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|45 col 256| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|45 col 260| [Google.Acronyms] Spell out 'IAM', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|47 col 27| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|49 col 137| [Google.Acronyms] Spell out 'OIDC', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|49 col 190| [Google.Acronyms] Spell out 'EKS', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|49 col 220| [Google.WordList] Use 'preceding' instead of 'above'.
docs/manage/automate-s3-access.md|50 col 14| [Google.Acronyms] Spell out 'IAM', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|51 col 54| [Google.Acronyms] Spell out 'IAM', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|52 col 96| [Google.Acronyms] Spell out 'IAM', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|53 col 235| [Google.Parens] Use parentheses judiciously.
docs/manage/automate-s3-access.md|53 col 236| [Google.Latin] Use 'that is' instead of 'i.e.'.
docs/manage/automate-s3-access.md|53 col 297| [Google.Acronyms] Spell out 'EKS', if it's unfamiliar to the audience.
docs/manage/automate-s3-access.md|69 col 7| [Google.Colons] ': E' should be in lowercase.
docs/manage/automate-s3-access.md|69 col 25| [Google.WordList] Use 'Google Cloud Platform' or 'GCP' instead of 'Cloud'.
docs/manage/automate-s3-access.md|70 col 7| [Google.Colons] ': E' should be in lowercase.
docs/manage/automate-s3-access.md|71 col 7| [Google.Colons] ': I' should be in lowercase.
docs/manage/automate-s3-access.md|72 col 8| [Google.Colons] ': I' should be in lowercase.
docs/manage/automate-s3-access.md|72 col 10| [Google.Acronyms] Spell out 'IAM', if it's unfamiliar to the audience.
docs/install/tarball.md|1 col 3| [Google.Headings] 'Download Percona Backup for MongoDB from Percona website' should use sentence-style capitalization.
docs/install/tarball.md|6 col 1| [Google.Parens] Use parentheses judiciously.
docs/install/tarball.md|6 col 175| [Google.Passive] In general, use active voice instead of passive voice ('are satisfied').
CONTRIBUTING.md|3 col 39| [Google.Exclamation] Don't use exclamation points in text.
CONTRIBUTING.md|5 col 1| [Google.We] Try to avoid using first-person plural like 'We'.
CONTRIBUTING.md|15 col 42| [Google.Passive] In general, use active voice instead of passive voice ('is written').
CONTRIBUTING.md|27 col 27| [Google.WordList] Use 'select' instead of 'check'.
CONTRIBUTING.md|35 col 294| [Google.Spacing] 'e. T' should have one space.
CONTRIBUTING.md|36 col 17| [Google.We] Try to avoid using first-person plural like 'our'.
CONTRIBUTING.md|70 col 103| [Vale.Spelling] Did you really mean 'repo'?
CONTRIBUTING.md|71 col 37| [Google.Parens] Use parentheses judiciously.
CONTRIBUTING.md|71 col 52| [Vale.Spelling] Did you really mean 'VSCode'?
CONTRIBUTING.md|71 col 118| [Google.WordList] Use 'select' instead of 'check'.
CONTRIBUTING.md|71 col 137| [Google.Passive] In general, use active voice instead of passive voice ('is rendered').
CONTRIBUTING.md|72 col 128| [Google.Will] Avoid using 'will'.
CONTRIBUTING.md|78 col 96| [Google.Passive] In general, use active voice instead of passive voice ('is called').
CONTRIBUTING.md|86 col 4| [Google.We] Try to avoid using first-person plural like 'We'.
CONTRIBUTING.md|86 col 12| [Google.We] Try to avoid using first-person plural like 'our'.
CONTRIBUTING.md|127 col 6| [Google.Headings] 'PDF' should use sentence-style capitalization.
CONTRIBUTING.md|146 col 28| [Google.Passive] In general, use active voice instead of passive voice ('is merged').
CONTRIBUTING.md|148 col 24| [Google.Passive] In general, use active voice instead of passive voice ('is merged').
CONTRIBUTING.md|148 col 101| [Google.Exclamation] Don't use exclamation points in text.
CONTRIBUTING.md|159 col 35| [Vale.Spelling] Did you really mean 'favicons'?
CONTRIBUTING.md|161 col 12| [Vale.Spelling] Did you really mean 'Javascript'?
CONTRIBUTING.md|168 col 48| [Google.Passive] In general, use active voice instead of passive voice ('are put').
docs/install/docker.md|1 col 3| [Google.Headings] 'Run Percona Backup for MongoDB in a Docker container' should use sentence-style capitalization.
docs/install/docker.md|3 col 45| [Google.Passive] In general, use active voice instead of passive voice ('are hosted').
docs/install/docker.md|26 col 151| [Google.Parens] Use parentheses judiciously.
docs/install/docker.md|46 col 135| [Vale.Spelling] Did you really mean 'storages'?
docs/install/docker.md|46 col 144| [Google.Passive] In general, use active voice instead of passive voice ('are supported').
docs/install/docker.md|67 col 1| [Google.Parens] Use parentheses judiciously.
docs/features/comparison.md|8 col 26| [Google.Parens] Use parentheses judiciously.
docs/features/comparison.md|11 col 22| [Google.Parens] Use parentheses judiciously.
docs/features/comparison.md|12 col 72| [Google.Acronyms] Spell out 'PMM', if it's unfamiliar to the audience.
docs/features/comparison.md|12 col 178| [Google.WordList] Use 'Google Cloud Platform' or 'GCP' instead of 'Cloud'.
docs/features/comparison.md|22 col 1| [Google.LyHyphens] ' locally-' doesn't need a hyphen.
docs/features/selective-backup.md|9 col 143| [Google.Passive] In general, use active voice instead of passive voice ('was corrupted').
docs/features/selective-backup.md|9 col 314| [Google.Passive] In general, use active voice instead of passive voice ('be backed').
docs/features/selective-backup.md|13 col 39| [Google.WordList] Use 'capability' or 'feature' instead of 'functionality'.
docs/features/selective-backup.md|20 col 4| [Google.Headings] 'Sharded collections' should use sentence-style capitalization.
docs/features/selective-backup.md|28 col 186| [Google.Passive] In general, use active voice instead of passive voice ('are ignored').
docs/features/selective-backup.md|31 col 49| [Google.Contractions] Use 'isn't' instead of 'is not'.
docs/features/selective-backup.md|33 col 147| [Google.Passive] In general, use active voice instead of passive voice ('are ignored').
docs/features/selective-backup.md|33 col 171| [Google.We] Try to avoid using first-person plural like 'we'.
docs/features/selective-backup.md|37 col 64| [Google.Passive] In general, use active voice instead of passive voice ('is set').
docs/features/selective-backup.md|37 col 246| [Google.Will] Avoid using 'will'.
docs/features/selective-backup.md|37 col 251| [Google.Passive] In general, use active voice instead of passive voice ('be set').
docs/features/selective-backup.md|37 col 353| [Google.Will] Avoid using 'will'.
docs/features/selective-backup.md|37 col 358| [Google.Passive] In general, use active voice instead of passive voice ('be restored').
docs/features/selective-backup.md|37 col 374| [Google.Semicolons] Use semicolons judiciously.
docs/features/selective-backup.md|37 col 390| [Google.Will] Avoid using 'will'.
docs/features/selective-backup.md|37 col 390| [Google.Contractions] Use 'won't' instead of 'will not'.
docs/features/selective-backup.md|37 col 399| [Google.Passive] In general, use active voice instead of passive voice ('be deleted').
docs/features/selective-backup.md|37 col 447| [Google.Parens] Use parentheses judiciously.
docs/features/selective-backup.md|42 col 42| [Google.Passive] In general, use active voice instead of passive voice ('are supported').
docs/features/selective-backup.md|43 col 35| [Google.Passive] In general, use active voice instead of passive voice ('are supported').
docs/features/selective-backup.md|43 col 146| [Google.Passive] In general, use active voice instead of passive voice ('are supported').
docs/features/selective-backup.md|44 col 36| [Google.Contractions] Use 'aren't' instead of 'are not'.
docs/features/selective-backup.md|45 col 24| [Google.Contractions] Use 'aren't' instead of 'are not'.
docs/features/selective-backup.md|45 col 129| [Google.Parens] Use parentheses judiciously.
docs/features/selective-backup.md|45 col 130| [Google.Latin] Use 'for example' instead of 'e.g.'.
docs/features/selective-backup.md|46 col 34| [Google.Contractions] Use 'aren't' instead of 'are not'.
docs/features/selective-backup.md|47 col 73| [Google.Contractions] Use 'can't' instead of 'cannot'.
docs/features/selective-backup.md|47 col 80| [Google.Passive] In general, use active voice instead of passive voice ('be backed').
docs/features/selective-backup.md|48 col 37| [Google.Contractions] Use 'isn't' instead of 'is not'.
docs/install/initial-setup.md|3 col 107| [Google.Contractions] Use 'that's' instead of 'that is'.
docs/install/initial-setup.md|15 col 4| [Google.Headings] 'Configure authentication in MongoDB' should use sentence-style capitalization.
docs/install/initial-setup.md|57 col 142| [Google.WordList] Use 'preceding' instead of 'above'.
docs/install/initial-setup.md|57 col 148| [Google.Passive] In general, use active voice instead of passive voice ('are granted').
docs/install/initial-setup.md|79 col 1| [Google.Parens] Use parentheses judiciously.
docs/install/initial-setup.md|79 col 104| [Vale.Spelling] Did you really mean 'systemd'?
docs/install/initial-setup.md|81 col 25| [Vale.Spelling] Did you really mean 'systemd'?
docs/install/initial-setup.md|133 col 302| [Google.Passive] In general, use active voice instead of passive voice ('be passed').
docs/install/initial-setup.md|157 col 16| [Google.Acronyms] Spell out 'SCRAM', if it's unfamiliar to the audience.
docs/install/initial-setup.md|161 col 239| [Google.Latin] Use 'for example' instead of 'e.g.'.
docs/install/initial-setup.md|161 col 261| [Google.Acronyms] Spell out 'COM', if it's unfamiliar to the audience.
docs/install/initial-setup.md|175 col 45| [Google.Will] Avoid using 'will'.
docs/install/initial-setup.md|177 col 50| [Google.Acronyms] Spell out 'LDAP', if it's unfamiliar to the audience.
docs/install/initial-setup.md|177 col 220| [Google.Acronyms] Spell out 'LDAP', if it's unfamiliar to the audience.
docs/install/initial-setup.md|177 col 256| [Google.Passive] In general, use active voice instead of passive voice ('are stored').
docs/install/initial-setup.md|177 col 286| [Google.Acronyms] Spell out 'LDAP', if it's unfamiliar to the audience.
docs/install/initial-setup.md|183 col 13| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/install/initial-setup.md|183 col 17| [Google.Acronyms] Spell out 'IAM', if it's unfamiliar to the audience.
docs/install/initial-setup.md|183 col 126| [Google.Acronyms] Spell out 'ARN', if it's unfamiliar to the audience.
docs/install/initial-setup.md|183 col 137| [Google.Acronyms] Spell out 'IAM', if it's unfamiliar to the audience.
docs/install/initial-setup.md|204 col 4| [Google.Headings] 'Configure remote backup storage' should use sentence-style capitalization.
docs/install/initial-setup.md|208 col 75| [Google.We] Try to avoid using first-person plural like 'We'.
docs/install/initial-setup.md|208 col 145| [Vale.Spelling] Did you really mean 'storages'?
docs/install/initial-setup.md|211 col 1| [Google.Parens] Use parentheses judiciously.
docs/install/initial-setup.md|211 col 26| [Google.Latin] Use 'for example' instead of 'e.g.'.
docs/install/initial-setup.md|215 col 58| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/install/initial-setup.md|263 col 122| [Google.Parens] Use parentheses judiciously.
docs/install/initial-setup.md|267 col 69| [Google.Contractions] Use 'it's' instead of 'It is'.
docs/install/initial-setup.md|274 col 275| [Google.Latin] Use 'for example' instead of 'e.g.'.
docs/install/initial-setup.md|274 col 361| [Google.Latin] Use 'for example' instead of 'e.g.'.
docs/install/initial-setup.md|277 col 8| [Google.Passive] In general, use active voice instead of passive voice ('is redirected').
docs/install/initial-setup.md|277 col 48| [Google.Passive] In general, use active voice instead of passive voice ('is backgrounded').
docs/install/initial-setup.md|277 col 51| [Vale.Spelling] Did you really mean 'backgrounded'?
docs/install/initial-setup.md|287 col 130| [Google.Will] Avoid using 'will'.
docs/install/initial-setup.md|287 col 135| [Google.Passive] In general, use active voice instead of passive voice ('be written').
docs/install/initial-setup.md|293 col 65| [Google.Passive] In general, use active voice instead of passive voice ('is captured').
docs/install/initial-setup.md|306 col 66| [Vale.Spelling] Did you really mean 'stdout'?
docs/install/initial-setup.md|306 col 77| [Vale.Spelling] Did you really mean 'stderr'?
docs/install/initial-setup.md|308 col 58| [Google.Passive] In general, use active voice instead of passive voice ('is printed').
docs/features/logical.md|5 col 39| [Google.Colons] ': T' should be in lowercase.
docs/features/backup-types.md|13 col 107| [Google.Parens] Use parentheses judiciously.
docs/features/backup-types.md|14 col 139| [Google.Parens] Use parentheses judiciously.
docs/features/backup-types.md|14 col 219| [Google.Contractions] Use 'aren't' instead of 'are not'.
docs/features/backup-types.md|15 col 53| [Google.Parens] Use parentheses judiciously.
docs/features/backup-types.md|15 col 68| [Google.Acronyms] Spell out 'PSMDB', if it's unfamiliar to the audience.
docs/features/backup-types.md|16 col 68| [Google.Parens] Use parentheses judiciously.
docs/features/incremental-backup.md|7 col 337| [Google.Passive] In general, use active voice instead of passive voice ('are required').
docs/features/incremental-backup.md|9 col 5| [Google.We] Try to avoid using first-person plural like 'We'.
docs/features/incremental-backup.md|11 col 37| [Google.Passive] In general, use active voice instead of passive voice ('is based').
docs/features/incremental-backup.md|11 col 165| [Google.Contractions] Use 'that's' instead of 'that is'.
docs/features/incremental-backup.md|12 col 23| [Google.Passive] In general, use active voice instead of passive voice ('are supported').
docs/features/incremental-backup.md|13 col 58| [Google.Parens] Use parentheses judiciously.
docs/features/incremental-backup.md|13 col 181| [Google.Passive] In general, use active voice instead of passive voice ('is opened').
docs/features/incremental-backup.md|13 col 212| [Google.Contractions] Use 'aren't' instead of 'are not'.
docs/features/incremental-backup.md|13 col 246| [Google.Passive] In general, use active voice instead of passive voice ('is configured').
docs/features/incremental-backup.md|17 col 81| [Google.Passive] In general, use active voice instead of passive voice ('was changed').
docs/features/incremental-backup.md|17 col 119| [Google.Passive] In general, use active voice instead of passive voice ('was taken').
docs/features/incremental-backup.md|28 col 105| [Google.Passive] In general, use active voice instead of passive voice ('was taken').
docs/features/incremental-backup.md|28 col 175| [Google.Passive] In general, use active voice instead of passive voice ('be run').
docs/usage/describe-backup.md|9 col 1| [Google.OxfordComma] Use the Oxford comma in 'The output provides the backup name, type, status, size and'.
docs/usage/describe-backup.md|9 col 107| [Google.Passive] In general, use active voice instead of passive voice ('was taken').
docs/usage/describe-backup.md|9 col 213| [Google.Passive] In general, use active voice instead of passive voice ('were backed').
docs/usage/list-backup.md|20 col 66| [Google.Will] Avoid using 'will'.
docs/usage/list-backup.md|20 col 71| [Google.Passive] In general, use active voice instead of passive voice ('be returned').
docs/usage/list-backup.md|21 col 70| [Google.Passive] In general, use active voice instead of passive voice ('is enabled').
docs/usage/restore-progress.md|7 col 240| [Google.Passive] In general, use active voice instead of passive voice ('are shut').
docs/usage/restore-progress.md|16 col 51| [Google.Passive] In general, use active voice instead of passive voice ('was restored').
docs/usage/restore-progress.md|21 col 24| [Google.EmDash] Don't put a space before or after a dash.
docs/usage/restore-progress.md|21 col 25| [Google.EnDash] Use an em dash ('—') instead of '–'.
docs/usage/restore-progress.md|24 col 65| [Google.Passive] In general, use active voice instead of passive voice ('is provided').
docs/usage/restore-progress.md|30 col 83| [Google.Contractions] Use 'isn't' instead of 'is not'.
docs/usage/restore-progress.md|30 col 104| [Google.WordList] Use 'select' instead of 'check'.
docs/usage/restore-progress.md|32 col 68| [Google.Passive] In general, use active voice instead of passive voice ('is printed').
docs/features/physical.md|8 col 14| [Google.Passive] In general, use active voice instead of passive voice ('is used').
docs/features/physical.md|8 col 223| [Google.WordList] Use 'capability' or 'feature' instead of 'functionality'.
docs/features/physical.md|25 col 85| [Vale.Repetition] 'the' is repeated!
docs/features/physical.md|25 col 184| [Google.Passive] In general, use active voice instead of passive voice ('are saved').
docs/features/physical.md|25 col 284| [Google.Passive] In general, use active voice instead of passive voice ('is deleted').
docs/features/physical.md|27 col 228| [Google.Parens] Use parentheses judiciously.
docs/features/physical.md|31 col 298| [Google.Passive] In general, use active voice instead of passive voice ('are required').
docs/features/physical.md|40 col 94| [Google.Parens] Use parentheses judiciously.
docs/features/physical.md|40 col 95| [Google.Acronyms] Spell out 'PSMDB', if it's unfamiliar to the audience.
docs/features/physical.md|40 col 174| [Google.Acronyms] Spell out 'PSMDB', if it's unfamiliar to the audience.
docs/features/physical.md|42 col 1| [Google.OxfordComma] Use the Oxford comma in 'You can make a physical, incremental or'.
docs/features/physical.md|44 col 1| [Google.OxfordComma] Use the Oxford comma in 'Physical, incremental and'.
docs/features/physical.md|44 col 73| [Google.Acronyms] Spell out 'PSMDB', if it's unfamiliar to the audience.
docs/features/physical.md|44 col 112| [Google.Passive] In general, use active voice instead of passive voice ('is based').
docs/features/physical.md|44 col 231| [Google.WordList] Use 'capability' or 'feature' instead of 'functionality'.
docs/features/physical.md|44 col 296| [Google.Acronyms] Spell out 'PSMDB', if it's unfamiliar to the audience.
docs/features/physical.md|44 col 339| [Google.Acronyms] Spell out 'PSMDB', if it's unfamiliar to the audience.
docs/features/physical.md|48 col 77| [Google.Colons] ': B' should be in lowercase.
docs/features/physical.md|49 col 167| [Google.Contractions] Use 'it's' instead of 'it is'.
docs/features/physical.md|57 col 143| [Google.Acronyms] Spell out 'GDPR', if it's unfamiliar to the audience.
docs/features/physical.md|57 col 149| [Google.Acronyms] Spell out 'HIPAA', if it's unfamiliar to the audience.
docs/features/physical.md|57 col 156| [Google.Acronyms] Spell out 'PCI', if it's unfamiliar to the audience.
docs/features/physical.md|57 col 160| [Google.Acronyms] Spell out 'DSS', if it's unfamiliar to the audience.
docs/features/physical.md|57 col 168| [Google.Acronyms] Spell out 'PHI', if it's unfamiliar to the audience.
docs/features/physical.md|61 col 253| [Google.Contractions] Use 'isn't' instead of 'is not'.
docs/features/physical.md|67 col 430| [Google.Passive] In general, use active voice instead of passive voice ('been improved').
docs/features/physical.md|71 col 166| [Google.We] Try to avoid using first-person plural like 'we'.
docs/features/physical.md|76 col 4| [Google.Acronyms] Spell out 'KMIP', if it's unfamiliar to the audience.
docs/features/physical.md|80 col 196| [Google.Contractions] Use 'isn't' instead of 'is not'.
docs/features/physical.md|86 col 149| [Google.Passive] In general, use active voice instead of passive voice ('was encrypted').
docs/features/physical.md|86 col 180| [Google.Contractions] Use 'aren't' instead of 'are not'.
docs/features/point-in-time-recovery.md|28 col 161| [Google.Passive] In general, use active voice instead of passive voice ('is used').
docs/features/point-in-time-recovery.md|35 col 98| [Google.Passive] In general, use active voice instead of passive voice ('be met').
docs/features/point-in-time-recovery.md|65 col 106| [Google.Passive] In general, use active voice instead of passive voice ('is disabled').
docs/features/point-in-time-recovery.md|65 col 109| [Google.WordList] Use 'turn off' or 'off' instead of 'disabled'.
docs/features/point-in-time-recovery.md|67 col 96| [Google.Parens] Use parentheses judiciously.
docs/features/point-in-time-recovery.md|82 col 93| [Google.Passive] In general, use active voice instead of passive voice ('is updated').
docs/features/point-in-time-recovery.md|90 col 18| [Google.Passive] In general, use active voice instead of passive voice ('are saved').
docs/features/point-in-time-recovery.md|109 col 82| [Google.Will] Avoid using 'will'.
docs/features/point-in-time-recovery.md|117 col 18| [Google.Passive] In general, use active voice instead of passive voice ('are stored').
docs/features/point-in-time-recovery.md|121 col 1| [Google.Parens] Use parentheses judiciously.
docs/usage/schedule-backup.md|3 col 1| [Google.We] Try to avoid using first-person plural like 'We'.
docs/usage/schedule-backup.md|15 col 238| [Google.We] Try to avoid using first-person plural like 'we'.
docs/usage/schedule-backup.md|43 col 58| [Google.Will] Avoid using 'will'.
docs/usage/schedule-backup.md|71 col 1| [Google.Contractions] Use 'it's' instead of 'It is'.
docs/usage/schedule-backup.md|73 col 111| [Google.Will] Avoid using 'will'.
docs/usage/schedule-backup.md|73 col 170| [Google.Passive] In general, use active voice instead of passive voice ('been made').
docs/usage/schedule-backup.md|75 col 37| [Google.Will] Avoid using 'will'.
docs/usage/schedule-backup.md|79 col 6| [Google.Contractions] Use 'it's' instead of 'it is'.
docs/usage/schedule-backup.md|83 col 18| [Google.Contractions] Use 'aren't' instead of 'are not'.
docs/usage/cancel-backup.md|13 col 41| [Google.Passive] In general, use active voice instead of passive voice ('is marked').
docs/features/snapshots.md|11 col 149| [Google.Passive] In general, use active voice instead of passive voice ('are stored').
docs/features/snapshots.md|17 col 25| [Google.EmDash] Don't put a space before or after a dash.
docs/features/snapshots.md|18 col 16| [Google.EmDash] Don't put a space before or after a dash.
docs/features/snapshots.md|19 col 34| [Google.EmDash] Don't put a space before or after a dash.
docs/features/snapshots.md|21 col 122| [Google.Passive] In general, use active voice instead of passive voice ('are planned').
docs/features/snapshots.md|47 col 4| [Google.Parens] Use parentheses judiciously.
docs/features/snapshots.md|47 col 23| [Google.WordList] Use 'select' instead of 'check'.
docs/features/snapshots.md|61 col 92| [Google.WordList] Use 'turn off' or 'off' instead of 'disable'.
docs/features/snapshots.md|83 col 34| [Google.Passive] In general, use active voice instead of passive voice ('is made').
docs/features/snapshots.md|91 col 179| [Google.Passive] In general, use active voice instead of passive voice ('is restored').
docs/features/snapshots.md|103 col 33| [Vale.Spelling] Did you really mean 'resync'?
docs/features/snapshots.md|121 col 101| [Google.Passive] In general, use active voice instead of passive voice ('was made').
docs/features/snapshots.md|144 col 53| [Google.Passive] In general, use active voice instead of passive voice ('is undefined').
docs/features/snapshots.md|146 col 36| [Google.Passive] In general, use active voice instead of passive voice ('is undefined').
docs/usage/oplog-replay.md|6 col 1| [Google.Parens] Use parentheses judiciously.
docs/usage/oplog-replay.md|6 col 153| [Google.Acronyms] Spell out 'EBS', if it's unfamiliar to the audience.
docs/usage/oplog-replay.md|6 col 350| [Google.Passive] In general, use active voice instead of passive voice ('is controlled').
docs/usage/oplog-replay.md|44 col 89| [Google.Passive] In general, use active voice instead of passive voice ('is done').
docs/usage/oplog-replay.md|46 col 25| [Google.Passive] In general, use active voice instead of passive voice ('are saved').
... (Too many findings. Dropped some findings)

Annotations

Check failure on line 3 in docs/manage/overview.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] docs/manage/overview.md#L3

[Vale.Spelling] Did you really mean 'followng'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'followng'?", "location": {"path": "docs/manage/overview.md", "range": {"start": {"line": 3, "column": 149}}}, "severity": "ERROR"}

Check notice on line 6 in docs/manage/overview.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] docs/manage/overview.md#L6

[Google.Parens] Use parentheses judiciously.
Raw output
{"message": "[Google.Parens] Use parentheses judiciously.", "location": {"path": "docs/manage/overview.md", "range": {"start": {"line": 6, "column": 42}}}, "severity": "INFO"}

Check warning on line 3 in docs/404.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] docs/404.md#L3

[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": "docs/404.md", "range": {"start": {"line": 3, "column": 1}}}, "severity": "WARNING"}

Check warning on line 21 in docs/index.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] docs/index.md#L21

[Google.Headings] ':material-progress-download: Installation guides { .title }' should use sentence-style capitalization.
Raw output
{"message": "[Google.Headings] ':material-progress-download: Installation guides { .title }' should use sentence-style capitalization.", "location": {"path": "docs/index.md", "range": {"start": {"line": 21, "column": 4}}}, "severity": "WARNING"}

Check warning on line 29 in docs/index.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] docs/index.md#L29

[Google.Headings] ':material-backup-restore: Backup management { .title }' should use sentence-style capitalization.
Raw output
{"message": "[Google.Headings] ':material-backup-restore: Backup management { .title }' should use sentence-style capitalization.", "location": {"path": "docs/index.md", "range": {"start": {"line": 29, "column": 5}}}, "severity": "WARNING"}

Check warning on line 37 in docs/index.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] docs/index.md#L37

[Google.Headings] ':fontawesome-solid-gears: Administration { .title }' should use sentence-style capitalization.
Raw output
{"message": "[Google.Headings] ':fontawesome-solid-gears: Administration { .title }' should use sentence-style capitalization.", "location": {"path": "docs/index.md", "range": {"start": {"line": 37, "column": 5}}}, "severity": "WARNING"}

Check warning on line 44 in docs/index.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] docs/index.md#L44

[Google.Headings] ':material-frequently-asked-questions: Diagnostics and FAQ { .title }' should use sentence-style capitalization.
Raw output
{"message": "[Google.Headings] ':material-frequently-asked-questions: Diagnostics and FAQ { .title }' should use sentence-style capitalization.", "location": {"path": "docs/index.md", "range": {"start": {"line": 44, "column": 5}}}, "severity": "WARNING"}

Check warning on line 46 in docs/index.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] docs/index.md#L46

[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": "docs/index.md", "range": {"start": {"line": 46, "column": 1}}}, "severity": "WARNING"}

Check warning on line 46 in docs/index.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] docs/index.md#L46

[Google.Will] Avoid using 'will'.
Raw output
{"message": "[Google.Will] Avoid using 'will'.", "location": {"path": "docs/index.md", "range": {"start": {"line": 46, "column": 29}}}, "severity": "WARNING"}