chore(release): Autobump agent plugin version (0.14.1) #2228
reviewdog [vale] report
reported by reviewdog 🐶
Findings (0)
Filtered Findings (6417)
CONTRIBUTING.md|1 col 3| [Google.Headings] 'How to Contribute' should use sentence-style capitalization.
CONTRIBUTING.md|6 col 4| [Google.Headings] 'Contributor License Agreement' should use sentence-style capitalization.
CONTRIBUTING.md|10 col 18| [Google.We] Try to avoid using first-person plural like ' us '.
CONTRIBUTING.md|20 col 75| [Google.We] Try to avoid using first-person plural like ' We '.
CONTRIBUTING.md|25 col 4| [Google.Headings] 'Community Guidelines' should use sentence-style capitalization.
content/en/contribute/approve-review/guidelines-reviewer.md|12 col 4| [Google.Headings] '{{% heading "prereq" %}}' should use sentence-style capitalization.
content/en/contribute/create/create-page.md|11 col 45| [Google.Will] Avoid using ' will '.
content/en/contribute/approve-review/guidelines-approver.md|6 col 4| [Google.Headings] '{{% heading "prereq" %}}' should use sentence-style capitalization.
content/en/contribute/approve-review/guidelines-approver.md|20 col 114| [Google.WordList] Use 'capability' or 'feature' instead of 'functionality'.
content/en/contribute/approve-review/guidelines-approver.md|32 col 4| [Google.Headings] 'SEO guidelines' should use sentence-style capitalization.
content/en/contribute/approve-review/guidelines-approver.md|48 col 5| [Google.Headings] 'Approver SEO checklist' should use sentence-style capitalization.
content/en/contribute/approve-review/guidelines-approver.md|50 col 11| [Google.We] Try to avoid using first-person plural like ' our '.
content/en/contribute/approve-review/guidelines-approver.md|52 col 197| [Google.Spacing] 'd. N' should have one space.
content/en/contribute/approve-review/guidelines-approver.md|54 col 58| [Google.Latin] Use 'for example' instead of 'e.g.,'.
content/en/contribute/approve-review/guidelines-approver.md|58 col 81| [Google.Will] Avoid using ' will '.
content/en/contribute/approve-review/guidelines-approver.md|60 col 36| [Google.Latin] Use 'for example' instead of 'e.g.,'.
content/en/contribute/approve-review/guidelines-approver.md|60 col 50| [Google.Will] Avoid using ' will '.
content/en/contribute/approve-review/guidelines-approver.md|70 col 23| [Google.WordList] Use 'URL' instead of 'url'.
content/en/contribute/approve-review/guidelines-approver.md|73 col 108| [Google.OptionalPlurals] Don't use plurals in parentheses such as in 'keyword(s)'.
content/en/contribute/create/local-clone.md|12 col 4| [Google.Headings] '{{% heading "prereq" %}}' should use sentence-style capitalization.
content/en/contribute/create/local-clone.md|212 col 71| [Google.Will] Avoid using ' will '.
content/en/contribute/create/local-clone.md|214 col 321| [Google.Exclamation] Don't use exclamation points in text.
content/en/contribute/create/local-clone.md|219 col 15| [Google.Exclamation] Don't use exclamation points in text.
content/en/contribute/create/local-clone.md|221 col 75| [Google.Exclamation] Don't use exclamation points in text.
README.md|3 col 48| [Google.We] Try to avoid using first-person plural like ' We '.
README.md|9 col 425| [Google.OxfordComma] Use the Oxford comma in ' addresses this problem by cutting the time, effort and '.
content/en/contribute/create/guides/shortcodes/tabs/file-with-tabs.md|19 col 6| [Google.Headings] 'Plain HTML' should use sentence-style capitalization.
content/en/managed-spin/_index.md|18 col 5| [Google.Headings] 'Armory Continuous Deployment for Spinnaker' should use sentence-style capitalization.
content/en/managed-spin/_index.md|93 col 159| [Google.WordList] Use 'capability' or 'feature' instead of 'functionality'.
content/en/managed-spin/_index.md|98 col 4| [Google.Headings] 'Uptime SLAs' should use sentence-style capitalization.
content/en/managed-spin/_index.md|106 col 179| [Google.WordList] Use 'tap' instead of 'touch'.
content/en/managed-spin/_index.md|110 col 131| [Google.Will] Avoid using ' will '.
content/en/contribute/create/guides/shortcodes/_index.md|43 col 6| [Google.Headings] '{{% heading "prereq" %}}' should use sentence-style capitalization.
content/en/contribute/create/guides/shortcodes/_index.md|51 col 6| [Google.Headings] '{{% heading "installOperator" %}}' should use sentence-style capitalization.
content/en/contribute/create/guides/shortcodes/_index.md|75 col 53| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/shortcodes/_index.md|86 col 90| [Google.Units] Put a nonbreaking space between the number and the unit in '7h'.
content/en/contribute/create/guides/shortcodes/_index.md|86 col 111| [Google.Units] Put a nonbreaking space between the number and the unit in '0d'.
content/en/contribute/create/guides/shortcodes/_index.md|89 col 6| [Google.Headings] 'Slide deck' should use sentence-style capitalization.
content/en/contribute/create/guides/shortcodes/_index.md|91 col 86| [Google.Units] Put a nonbreaking space between the number and the unit in '8s'.
content/en/contribute/create/guides/shortcodes/github-include.md|36 col 4| [Google.Headings] 'surround with collapsible panel' should use sentence-style capitalization.
content/en/contribute/create/guides/shortcodes/github-include.md|44 col 24| [Google.FirstPerson] Avoid first-person pronouns such as 'me'.
content/en/contribute/create/guides/shortcodes/entire-gist.md|9 col 39| [Google.Units] Put a nonbreaking space between the number and the unit in '9d'.
content/en/contribute/create/guides/shortcodes/entire-gist.md|9 col 53| [Google.Units] Put a nonbreaking space between the number and the unit in '804d'.
content/en/contribute/create/guides/shortcodes/entire-gist.md|11 col 37| [Google.Units] Put a nonbreaking space between the number and the unit in '9d'.
content/en/contribute/create/guides/shortcodes/entire-gist.md|11 col 51| [Google.Units] Put a nonbreaking space between the number and the unit in '804d'.
content/en/contribute/create/guides/shortcodes/csv-short.md|9 col 4| [Google.Headings] 'Table from CSV file' should use sentence-style capitalization.
content/en/contribute/create/guides/shortcodes/csv-short.md|17 col 5| [Google.Headings] 'CSV without embedded HTML' should use sentence-style capitalization.
content/en/contribute/create/guides/shortcodes/csv-short.md|21 col 5| [Google.Headings] 'CSV with embedded HTML' should use sentence-style capitalization.
content/en/contribute/create/guides/shortcodes/tabs/index.md|9 col 4| [Google.Headings] 'Tabs - Docsy shortcode' should use sentence-style capitalization.
content/en/contribute/create/guides/shortcodes/tabs/index.md|13 col 119| [Google.Exclamation] Don't use exclamation points in text.
content/en/contribute/create/guides/shortcodes/tabs/index.md|15 col 103| [Google.Exclamation] Don't use exclamation points in text.
content/en/contribute/create/guides/shortcodes/tabs/index.md|17 col 5| [Google.Headings] 'tab with %, include with %' should use sentence-style capitalization.
content/en/contribute/create/guides/shortcodes/tabs/index.md|42 col 5| [Google.Headings] 'tab with %, include with <' should use sentence-style capitalization.
content/en/contribute/create/guides/shortcodes/tabs/index.md|68 col 5| [Google.Headings] 'tab with %, readfile with %' should use sentence-style capitalization.
content/en/contribute/create/guides/shortcodes/tabs/index.md|93 col 5| [Google.Headings] 'tab with %, readfile with <' should use sentence-style capitalization.
content/en/contribute/create/guides/shortcodes/tabs/index.md|122 col 5| [Google.Headings] 'Inserting raw HTML' should use sentence-style capitalization.
content/en/contribute/create/guides/shortcodes/gist-vs-codeblock.md|23 col 29| [Google.Units] Put a nonbreaking space between the number and the unit in '67d'.
content/en/contribute/create/guides/shortcodes/gist-vs-codeblock.md|26 col 27| [Google.Units] Put a nonbreaking space between the number and the unit in '67d'.
content/en/contribute/create/guides/shortcodes/gist-vs-codeblock.md|68 col 39| [Google.Units] Put a nonbreaking space between the number and the unit in '9d'.
content/en/contribute/create/guides/shortcodes/gist-vs-codeblock.md|68 col 53| [Google.Units] Put a nonbreaking space between the number and the unit in '804d'.
content/en/contribute/create/guides/shortcodes/gist-vs-codeblock.md|70 col 37| [Google.Units] Put a nonbreaking space between the number and the unit in '9d'.
content/en/contribute/create/guides/shortcodes/gist-vs-codeblock.md|70 col 51| [Google.Units] Put a nonbreaking space between the number and the unit in '804d'.
content/en/contribute/create/guides/tips-tricks.md|24 col 68| [Google.Will] Avoid using ' will '.
content/en/contribute/create/guides/tips-tricks.md|79 col 4| [Google.Headings] 'Experimental Feature' should use sentence-style capitalization.
content/en/contribute/create/guides/tips-tricks.md|95 col 122| [Google.Exclamation] Don't use exclamation points in text.
content/en/contribute/create/guides/tips-tricks.md|103 col 68| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/contribute/create/guides/tips-tricks.md|103 col 130| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/contribute/create/guides/diagram-guide.md|9 col 4| [Google.Headings] '{{% heading "prereq" %}}' should use sentence-style capitalization.
content/en/contribute/create/guides/diagram-guide.md|61 col 24| [Google.FirstPerson] Avoid first-person pronouns such as 'me'.
content/en/contribute/create/guides/diagram-guide.md|129 col 24| [Google.FirstPerson] Avoid first-person pronouns such as 'me'.
content/en/contribute/create/guides/diagram-guide.md|185 col 24| [Google.FirstPerson] Avoid first-person pronouns such as 'me'.
content/en/contribute/create/github-changes.md|9 col 4| [Google.Headings] 'Open a pull request (PR) on GitHub' should use sentence-style capitalization.
content/en/contribute/create/github-changes.md|46 col 316| [Google.Exclamation] Don't use exclamation points in text.
content/en/contribute/create/github-changes.md|51 col 18| [Google.Exclamation] Don't use exclamation points in text.
content/en/contribute/create/github-changes.md|53 col 4| [Google.Headings] 'Address feedback in GitHub' should use sentence-style capitalization.
content/en/contribute/create/code-of-conduct.md|7 col 4| [Google.Headings] 'Contributor Covenant Code of Conduct' should use sentence-style capitalization.
content/en/contribute/create/code-of-conduct.md|13 col 64| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/contribute/create/code-of-conduct.md|14 col 63| [Google.We] Try to avoid using first-person plural like ' our '.
content/en/contribute/create/code-of-conduct.md|14 col 79| [Google.We] Try to avoid using first-person plural like ' our '.
content/en/contribute/create/code-of-conduct.md|56 col 71| [Google.WordList] Use 'email' instead of 'e-mail'.
content/en/contribute/create/code-of-conduct.md|64 col 72| [Google.Will] Avoid using ' will '.
content/en/contribute/create/code-of-conduct.md|64 col 110| [Google.Will] Avoid using ' will '.
content/en/contribute/create/guides/content-guide.md|20 col 262| [Google.WordList] Use 'to' instead of 'in order to'.
content/en/contribute/create/guides/content-guide.md|66 col 140| [Google.Latin] Use 'for example' instead of 'e.g.,'.
content/en/contribute/create/guides/content-guide.md|66 col 154| [Google.Will] Avoid using ' will '.
content/en/contribute/create/guides/content-guide.md|80 col 4| [Google.Units] Put a nonbreaking space between the number and the unit in '2s'.
content/en/contribute/create/guides/content-guide.md|80 col 12| [Google.Units] Put a nonbreaking space between the number and the unit in '3s'.
content/en/contribute/create/guides/content-guide.md|81 col 16| [Google.Units] Put a nonbreaking space between the number and the unit in '4s'.
content/en/contribute/create/guides/content-guide.md|143 col 24| [Google.WordList] Use 'select' instead of 'check'.
content/en/contribute/create/guides/content-guide.md|160 col 113| [Google.WordList] Use 'to' instead of 'in order to'.
content/en/contribute/create/guides/content-guide.md|196 col 24| [Google.WordList] Use 'select' instead of 'check'.
content/en/contribute/create/guides/content-guide.md|213 col 132| [Google.WordList] Use 'to' instead of 'in order to'.
content/en/contribute/create/guides/content-guide.md|250 col 24| [Google.WordList] Use 'select' instead of 'check'.
content/en/contribute/create/guides/content-guide.md|269 col 132| [Google.WordList] Use 'to' instead of 'in order to'.
content/en/contribute/create/guides/content-guide.md|287 col 4| [Google.Headings] '{{% heading "nextSteps" %}}' should use sentence-style capitalization.
content/en/continuous-deployment/try/instructions.md|17 col 269| [Google.Exclamation] Don't use exclamation points in text.
content/en/continuous-deployment/try/instructions.md|19 col 176| [Google.WordList] Use 'app' instead of 'application'.
content/en/continuous-deployment/try/instructions.md|25 col 4| [Google.Headings] '{{% heading "prereq" %}}' should use sentence-style capitalization.
content/en/continuous-deployment/try/instructions.md|37 col 359| [Google.Spacing] 't. T' should have one space.
content/en/continuous-deployment/try/instructions.md|37 col 395| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/continuous-deployment/try/instructions.md|44 col 4| [Google.Headings] 'Create the Armory CD Self-Hosted container' should use sentence-style capitalization.
content/en/continuous-deployment/try/instructions.md|67 col 123| [Google.Spacing] 'r. T' should have one space.
content/en/continuous-deployment/try/instructions.md|72 col 4| [Google.Headings] 'Use Armory CD Self-Hosted' should use sentence-style capitalization.
content/en/continuous-deployment/try/instructions.md|103 col 41| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/try/instructions.md|103 col 213| [Google.WordList] Use 'turn off' or 'off' instead of 'disabled'.
content/en/continuous-deployment/try/quickstart-quick-spin.md|17 col 4| [Google.Headings] '{{% heading "prereq" %}}' should use sentence-style capitalization.
content/en/continuous-deployment/try/quickstart-quick-spin.md|25 col 58| [Google.Units] Put a nonbreaking space between the number and the unit in '8s'.
content/en/continuous-deployment/feature-status/deprecations/pacrd-deprecation.md|11 col 23| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/feature-status/deprecations/pacrd-deprecation.md|11 col 284| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/feature-status/deprecations/pacrd-deprecation.md|17 col 50| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/continuous-deployment/feature-status/deprecations/pacrd-deprecation.md|17 col 106| [Google.We] Try to avoid using first-person plural like ' Our '.
content/en/continuous-deployment/feature-status/deprecations/pacrd-deprecation.md|17 col 247| [Google.We] Try to avoid using first-person plural like ' us '.
content/en/continuous-deployment/feature-status/deprecations/pacrd-deprecation.md|17 col 274| [Google.We] Try to avoid using first-person plural like ' We '.
content/en/continuous-deployment/feature-status/deprecations/pacrd-deprecation.md|17 col 303| [Google.WordList] Use 'to' instead of 'in order to'.
content/en/continuous-deployment/feature-status/deprecations/pacrd-deprecation.md|17 col 332| [Google.We] Try to avoid using first-person plural like ' our '.
content/en/continuous-deployment/feature-status/deprecations/pacrd-deprecation.md|19 col 62| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/continuous-deployment/feature-status/deprecations/pacrd-deprecation.md|21 col 6| [Google.FirstPerson] Avoid first-person pronouns such as ' I '.
content/en/continuous-deployment/feature-status/deprecations/pacrd-deprecation.md|23 col 46| [Google.Spacing] 's. A' should have one space.
content/en/continuous-deployment/feature-status/deprecations/pacrd-deprecation.md|25 col 11| [Google.FirstPerson] Avoid first-person pronouns such as ' I '.
content/en/continuous-deployment/feature-status/deprecations/pacrd-deprecation.md|27 col 45| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/continuous-deployment/feature-status/deprecations/pacrd-deprecation.md|29 col 19| [Google.We] Try to avoid using first-person plural like ' our '.
content/en/continuous-deployment/feature-status/deprecations/pacrd-deprecation.md|31 col 20| [Google.FirstPerson] Avoid first-person pronouns such as ' I '.
content/en/continuous-deployment/feature-status/deprecations/pacrd-deprecation.md|33 col 31| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/feature-status/deprecations/pacrd-deprecation.md|35 col 14| [Google.FirstPerson] Avoid first-person pronouns such as ' I '.
content/en/continuous-deployment/feature-status/deprecations/pacrd-deprecation.md|35 col 27| [Google.FirstPerson] Avoid first-person pronouns such as ' I '.
content/en/continuous-deployment/feature-status/deprecations/pacrd-deprecation.md|37 col 151| [Google.We] Try to avoid using first-person plural like ' our '.
content/en/continuous-deployment/feature-status/deprecations/cf-support-spec.md|10 col 4| [Google.Headings] 'Supported Cloud Foundry Versions' should use sentence-style capitalization.
content/en/continuous-deployment/feature-status/deprecations/cf-support-spec.md|14 col 4| [Google.Headings] 'Supported Resources' should use sentence-style capitalization.
content/en/continuous-deployment/feature-status/deprecations/cf-support-spec.md|47 col 4| [Google.Headings] 'Supported Operations' should use sentence-style capitalization.
content/en/continuous-deployment/feature-status/deprecations/cf-support-spec.md|49 col 85| [Google.WordList] Use 'app' instead of 'application'.
content/en/continuous-deployment/feature-status/deprecations/cf-support-spec.md|68 col 4| [Google.Headings] 'Supported Rollout Strategies' should use sentence-style capitalization.
content/en/continuous-deployment/_index.md|9 col 4| [Google.Headings] 'What is Armory Continuous Deployment?' should use sentence-style capitalization.
content/en/continuous-deployment/_index.md|17 col 39| [Google.OxfordComma] Use the Oxford comma in ' is an open source, multi-cloud Continuous Delivery and Deployment platform that provides a single pane of glass with visibility across your deployment for deployment status, infrastructure, security and '.
content/en/continuous-deployment/_index.md|17 col 270| [Google.OxfordComma] Use the Oxford comma in ' using pipelines, flexible and '.
content/en/continuous-deployment/_index.md|21 col 5| [Google.Headings] 'Kubernetes Operators for installation' should use sentence-style capitalization.
content/en/continuous-deployment/feature-status/deprecations/_index.md|13 col 58| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/feature-status/deprecations/_index.md|13 col 129| [Google.Spacing] 's. W' should have one space.
content/en/continuous-deployment/feature-status/deprecations/_index.md|13 col 132| [Google.We] Try to avoid using first-person plural like ' We '.
content/en/continuous-deployment/feature-status/deprecations/_index.md|13 col 216| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/continuous-deployment/feature-status/deprecations/_index.md|13 col 219| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/feature-status/deprecations/_index.md|13 col 341| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/continuous-deployment/feature-status/deprecations/_index.md|13 col 344| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/feature-status/deprecations/_index.md|15 col 29| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/continuous-deployment/feature-status/deprecations/_index.md|27 col 4| [Google.Headings] 'FAQ' should use sentence-style capitalization.
content/en/continuous-deployment/feature-status/deprecations/_index.md|29 col 6| [Google.Headings] 'How much notice will I receive on Feature Deprecations and End of Support?' should use sentence-style capitalization.
content/en/continuous-deployment/feature-status/deprecations/_index.md|29 col 21| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/feature-status/deprecations/_index.md|29 col 26| [Google.FirstPerson] Avoid first-person pronouns such as ' I '.
content/en/continuous-deployment/feature-status/deprecations/_index.md|31 col 174| [Google.Spacing] 'd. F' should have one space.
content/en/continuous-deployment/feature-status/deprecations/_index.md|31 col 256| [Google.We] Try to avoid using first-person plural like ' our '.
content/en/continuous-deployment/feature-status/deprecations/_index.md|33 col 136| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/feature-status/deprecations/_index.md|33 col 173| [Google.WordList] Use 'to' instead of 'in order to'.
content/en/continuous-deployment/feature-status/deprecations/_index.md|35 col 118| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/continuous-deployment/feature-status/deprecations/_index.md|41 col 9| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/feature-status/deprecations/_index.md|45 col 128| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/feature-status/deprecations/_index.md|45 col 203| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/feature-status/deprecations/_index.md|47 col 35| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/feature-status/deprecations/_index.md|47 col 205| [Google.Spacing] 'n. A' should have one space.
content/en/continuous-deployment/feature-status/deprecations/_index.md|47 col 239| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/feature-status/deprecations/_index.md|50 col 123| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/feature-status/deprecations/_index.md|52 col 12| [Google.FirstPerson] Avoid first-person pronouns such as ' I '.
content/en/continuous-deployment/feature-status/deprecations/_index.md|54 col 152| [Google.We] Try to avoid using first-person plural like ' our '.
content/en/continuous-deployment/feature-status/deprecations/halyard-deprecation.md|12 col 351| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/feature-status/deprecations/halyard-deprecation.md|15 col 60| [Google.We] Try to avoid using first-person plural like ' We '.
content/en/continuous-deployment/feature-status/deprecations/halyard-deprecation.md|19 col 43| [Google.WordList] Use 'capability' or 'feature' instead of 'functionality'.
content/en/continuous-deployment/feature-status/deprecations/halyard-deprecation.md|23 col 52| [Google.We] Try to avoid using first-person plural like ' us '.
content/en/continuous-deployment/feature-status/deprecations/halyard-deprecation.md|26 col 62| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/continuous-deployment/feature-status/deprecations/halyard-deprecation.md|27 col 26| [Google.Spacing] 'e. F' should have one space.
content/en/continuous-deployment/feature-status/deprecations/halyard-deprecation.md|31 col 6| [Google.FirstPerson] Avoid first-person pronouns such as ' I '.
content/en/continuous-deployment/feature-status/deprecations/halyard-deprecation.md|36 col 11| [Google.FirstPerson] Avoid first-person pronouns such as ' I '.
content/en/continuous-deployment/feature-status/deprecations/halyard-deprecation.md|38 col 45| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/continuous-deployment/feature-status/deprecations/halyard-deprecation.md|42 col 20| [Google.FirstPerson] Avoid first-person pronouns such as ' I '.
content/en/continuous-deployment/feature-status/deprecations/halyard-deprecation.md|44 col 70| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/feature-status/deprecations/halyard-deprecation.md|46 col 14| [Google.FirstPerson] Avoid first-person pronouns such as ' I '.
content/en/continuous-deployment/feature-status/deprecations/halyard-deprecation.md|46 col 27| [Google.FirstPerson] Avoid first-person pronouns such as ' I '.
content/en/continuous-deployment/feature-status/deprecations/halyard-deprecation.md|48 col 152| [Google.We] Try to avoid using first-person plural like ' our '.
content/en/continuous-deployment/armory-admin/aws/artifacts-ecr-connect.md|46 col 7| [Google.Exclamation] Don't use exclamation points in text.
content/en/continuous-deployment/armory-admin/fiat-create-permissions.md|20 col 13| [Google.WordList] Use 'app' instead of 'application'.
content/en/continuous-deployment/armory-admin/fiat-create-permissions.md|79 col 22| [Google.WordList] Use 'app' instead of 'application'.
content/en/continuous-deployment/armory-admin/fiat-create-permissions.md|81 col 16| [Google.WordList] Use 'app' instead of 'application'.
content/en/continuous-deployment/armory-admin/fiat-create-permissions.md|116 col 8| [Google.WordList] Use 'preceding' instead of 'above'.
content/en/continuous-deployment/armory-admin/fiat-create-permissions.md|120 col 110| [Google.WordList] Use 'app' instead of 'application'.
content/en/contribute/create/guides/docs-style-guide.md|14 col 4| [Google.Headings] '{{% heading "prereq" %}}' should use sentence-style capitalization.
content/en/contribute/create/guides/docs-style-guide.md|39 col 46| [Google.Will] Avoid using ' will '.
content/en/contribute/create/guides/docs-style-guide.md|58 col 26| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|58 col 64| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|66 col 32| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|66 col 65| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|67 col 35| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|67 col 65| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/contribute/create/guides/docs-style-guide.md|67 col 73| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|69 col 5| [Google.Headings] 'Avoid Latin phrases' should use sentence-style capitalization.
content/en/contribute/create/guides/docs-style-guide.md|75 col 16| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|75 col 22| [Google.Latin] Use 'for example' instead of 'e.g.,'.
content/en/contribute/create/guides/docs-style-guide.md|75 col 28| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|76 col 12| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|76 col 17| [Google.Latin] Use 'that is' instead of 'i.e.,'.
content/en/contribute/create/guides/docs-style-guide.md|76 col 23| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|108 col 27| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|108 col 51| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/contribute/create/guides/docs-style-guide.md|108 col 66| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|109 col 59| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|109 col 94| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|110 col 62| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/contribute/create/guides/docs-style-guide.md|118 col 15| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|118 col 36| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|123 col 264| [Google.Will] Avoid using ' will '.
content/en/contribute/create/guides/docs-style-guide.md|123 col 297| [Google.Will] Avoid using ' will '.
content/en/contribute/create/guides/docs-style-guide.md|129 col 26| [Google.Will] Avoid using ' will '.
content/en/contribute/create/guides/docs-style-guide.md|135 col 19| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|135 col 49| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|136 col 32| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|136 col 70| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|171 col 57| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|171 col 124| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|212 col 36| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|212 col 76| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/docs-style-guide.md|265 col 4| [Google.Headings] 'Inline code formatting' should use sentence-style capitalization.
content/en/contribute/create/guides/docs-style-guide.md|267 col 5| [Google.Headings] 'Use code style for inline code and commands' should use sentence-style capitalization.
content/en/contribute/create/guides/docs-style-guide.md|332 col 4| [Google.Headings] 'Versioning Armory CD examples' should use sentence-style capitalization.
content/en/contribute/create/guides/docs-style-guide.md|364 col 10| [Google.EmDash] Don't put a space before or after a dash.
content/en/contribute/create/guides/docs-style-guide.md|365 col 12| [Google.EnDash] Use an em dash ('—') instead of '–'.
content/en/contribute/create/guides/docs-style-guide.md|401 col 12| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/contribute/create/guides/docs-style-guide.md|405 col 16| [Google.WordList] Use 'select' instead of 'check'.
content/en/continuous-deployment/armory-admin/aws/artifacts-s3-configure.md|21 col 31| [Google.Spacing] 's. M' should have one space.
content/en/continuous-deployment/armory-admin/aws/artifacts-s3-configure.md|24 col 4| [Google.Headings] 'Enable S3 artifacts' should use sentence-style capitalization.
content/en/continuous-deployment/armory-admin/aws/artifacts-s3-configure.md|45 col 4| [Google.Headings] 'Add S3 account' should use sentence-style capitalization.
content/en/continuous-deployment/armory-admin/aws/exposing-spinnaker.md|14 col 4| [Google.Headings] 'DNS Preparation' should use sentence-style capitalization.
content/en/continuous-deployment/armory-admin/aws/exposing-spinnaker.md|18 col 67| [Google.WordList] Use 'to' instead of 'in order to'.
content/en/continuous-deployment/armory-admin/aws/exposing-spinnaker.md|23 col 4| [Google.Headings] 'Exposing Armory on EKS with a public Load Balancer' should use sentence-style capitalization.
content/en/continuous-deployment/armory-admin/aws/exposing-spinnaker.md|25 col 5| [Google.Headings] 'Create a LoadBalancer service' should use sentence-style capitalization.
content/en/continuous-deployment/armory-admin/aws/exposing-spinnaker.md|27 col 44| [Google.We] Try to avoid using first-person plural like ' we '.
... (Too many findings. Dropped some findings)