docs/reference/backup-options.md|55 col 83| [Google.Will] Avoid using 'will'.
docs/reference/backup-options.md|57 col 5| [Google.Headings] 'backup.timeouts.startingStatus' should use sentence-style capitalization.
docs/reference/backup-options.md|62 col 15| [Google.Parens] Use parentheses judiciously.

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').
_resource/includes/abbreviations.md|2 col 3| [Google.Acronyms] Spell out 'SLA', if it's unfamiliar to the audience.
_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/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/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/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/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/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/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/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|45 col 120| [Google.Passive] In general, use active voice instead of passive voice ('is used').
docs/usage/pitr-tutorial.md|45 col 159| [Google.Contractions] Use 'it's' instead of 'it is'.
docs/usage/pitr-tutorial.md|75 col 118| [Google.Passive] In general, use active voice instead of passive voice ('is made').
docs/usage/pitr-tutorial.md|86 col 155| [Google.Passive] In general, use active voice instead of passive voice ('is ignored').
docs/usage/pitr-tutorial.md|96 col 158| [Google.Parens] Use parentheses judiciously.
docs/usage/pitr-tutorial.md|98 col 86| [Google.Parens] Use parentheses judiciously.
docs/usage/pitr-tutorial.md|100 col 29| [Google.Passive] In general, use active voice instead of passive voice ('is started').
docs/usage/pitr-tutorial.md|100 col 133| [Google.Parens] Use parentheses judiciously.
docs/usage/pitr-tutorial.md|100 col 214| [Google.Passive] In general, use active voice instead of passive voice ('is provided').
docs/usage/pitr-tutorial.md|112 col 42| [Google.Contractions] Use 'it's' instead of 'it is'.
docs/usage/pitr-tutorial.md|124 col 4| [Vale.Spelling] Did you really mean 'Resync'?
docs/usage/pitr-tutorial.md|145 col 140| [Google.Passive] In general, use active voice instead of passive voice ('is shut').
docs/usage/pitr-tutorial.md|146 col 249| [Google.Passive] In general, use active voice instead of passive voice ('be included').
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/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/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|20 col 5| [Google.Headings] '1. Clone the repository' should use sentence-style capitalization.
docs/install/source.md|41 col 45| [Google.Passive] In general, use active voice instead of passive voice ('been built').
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').
docs/install/tarball.md|23 col 5| [Google.Headings] '2. Extract the tarball' should use sentence-style capitalization.
docs/install/repos.md|19 col 6| [Google.Headings] '2. Enable the repository' should use sentence-style capitalization.
docs/install/repos.md|21 col 69| [Google.Passive] In general, use active voice instead of passive voice ('are stored').
docs/install/repos.md|27 col 6| [Google.Headings] '3. Install Percona Backup for MongoDB' should use sentence-style capitalization.
docs/release-notes/1.4.0.md|10 col 34| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.4.0.md|13 col 4| [Google.Headings] 'New Features' should use sentence-style capitalization.
docs/release-notes/1.4.0.md|21 col 116| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.4.0.md|25 col 4| [Google.Headings] 'Bugs Fixed' should use sentence-style capitalization.
docs/release-notes/1.4.0.md|27 col 83| [Vale.Spelling] Did you really mean 'rset'?
docs/release-notes/1.4.0.md|31 col 72| [Google.Passive] In general, use active voice instead of passive voice ('are created').
docs/release-notes/1.4.0.md|33 col 101| [Google.Passive] In general, use active voice instead of passive voice ('is enabled').
docs/release-notes/2.2.0.md|1 col 36| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.2.0.md|8 col 215| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.2.0.md|10 col 4| [Google.Headings] 'Release Highlights' should use sentence-style capitalization.
docs/release-notes/2.2.0.md|12 col 188| [Vale.Spelling] Did you really mean 'DBAs'?
docs/release-notes/2.2.0.md|13 col 112| [Google.Acronyms] Spell out 'EBS', if it's unfamiliar to the audience.
docs/release-notes/2.2.0.md|16 col 4| [Google.Headings] 'New Features' should use sentence-style capitalization.
docs/release-notes/2.2.0.md|26 col 88| [Google.EnDash] Use an em dash ('—') instead of '–'.
docs/release-notes/2.2.0.md|27 col 74| [Google.Acronyms] Spell out 'PSMDB', if it's unfamiliar to the audience.
docs/release-notes/2.2.0.md|27 col 88| [Google.WordList] Use 'select' instead of 'check'.
docs/release-notes/2.2.0.md|29 col 4| [Google.Headings] 'Bugs Fixed' should use sentence-style capitalization.
docs/release-notes/2.2.0.md|32 col 129| [Vale.Spelling] Did you really mean 'authSource'?
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/release-notes/1.3.2.md|10 col 34| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.3.2.md|13 col 4| [Google.Headings] 'New Features' should use sentence-style capitalization.
docs/release-notes/1.3.2.md|15 col 59| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/release-notes/1.3.2.md|15 col 63| [Google.Acronyms] Spell out 'KMS', if it's unfamiliar to the audience.
docs/release-notes/1.3.2.md|27 col 1| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.3.2.md|27 col 17| [Vale.Spelling] Did you really mean 'pedroalb'?
docs/release-notes/1.3.2.md|33 col 117| [Vale.Spelling] Did you really mean 'gzip'?
docs/release-notes/1.3.2.md|35 col 4| [Google.Headings] 'Bugs Fixed' should use sentence-style capitalization.
docs/release-notes/1.3.2.md|37 col 150| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.3.2.md|37 col 166| [Vale.Spelling] Did you really mean 'pedroalb'?
docs/release-notes/1.3.2.md|39 col 120| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.3.2.md|39 col 142| [Vale.Spelling] Did you really mean 'Bernier'?
docs/release-notes/2.1.0.md|1 col 36| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.1.0.md|8 col 215| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.1.0.md|10 col 4| [Google.Headings] 'Release Highlights' should use sentence-style capitalization.
docs/release-notes/2.1.0.md|17 col 18| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/release-notes/2.1.0.md|17 col 164| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/release-notes/2.1.0.md|19 col 4| [Google.Headings] 'New Features' should use sentence-style capitalization.
docs/release-notes/2.1.0.md|26 col 95| [Vale.Spelling] Did you really mean 'storages'?
docs/release-notes/2.1.0.md|28 col 111| [Vale.Spelling] Did you really mean 'resync'?
docs/release-notes/2.1.0.md|30 col 124| [Google.Passive] In general, use active voice instead of passive voice ('is made').
docs/release-notes/2.1.0.md|34 col 63| [Vale.Spelling] Did you really mean 'mongod'?
docs/release-notes/2.1.0.md|35 col 73| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/release-notes/2.1.0.md|36 col 109| [Google.Acronyms] Spell out 'PSMDB', if it's unfamiliar to the audience.
docs/release-notes/2.1.0.md|39 col 108| [Google.Passive] In general, use active voice instead of passive voice ('is used').
docs/release-notes/2.1.0.md|41 col 4| [Google.Headings] 'Bugs Fixed' should use sentence-style capitalization.
docs/release-notes/2.1.0.md|45 col 154| [Google.Passive] In general, use active voice instead of passive voice ('were added').
docs/release-notes/2.1.0.md|47 col 115| [Google.Acronyms] Spell out 'PSMDB', if it's unfamiliar to the audience.
docs/release-notes/2.1.0.md|48 col 120| [Google.Passive] In general, use active voice instead of passive voice ('is configured').
docs/release-notes/2.1.0.md|48 col 137| [Google.Acronyms] Spell out 'PSMDB', if it's unfamiliar to the audience.
docs/release-notes/2.0.5.md|1 col 36| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.0.5.md|8 col 215| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.0.5.md|10 col 4| [Google.Headings] 'Release Highlights' should use sentence-style capitalization.
docs/release-notes/2.0.5.md|14 col 62| [Vale.Spelling] Did you really mean 'mongod'?
docs/release-notes/2.0.5.md|14 col 107| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.0.5.md|15 col 27| [Google.Acronyms] Spell out 'CVE', if it's unfamiliar to the audience.
docs/release-notes/2.0.5.md|17 col 4| [Google.Headings] 'Bugs Fixed' should use sentence-style capitalization.
docs/release-notes/2.0.5.md|21 col 96| [Google.Acronyms] Spell out 'CVE', if it's unfamiliar to the audience.
docs/install/initial-setup.md|3 col 107| [Google.Contractions] Use 'that's' instead of 'that is'.
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|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/release-notes/1.2.0.md|10 col 34| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.2.0.md|12 col 4| [Google.Headings] 'New Features' should use sentence-style capitalization.
docs/release-notes/1.2.0.md|22 col 58| [Google.Passive] In general, use active voice instead of passive voice ('is set').
docs/release-notes/1.2.0.md|28 col 4| [Google.Headings] 'Bugs Fixed' should use sentence-style capitalization.
docs/release-notes/1.2.0.md|30 col 55| [Vale.Spelling] Did you really mean 'Resync'?
docs/release-notes/1.2.0.md|30 col 90| [Google.Passive] In general, use active voice instead of passive voice ('was set').
docs/release-notes/2.0.3.md|1 col 36| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.0.3.md|8 col 215| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.0.3.md|10 col 4| [Google.Headings] 'Release Highlights' should use sentence-style capitalization.
docs/release-notes/2.0.3.md|12 col 458| [Google.We] Try to avoid using first-person plural like 'we'.
docs/release-notes/2.0.3.md|12 col 498| [Google.WordList] Use 'capability' or 'feature' instead of 'functionality'.
docs/release-notes/2.0.3.md|14 col 20| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/release-notes/2.0.3.md|14 col 24| [Google.Acronyms] Spell out 'IRSA', if it's unfamiliar to the audience.
docs/release-notes/2.0.3.md|14 col 29| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.0.3.md|14 col 144| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/release-notes/2.0.3.md|14 col 166| [Google.Acronyms] Spell out 'IAM', if it's unfamiliar to the audience.
docs/release-notes/2.0.3.md|17 col 4| [Google.Headings] 'New Features' should use sentence-style capitalization.
docs/release-notes/2.0.3.md|26 col 62| [Google.Acronyms] Spell out 'AWS', if it's unfamiliar to the audience.
docs/release-notes/2.0.3.md|26 col 66| [Google.Acronyms] Spell out 'IRSA', if it's unfamiliar to the audience.
docs/release-notes/2.0.3.md|26 col 91| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.0.3.md|26 col 111| [Vale.Spelling] Did you really mean 'pastequo'?
docs/release-notes/2.0.3.md|29 col 4| [Google.Headings] 'Bugs Fixed' should use sentence-style capitalization.
docs/release-notes/2.0.3.md|32 col 76| [Google.Acronyms] Spell out 'ERROR', if it's unfamiliar to the audience.
docs/release-notes/2.0.3.md|33 col 118| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.0.3.md|33 col 134| [Vale.Spelling] Did you really mean 'Piotr'?
docs/release-notes/2.0.3.md|33 col 140| [Vale.Spelling] Did you really mean 'Krogulec'?
docs/release-notes/2.0.3.md|33 col 186| [Vale.Spelling] Did you really mean 'ziollek'?
docs/release-notes/1.0.0.md|3 col 48| [Google.We] Try to avoid using first-person plural like 'our'.
docs/release-notes/1.0.0.md|8 col 42| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.0.0.md|9 col 66| [Google.Passive] In general, use active voice instead of passive voice ('was inspired').
docs/release-notes/1.0.0.md|10 col 1| [Google.Parens] Use parentheses judiciously.
docs/release-notes/1.0.0.md|21 col 78| [Google.Passive] In general, use active voice instead of passive voice ('been simplified').
docs/release-notes/1.0.0.md|24 col 99| [Vale.Spelling] Did you really mean 'storages'?
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.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 36| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.0.0.md|7 col 215| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.0.0.md|10 col 4| [Google.Headings] 'Release Highlights' should use sentence-style capitalization.
docs/release-notes/2.0.0.md|13 col 97| [Google.Passive] In general, use active voice instead of passive voice ('is supported').
docs/release-notes/2.0.0.md|15 col 75| [Google.Passive] In general, use active voice instead of passive voice ('be done').
docs/release-notes/2.0.0.md|19 col 4| [Google.Headings] 'New Features' should use sentence-style capitalization.
docs/release-notes/2.0.0.md|26 col 172| [Vale.Spelling] Did you really mean 'mongod'?
docs/release-notes/2.0.0.md|31 col 4| [Google.Headings] 'Bugs Fixed' should use sentence-style capitalization.
docs/release-notes/2.0.0.md|35 col 64| [Google.Acronyms] Spell out 'UUID', if it's unfamiliar to the audience.
docs/release-notes/2.0.0.md|35 col 73| [Vale.Spelling] Did you really mean 'timeseries'?
docs/release-notes/2.0.0.md|39 col 29| [Google.Contractions] Use 'aren't' instead of 'are not'.
docs/release-notes/2.0.0.md|39 col 70| [Google.Contractions] Use 'aren't' instead of 'are not'.
docs/release-notes/2.0.0.md|39 col 102| [Google.Acronyms] Spell out 'SLA', if it's unfamiliar to the audience.
docs/release-notes/2.0.0.md|39 col 107| [Google.Contractions] Use 'they're' instead of 'They are'.
docs/release-notes/2.0.0.md|39 col 112| [Google.Passive] In general, use active voice instead of passive voice ('are included').
docs/release-notes/2.0.0.md|39 col 240| [Google.Parens] Use parentheses judiciously.
docs/release-notes/2.0.0.md|39 col 270| [Google.Contractions] Use 'it's' instead of 'it is'.
docs/release-notes/2.0.0.md|39 col 273| [Google.Passive] In general, use active voice instead of passive voice ('is deemed').
docs/release-notes/2.0.0.md|39 col 301| [Google.WordList] Use 'capability' or 'feature' instead of 'functionality'.
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.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.
... (Too many findings. Dropped some findings)