docs/install/docker.md|15 col 91| [Google.Passive] In general, use active voice instead of passive voice ('are supported').
docs/install/docker.md|16 col 87| [Google.Will] Avoid using 'will'.
docs/install/docker.md|31 col 157| [Google.Parens] Use parentheses judiciously.
docs/install/docker.md|45 col 57| [Google.We] Try to avoid using first-person plural like 'let's'.
docs/install/docker.md|57 col 135| [Vale.Spelling] Did you really mean 'storages'?
docs/install/docker.md|57 col 144| [Google.Passive] In general, use active voice instead of passive voice ('are supported').

_resource/includes/abbreviations.md|2 col 7| [Google.Colons] ': S' should be in lowercase.
_resource/includes/abbreviations.md|3 col 6| [Google.Colons] ': G' should be in lowercase.
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/manage/status.md|1 col 3| [Google.Headings] 'Percona Backup for MongoDB status' should use sentence-style capitalization.
docs/manage/status.md|5 col 9| [Google.WordList] Use 'select' instead of 'check'.
docs/manage/status.md|13 col 92| [Google.Passive] In general, use active voice instead of passive voice ('is connected').
docs/manage/status.md|17 col 94| [Google.Parens] Use parentheses judiciously.
docs/manage/status.md|19 col 74| [Google.Parens] Use parentheses judiciously.
docs/manage/status.md|19 col 86| [Google.WordList] Use 'turn off' or 'off' instead of 'disabled'.
docs/manage/status.md|23 col 61| [Google.Passive] In general, use active voice instead of passive voice ('is provided').
README.md|1 col 3| [Google.Headings] 'Percona Backup for MongoDB documentation' should use sentence-style capitalization.
README.md|4 col 39| [Google.Exclamation] Don't use exclamation points in text.
README.md|13 col 161| [Google.Passive] In general, use active voice instead of passive voice ('is written').
README.md|13 col 257| [Google.Passive] In general, use active voice instead of passive voice ('is created').
README.md|17 col 1| [Google.We] Try to avoid using first-person plural like 'We'.
README.md|21 col 9| [Google.Passive] In general, use active voice instead of passive voice ('is dedicated').
README.md|21 col 74| [Google.We] Try to avoid using first-person plural like 'we'.
README.md|21 col 125| [Google.We] Try to avoid using first-person plural like 'our'.
README.md|21 col 175| [Google.We] Try to avoid using first-person plural like 'we'.
README.md|21 col 175| [Google.Contractions] Use 'we're' instead of 'we are'.
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/copyright.md|5 col 45| [Google.Parens] Use parentheses judiciously.
docs/copyright.md|5 col 66| [Google.Acronyms] Spell out 'LLC', if it's unfamiliar to the audience.
docs/copyright.md|6 col 5| [Google.Passive] In general, use active voice instead of passive voice ('is distributed').
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/release-notes.md|1 col 3| [Google.Headings] 'Percona Backup for MongoDB release notes' 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.Acronyms] Spell out 'IAM', 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|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/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/manage/troubleshooting.md|1 col 3| [Google.Headings] 'Percona Backup for MongoDB diagnostics tools' should use sentence-style capitalization.
docs/manage/troubleshooting.md|9 col 6| [Google.WordList] Use 'select' instead of 'check'.
docs/manage/troubleshooting.md|33 col 49| [Google.Parens] Use parentheses judiciously.
docs/manage/troubleshooting.md|75 col 53| [Google.Parens] Use parentheses judiciously.
docs/manage/troubleshooting.md|103 col 124| [Google.Passive] In general, use active voice instead of passive voice ('is appended').
docs/manage/troubleshooting.md|119 col 72| [Google.WordList] Use 'select' instead of 'check'.
docs/manage/troubleshooting.md|154 col 48| [Google.OptionalPlurals] Don't use plurals in parentheses such as in 'node(s)'.
docs/manage/troubleshooting.md|154 col 52| [Google.Parens] Use parentheses judiciously.
docs/manage/troubleshooting.md|154 col 123| [Google.Spacing] 'd. I' should have one space.
docs/usage/pitr-tutorial.md|5 col 128| [Google.WordList] Use 'select' instead of 'check'.
docs/usage/pitr-tutorial.md|9 col 119| [Google.Contractions] Use 'can't' instead of 'cannot'.
docs/usage/pitr-tutorial.md|9 col 126| [Google.Passive] In general, use active voice instead of passive voice ('be run').
docs/usage/pitr-tutorial.md|16 col 24| [Google.Passive] In general, use active voice instead of passive voice ('are made').
docs/usage/pitr-tutorial.md|129 col 118| [Google.Passive] In general, use active voice instead of passive voice ('is made').
docs/usage/pitr-tutorial.md|142 col 159| [Google.Passive] In general, use active voice instead of passive voice ('is ignored').
docs/usage/pitr-tutorial.md|151 col 162| [Google.Parens] Use parentheses judiciously.
docs/usage/pitr-tutorial.md|153 col 90| [Google.Parens] Use parentheses judiciously.
docs/usage/pitr-tutorial.md|155 col 33| [Google.Passive] In general, use active voice instead of passive voice ('is started').
docs/usage/pitr-tutorial.md|155 col 137| [Google.Parens] Use parentheses judiciously.
docs/usage/pitr-tutorial.md|155 col 218| [Google.Passive] In general, use active voice instead of passive voice ('is provided').
docs/usage/restore.md|283 col 106| [Google.Contractions] Use 'that's' instead of 'that is'.
docs/usage/restore.md|283 col 111| [Google.Passive] In general, use active voice instead of passive voice ('is defined').
docs/usage/restore.md|283 col 196| [Google.Contractions] Use 'it's' instead of 'it is'.
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').
docs/usage/oplog-replay.md|50 col 44| [Google.Passive] In general, use active voice instead of passive voice ('been created').
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/usage/logs.md|18 col 76| [Google.Passive] In general, use active voice instead of passive voice ('are supported').
docs/usage/logs.md|18 col 90| [Google.Parens] Use parentheses judiciously.
docs/usage/logs.md|26 col 51| [Google.Parens] Use parentheses judiciously.
docs/usage/logs.md|51 col 107| [Google.Passive] In general, use active voice instead of passive voice ('is specified').
docs/usage/logs.md|51 col 155| [Google.Passive] In general, use active voice instead of passive voice ('are shown').
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/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/release-notes/1.3.4.md|1 col 3| [Google.Headings] 'Percona Backup for MongoDB 1.3.4' should use sentence-style capitalization.
docs/release-notes/1.3.4.md|10 col 34| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.3.4.md|19 col 4| [Google.Headings] 'Bugs Fixed' should use sentence-style capitalization.
docs/release-notes/1.3.4.md|21 col 71| [Vale.Spelling] Did you really mean 'demultiplexing'?
docs/release-notes/1.3.4.md|23 col 109| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.3.4.md|23 col 125| [Vale.Spelling] Did you really mean 'pedroalb'?
docs/usage/start-backup.md|104 col 115| [Google.Passive] In general, use active voice instead of passive voice ('is done').
docs/usage/start-backup.md|116 col 33| [Google.Parens] Use parentheses judiciously.
docs/usage/start-backup.md|119 col 82| [Google.Will] Avoid using 'will'.
docs/usage/start-backup.md|123 col 29| [Google.Parens] Use parentheses judiciously.
docs/usage/start-backup.md|129 col 20| [Google.Contractions] Use 'aren't' instead of 'are not'.
docs/usage/start-backup.md|141 col 86| [Google.Passive] In general, use active voice instead of passive voice ('is elected').
docs/usage/start-backup.md|141 col 194| [Google.Passive] In general, use active voice instead of passive voice ('is elected').
docs/usage/start-backup.md|141 col 374| [Google.Passive] In general, use active voice instead of passive voice ('is elected').
docs/usage/start-backup.md|158 col 66| [Google.Will] Avoid using 'will'.
docs/usage/start-backup.md|170 col 115| [Google.Passive] In general, use active voice instead of passive voice ('is selected').
docs/release-notes/1.2.1.md|1 col 1| [Google.Headings] 'Percona Backup for MongoDB 1.2.1' should use sentence-style capitalization.
docs/release-notes/1.2.1.md|10 col 34| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.2.1.md|12 col 4| [Google.Headings] 'Bugs Fixed' should use sentence-style capitalization.
docs/release-notes/1.2.1.md|14 col 91| [Vale.Spelling] Did you really mean 'debian'?
docs/usage/delete-backup.md|13 col 23| [Google.Parens] Use parentheses judiciously.
docs/usage/delete-backup.md|14 col 14| [Google.Parens] Use parentheses judiciously.
docs/usage/delete-backup.md|15 col 9| [Google.Parens] Use parentheses judiciously.
docs/usage/delete-backup.md|15 col 10| [Google.Units] Put a nonbreaking space between the number and the unit in '1d'.
docs/usage/delete-backup.md|15 col 16| [Google.Units] Put a nonbreaking space between the number and the unit in '30d'.
docs/usage/delete-backup.md|15 col 32| [Google.Passive] In general, use active voice instead of passive voice ('are supported').
docs/usage/delete-backup.md|17 col 61| [Google.Passive] In general, use active voice instead of passive voice ('be deleted').
docs/usage/delete-backup.md|17 col 76| [Google.Passive] In general, use active voice instead of passive voice ('are asked').
docs/usage/delete-backup.md|25 col 27| [Google.Passive] In general, use active voice instead of passive voice ('is considered').
docs/usage/delete-backup.md|25 col 171| [Google.Passive] In general, use active voice instead of passive voice ('be used').
docs/usage/delete-backup.md|29 col 38| [Google.Passive] In general, use active voice instead of passive voice ('are deleted').
docs/usage/delete-backup.md|30 col 36| [Google.Passive] In general, use active voice instead of passive voice ('are deleted').
docs/usage/delete-backup.md|49 col 206| [Google.Contractions] Use 'that's' instead of 'that is'.
docs/usage/delete-backup.md|64 col 23| [Google.We] Try to avoid using first-person plural like 'let's'.
docs/usage/delete-backup.md|87 col 35| [Google.Passive] In general, use active voice instead of passive voice ('is enabled').
docs/usage/delete-backup.md|94 col 33| [Google.Contractions] Use 'that's' instead of 'that is'.
docs/usage/delete-backup.md|94 col 53| [Google.Parens] Use parentheses judiciously.
docs/usage/delete-backup.md|94 col 95| [Google.WordList] Use 'select' instead of 'check'.
docs/usage/delete-backup.md|96 col 122| [Google.OptionalPlurals] Don't use plurals in parentheses such as in 'backup(s)'.
docs/usage/delete-backup.md|96 col 128| [Google.Parens] Use parentheses judiciously.
docs/usage/delete-backup.md|98 col 228| [Google.Passive] In general, use active voice instead of passive voice ('are created').
docs/usage/delete-backup.md|100 col 56| [Google.Passive] In general, use active voice instead of passive voice ('is enabled').
docs/usage/delete-backup.md|114 col 100| [Google.Contractions] Use 'can't' instead of 'cannot'.
docs/usage/delete-backup.md|116 col 38| [Google.Contractions] Use 'it's' instead of 'it is'.
docs/usage/delete-backup.md|117 col 43| [Google.Passive] In general, use active voice instead of passive voice ('is enabled').
docs/usage/delete-backup.md|213 col 119| [Google.Contractions] Use 'doesn't' instead of 'does not'.
docs/usage/delete-backup.md|213 col 147| [Google.Passive] In general, use active voice instead of passive voice ('were made').
docs/usage/delete-backup.md|213 col 389| [Google.Passive] In general, use active voice instead of passive voice ('were made').
docs/release-notes/1.8.1.md|1 col 3| [Google.Headings] 'Percona Backup for MongoDB 1.8.1 (2022-07-12)' should use sentence-style capitalization.
docs/release-notes/1.8.1.md|1 col 36| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.8.1.md|7 col 215| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.8.1.md|10 col 4| [Google.Headings] 'Release Highlights' should use sentence-style capitalization.
docs/release-notes/1.8.1.md|12 col 114| [Google.Acronyms] Spell out 'UUID', if it's unfamiliar to the audience.
docs/release-notes/1.8.1.md|12 col 151| [Google.Contractions] Use 'aren't' instead of 'are not'.
docs/release-notes/1.7.0.md|1 col 3| [Google.Headings] 'Percona Backup for MongoDB 1.7.0 (2022-04-18)' should use sentence-style capitalization.
docs/release-notes/1.7.0.md|1 col 36| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.7.0.md|8 col 215| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.7.0.md|12 col 208| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.7.0.md|14 col 85| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.7.0.md|14 col 105| [Google.Passive] In general, use active voice instead of passive voice ('is recovered').
docs/release-notes/1.7.0.md|22 col 4| [Google.Headings] 'New Features' should use sentence-style capitalization.
docs/release-notes/1.7.0.md|28 col 152| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.7.0.md|28 col 172| [Google.Passive] In general, use active voice instead of passive voice ('is recovered').
docs/release-notes/1.7.0.md|32 col 60| [Google.Acronyms] Spell out 'TLS', if it's unfamiliar to the audience.
docs/release-notes/1.7.0.md|34 col 137| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.7.0.md|34 col 148| [Vale.Spelling] Did you really mean 'Damiano'?
docs/release-notes/1.7.0.md|34 col 156| [Vale.Spelling] Did you really mean 'Albani'?
docs/release-notes/1.7.0.md|36 col 63| [Vale.Spelling] Did you really mean 'Zstandard'?
docs/release-notes/1.7.0.md|36 col 92| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.7.0.md|36 col 103| [Vale.Spelling] Did you really mean 'Damiano'?
docs/release-notes/1.7.0.md|36 col 111| [Vale.Spelling] Did you really mean 'Albani'?
docs/release-notes/1.7.0.md|38 col 103| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.7.0.md|38 col 114| [Vale.Spelling] Did you really mean 'Damiano'?
docs/release-notes/1.7.0.md|38 col 122| [Vale.Spelling] Did you really mean 'Albani'?
docs/release-notes/1.7.0.md|40 col 154| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.7.0.md|40 col 165| [Vale.Spelling] Did you really mean 'Damiano'?
docs/release-notes/1.7.0.md|40 col 173| [Vale.Spelling] Did you really mean 'Albani'?
docs/release-notes/1.7.0.md|42 col 151| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.7.0.md|42 col 162| [Vale.Spelling] Did you really mean 'Damiano'?
docs/release-notes/1.7.0.md|42 col 170| [Vale.Spelling] Did you really mean 'Albani'?
docs/release-notes/1.7.0.md|44 col 55| [Google.Contractions] Use 'it's' instead of 'It is'.
docs/release-notes/1.7.0.md|44 col 147| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.7.0.md|44 col 158| [Vale.Spelling] Did you really mean 'Damiano'?
docs/release-notes/1.7.0.md|44 col 166| [Vale.Spelling] Did you really mean 'Albani'?
docs/release-notes/1.7.0.md|46 col 4| [Google.Headings] 'Bugs Fixed' should use sentence-style capitalization.
docs/release-notes/1.7.0.md|48 col 194| [Google.Passive] In general, use active voice instead of passive voice ('be configured').
docs/release-notes/1.3.1.md|1 col 3| [Google.Headings] 'Percona Backup for MongoDB 1.3.1' should use sentence-style capitalization.
docs/release-notes/1.3.1.md|10 col 34| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.3.1.md|13 col 4| [Google.Headings] 'Bugs Fixed' should use sentence-style capitalization.
docs/release-notes/1.1.3.md|1 col 3| [Google.Headings] 'Percona Backup for MongoDB 1.1.3' should use sentence-style capitalization.
docs/release-notes/1.1.3.md|10 col 82| [Vale.Spelling] Did you really mean 'arg'?
docs/release-notes/1.1.3.md|12 col 98| [Google.WordList] Use 'administrator' instead of 'admin'.
docs/release-notes/1.1.3.md|16 col 4| [Google.Headings] 'Bugs Fixed' should use sentence-style capitalization.
docs/release-notes/1.1.3.md|20 col 64| [Vale.Spelling] Did you really mean 'resync'?
docs/release-notes/1.1.1.md|1 col 3| [Google.Headings] 'Percona Backup for MongoDB 1.1.1' should use sentence-style capitalization.
docs/release-notes/1.1.1.md|10 col 42| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.1.1.md|11 col 66| [Google.Passive] In general, use active voice instead of passive voice ('was inspired').
docs/release-notes/1.1.1.md|12 col 1| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.1.1.md|21 col 4| [Google.Headings] 'Bugs Fixed' should use sentence-style capitalization.
docs/release-notes/1.1.1.md|26 col 90| [Google.Passive] In general, use active voice instead of passive voice ('was broken').
docs/release-notes/1.5.0.md|1 col 3| [Google.Headings] 'Percona Backup for MongoDB 1.5.0' should use sentence-style capitalization.
docs/release-notes/1.5.0.md|10 col 34| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.5.0.md|13 col 4| [Google.Headings] 'New Features' should use sentence-style capitalization.
docs/release-notes/1.5.0.md|17 col 118| [Google.Will] Avoid using 'will'.
docs/release-notes/1.5.0.md|23 col 64| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.5.0.md|25 col 4| [Google.Headings] 'Bugs Fixed' should use sentence-style capitalization.
docs/release-notes/1.5.0.md|29 col 76| [Google.Acronyms] Spell out 'UUID', if it's unfamiliar to the audience.
docs/release-notes/1.5.0.md|29 col 95| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.5.0.md|29 col 106| [Vale.Spelling] Did you really mean 'Nikolay'?
docs/release-notes/1.5.0.md|29 col 143| [Vale.Spelling] Did you really mean 'Dmitry'?
docs/release-notes/1.5.0.md|29 col 150| [Vale.Spelling] Did you really mean 'Kuzmin'?
docs/release-notes/2.0.1.md|1 col 3| [Google.Headings] 'Percona Backup for MongoDB 2.0.1 (2022-10-12)' should use sentence-style capitalization.
docs/release-notes/2.0.1.md|1 col 36| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.0.1.md|8 col 215| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.0.1.md|10 col 4| [Google.Headings] 'Release Highlights' should use sentence-style capitalization.
docs/release-notes/2.0.1.md|12 col 1| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.0.1.md|12 col 100| [Google.Acronyms] Spell out 'SSE', if it's unfamiliar to the audience.
docs/release-notes/2.0.1.md|12 col 288| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/release-notes/2.0.1.md|12 col 292| [Google.Acronyms] Spell out 'KMS', if it's unfamiliar to the audience.
docs/release-notes/2.0.1.md|13 col 134| [Google.Passive] In general, use active voice instead of passive voice ('is deployed').
docs/release-notes/2.0.1.md|22 col 4| [Google.Headings] 'New Features' should use sentence-style capitalization.
docs/release-notes/2.0.1.md|25 col 95| [Vale.Spelling] Did you really mean 'stdin'?
docs/release-notes/2.0.1.md|31 col 131| [Google.Passive] In general, use active voice instead of passive voice ('is misconfigured').
docs/release-notes/2.0.1.md|32 col 71| [Google.Acronyms] Spell out 'SSE', if it's unfamiliar to the audience.
docs/release-notes/2.0.1.md|32 col 94| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.0.1.md|32 col 113| [Vale.Spelling] Did you really mean 'Bateman'?
docs/release-notes/2.0.1.md|36 col 4| [Google.Headings] 'Bugs Fixed' should use sentence-style capitalization.
docs/release-notes/2.0.1.md|39 col 157| [Vale.Spelling] Did you really mean 'resync'?
docs/release-notes/2.0.1.md|41 col 112| [Google.Passive] In general, use active voice instead of passive voice ('be created').
docs/release-notes/1.6.1.md|1 col 1| [Google.Headings] 'Percona Backup for MongoDB 1.6.1 (2021-11-04)' should use sentence-style capitalization.
docs/release-notes/1.6.1.md|1 col 38| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.6.1.md|9 col 34| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.6.1.md|12 col 4| [Google.Headings] 'Release Highlights' should use sentence-style capitalization.
docs/release-notes/1.6.1.md|18 col 115| [Google.Passive] In general, use active voice instead of passive voice ('is deployed').
docs/release-notes/1.6.1.md|18 col 189| [Google.Passive] In general, use active voice instead of passive voice ('are used').
docs/release-notes/1.6.1.md|18 col 408| [Vale.Spelling] Did you really mean 'kiam'?
docs/release-notes/1.6.1.md|18 col 426| [Vale.Spelling] Did you really mean 'irsa'?
docs/release-notes/1.6.1.md|24 col 59| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/release-notes/1.6.1.md|26 col 4| [Google.Headings] 'Bugs Fixed' should use sentence-style capitalization.
docs/release-notes/1.6.1.md|30 col 154| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.6.1.md|32 col 88| [Vale.Spelling] Did you really mean 'catchup'?
docs/release-notes/2.0.0.md|1 col 3| [Google.Headings] 'Percona Backup for MongoDB 2.0.0 (2022-09-21)' should use sentence-style capitalization.
docs/release-notes/2.0.0.md|1 col 36| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.0.0.md|7 col 215| [Google.Parens] Use parentheses judiciously.
... (Too many findings. Dropped some findings)