content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|17 col 5| [Google.OxfordComma] Use the Oxford comma in ' Feedback is important and we welcome any feedback, analysis, suggestions and '.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|17 col 31| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|17 col 208| [Google.OxfordComma] Use the Oxford comma in ' Feedback you provide will become the property of Armory and you agree that Armory may use or otherwise exploit all or part of your feedback or any derivative thereof in any manner without any further remuneration, compensation or '.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|17 col 229| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|23 col 7| [Google.OxfordComma] Use the Oxford comma in ' may, in its sole discretion, at any time, terminate or '.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|23 col 50| [Google.WordList] Use 'stop', 'exit', 'cancel', or 'end' instead of 'terminate'.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|23 col 191| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|25 col 626| [Google.Will] Avoid using ' WILL '.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|25 col 806| [Google.Will] Avoid using ' WILL '.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|25 col 873| [Google.Will] Avoid using ' WILL '.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|25 col 925| [Google.Will] Avoid using ' WILL '.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|32 col 4| [Google.Headings] 'Required Armory Operator version' should use sentence-style capitalization.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|38 col 29| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|44 col 5| [Google.Headings] 'AWS Lambda plugin migrated to OSS' should use sentence-style capitalization.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|46 col 44| [Google.Will] Avoid using ' will '.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|122 col 5| [Google.Headings] 'Bill Of Materials (BOM)' should use sentence-style capitalization.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|184 col 33| [Google.Ellipses] In general, don't use an ellipsis.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|187 col 30| [Google.Ellipses] In general, don't use an ellipsis.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|190 col 33| [Google.Ellipses] In general, don't use an ellipsis.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|193 col 31| [Google.Ellipses] In general, don't use an ellipsis.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|196 col 37| [Google.Ellipses] In general, don't use an ellipsis.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|199 col 30| [Google.Ellipses] In general, don't use an ellipsis.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|202 col 30| [Google.Ellipses] In general, don't use an ellipsis.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|206 col 30| [Google.Ellipses] In general, don't use an ellipsis.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|209 col 26| [Google.Ellipses] In general, don't use an ellipsis.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|212 col 30| [Google.Ellipses] In general, don't use an ellipsis.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|215 col 30| [Google.Ellipses] In general, don't use an ellipsis.
content/en/continuous-deployment/release-notes/rn-prerelease-armory-spinnaker/armoryspinnaker_v2-32-0-rc4.md|218 col 31| [Google.Ellipses] In general, don't use an ellipsis.

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/create/guides/add-image.md|16 col 31| [Google.FirstPerson] Avoid first-person pronouns such as 'my'.
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/approve-review/guidelines-reviewer.md|12 col 4| [Google.Headings] '{{% heading "prereq" %}}' should use sentence-style capitalization.
content/en/contribute/create/guides/page-links.md|82 col 18| [Google.We] Try to avoid using first-person plural like ' our '.
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/guides/shortcodes/tabs/file-with-tabs.md|19 col 6| [Google.Headings] 'Plain HTML' should use sentence-style capitalization.
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/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/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/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/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/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/shortcodes/overview.md|43 col 6| [Google.Headings] '{{% heading "prereq" %}}' should use sentence-style capitalization.
content/en/contribute/create/guides/shortcodes/overview.md|51 col 6| [Google.Headings] '{{% heading "installOperator" %}}' should use sentence-style capitalization.
content/en/contribute/create/guides/shortcodes/overview.md|75 col 53| [Google.Ellipses] In general, don't use an ellipsis.
content/en/contribute/create/guides/shortcodes/overview.md|86 col 90| [Google.Units] Put a nonbreaking space between the number and the unit in '7h'.
content/en/contribute/create/guides/shortcodes/overview.md|86 col 111| [Google.Units] Put a nonbreaking space between the number and the unit in '0d'.
content/en/contribute/create/guides/shortcodes/overview.md|91 col 86| [Google.Units] Put a nonbreaking space between the number and the unit in '8s'.
content/en/contribute/create/create-page.md|11 col 45| [Google.Will] Avoid using ' will '.
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/includes/install/docker-note.md|1 col 202| [Google.Spacing] 'r. T' should have one space.
content/en/includes/install/docker-note.md|3 col 17| [Google.Will] Avoid using ' will '.
content/en/includes/lts-beta.md|3 col 5| [Google.OxfordComma] Use the Oxford comma in ' Feedback is important and we welcome any feedback, analysis, suggestions and '.
content/en/includes/lts-beta.md|3 col 31| [Google.We] Try to avoid using first-person plural like ' we '.
content/en/includes/lts-beta.md|3 col 208| [Google.OxfordComma] Use the Oxford comma in ' Feedback you provide will become the property of Armory and you agree that Armory may use or otherwise exploit all or part of your feedback or any derivative thereof in any manner without any further remuneration, compensation or '.
content/en/includes/lts-beta.md|3 col 229| [Google.Will] Avoid using ' will '.
content/en/includes/lts-beta.md|9 col 7| [Google.OxfordComma] Use the Oxford comma in ' may, in its sole discretion, at any time, terminate or '.
content/en/includes/lts-beta.md|9 col 50| [Google.WordList] Use 'stop', 'exit', 'cancel', or 'end' instead of 'terminate'.
content/en/includes/lts-beta.md|9 col 191| [Google.Will] Avoid using ' will '.
content/en/includes/lts-beta.md|11 col 626| [Google.Will] Avoid using ' WILL '.
content/en/includes/lts-beta.md|11 col 806| [Google.Will] Avoid using ' WILL '.
content/en/includes/lts-beta.md|11 col 873| [Google.Will] Avoid using ' WILL '.
content/en/includes/lts-beta.md|11 col 925| [Google.Will] Avoid using ' WILL '.
content/en/includes/admin/tls/what-you-need.md|34 col 23| [Google.Will] Avoid using ' will '.
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/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.
content/en/includes/release-notes/agent/ki-permissions-whitespace.md|12 col 207| [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/includes/release-notes/gcs-hal-op.md|1 col 1| [Google.Headings] 'Google Cloud Storage (GCS) config missing ************** fails' should use sentence-style capitalization.
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|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/includes/breaking-changes/bc-kubectl-120.md|5 col 74| [Google.Spacing] 'e. Y' should have one space.
content/en/includes/breaking-changes/bc-kubectl-120.md|5 col 206| [Google.Spacing] 'd. L' should have one space.
content/en/includes/breaking-changes/bc-kubectl-120.md|5 col 303| [Google.Spacing] 'r. F' should have one space.
content/en/includes/breaking-changes/bc-java-tls-communication-failure.md|3 col 86| [Google.Will] Avoid using ' will '.
content/en/includes/breaking-changes/bc-java-tls-communication-failure.md|11 col 63| [Google.Will] Avoid using ' will '.
content/en/includes/breaking-changes/bc-java-tls-communication-failure.md|11 col 120| [Google.Will] Avoid using ' will '.
content/en/includes/breaking-changes/bc-docker-giduid.md|1 col 6| [Google.Headings] 'Spinnaker Dockerfile GID/UID changes' should use sentence-style capitalization.
content/en/includes/breaking-changes/bc-terraform-older-than-013.md|1 col 5| [Google.Headings] 'Supported Terraform Versions' should use sentence-style capitalization.
content/en/includes/breaking-changes/bc-plugin-compatibility-2-28-0.md|1 col 5| [Google.Headings] 'Plugin Compatibility' should use sentence-style capitalization.
content/en/includes/breaking-changes/bc-git-artifact-constraint.md|2 col 6| [Google.Headings] 'Git Artifact Constraint Trigger' should use sentence-style capitalization.
content/en/includes/breaking-changes/bc-git-artifact-constraint.md|4 col 113| [Google.Will] Avoid using ' will '.
content/en/includes/breaking-changes/bc-git-artifact-constraint.md|5 col 87| [Google.Ellipses] In general, don't use an ellipsis.
content/en/includes/breaking-changes/bc-orca-forcecacherefresh.md|1 col 6| [Google.Headings] 'ManifestForceCacheRefreshTask removed from Orca' should use sentence-style capitalization.
content/en/includes/breaking-changes/bc-orca-forcecacherefresh.md|31 col 15| [Google.OptionalPlurals] Don't use plurals in parentheses such as in 'message(s)'.
content/en/includes/breaking-changes/bc-k8s-job-suffix.md|3 col 314| [Google.Will] Avoid using ' will '.
content/en/includes/breaking-changes/bc-k8s-job-suffix.md|15 col 43| [Google.Will] Avoid using ' will '.
content/en/includes/breaking-changes/bc-k8s-job-suffix.md|15 col 91| [Google.WordList] Use 'preceding' instead of 'above'.
content/en/includes/breaking-changes/bc-k8s-job-suffix.md|15 col 104| [Google.Will] Avoid using ' will '.
content/en/includes/breaking-changes/bc-k8s-job-suffix.md|15 col 139| [Google.Will] Avoid using ' will '.
content/en/includes/breaking-changes/bc-k8s-job-suffix.md|15 col 184| [Google.We] Try to avoid using first-person plural like ' We '.
content/en/includes/breaking-changes/bc-k8s-v2-provider-aws-iam-auth.md|5 col 226| [Google.Units] Put a nonbreaking space between the number and the unit in '8s'.
content/en/includes/breaking-changes/bc-k8s-v2-provider-aws-iam-auth.md|5 col 347| [Google.Units] Put a nonbreaking space between the number and the unit in '8s'.
content/en/includes/breaking-changes/bc-k8s-v2-provider-aws-iam-auth.md|5 col 467| [Google.Units] Put a nonbreaking space between the number and the unit in '8s'.
content/en/includes/breaking-changes/bc-spinnaker-metrics.md|15 col 18| [Google.Will] Avoid using ' will '.
content/en/includes/breaking-changes/bc-orca-rdbms-configured-utf8.md|1 col 5| [Google.Headings] 'Orca requires RDBMS configured with UTF-8 encoding' should use sentence-style capitalization.
content/en/includes/breaking-changes/bc-orca-rdbms-configured-utf8.md|3 col 71| [Google.We] Try to avoid using first-person plural like ' We '.
content/en/includes/breaking-changes/bc-plugin-compatibility-2-30-0.md|16 col 64| [Google.Units] Put a nonbreaking space between the number and the unit in '8s'.
content/en/includes/breaking-changes/bc-k8s-infra-buttons.md|5 col 66| [Google.WordList] Use 'app' instead of 'application'.
content/en/includes/breaking-changes/bc-k8s-infra-buttons.md|23 col 110| [Google.WordList] Use 'app' instead of 'application'.
content/en/includes/breaking-changes/bc-k8s-infra-buttons.md|25 col 8| [Google.WordList] Use 'app' instead of 'application'.
content/en/includes/breaking-changes/bc-k8s-infra-buttons.md|30 col 8| [Google.WordList] Use 'app' instead of 'application'.
content/en/includes/breaking-changes/bc-k8s-infra-buttons.md|33 col 192| [Google.WordList] Use 'app' instead of 'application'.
content/en/includes/known-issues/ki-saml-authn.md|2 col 6| [Google.Headings] 'SAML Authentication' should use sentence-style capitalization.
content/en/includes/known-issues/ki-plugins-sdk.md|1 col 6| [Google.Headings] 'Orca Plugins using Plugin SDK' should use sentence-style capitalization.
content/en/includes/known-issues/ki-plugins-sdk.md|12 col 68| [Google.Will] Avoid using ' will '.
content/en/includes/breaking-changes/bc-k8s-version-pre1-16.md|9 col 41| [Google.Units] Put a nonbreaking space between the number and the unit in '8s'.
content/en/includes/breaking-changes/bc-java-tls-mysql.md|7 col 86| [Google.Will] Avoid using ' will '.
content/en/includes/breaking-changes/bc-java-tls-mysql.md|15 col 63| [Google.Will] Avoid using ' will '.
content/en/includes/known-issues/ki-aws-iam-token.md|1 col 6| [Google.Headings] 'AWS IAM tokens' should use sentence-style capitalization.
content/en/includes/known-issues/ki-app-eng-acct-auth.md|1 col 5| [Google.Headings] 'Google App Engine account authentication' should use sentence-style capitalization.
content/en/includes/known-issues/ki-app-eng-acct-auth.md|3 col 73| [Google.Spacing] 'r. T' should have one space.
content/en/includes/known-issues/ki-app-eng-acct-auth.md|3 col 175| [Google.Spacing] 'm. S' should have one space.
content/en/includes/known-issues/ki-app-eng-acct-auth.md|3 col 344| [Google.Spacing] 'n. T' should have one space.
content/en/includes/known-issues/ki-app-eng-acct-auth.md|3 col 548| [Google.Spacing] 'd. A' should have one space.
content/en/includes/known-issues/ki-healthchecks-dynamicAccounts.md|9 col 12| [Google.WordList] Use 'select' instead of 'check'.
content/en/includes/known-issues/ki-custom-job-stage.md|2 col 6| [Google.Headings] 'Custom Job Stages' should use sentence-style capitalization.
content/en/includes/known-issues/ki-secrets-and-spring-cloud.md|1 col 6| [Google.Headings] 'Secrets do not work with Spring Cloud Config' should use sentence-style capitalization.
content/en/includes/known-issues/ki-secrets-and-spring-cloud.md|5 col 2| [Google.Latin] Use 'for example' instead of 'e.g.'.
content/en/includes/known-issues/ki-artifact-binding-spel.md|2 col 6| [Google.Headings] 'SpEL expressions and artifact binding' should use sentence-style capitalization.
content/en/includes/known-issues/ki-dinghy-gh-notifications.md|2 col 6| [Google.Headings] 'Pipelines-as-Code GitHub comments' should use sentence-style capitalization.
content/en/includes/known-issues/ki-dinghy-gh-notifications.md|12 col 36| [Google.WordList] Use 'turn off' or 'off' instead of 'disable'.
content/en/includes/known-issues/ki-lambda-ui-caching.md|1 col 6| [Google.Headings] 'Lambda UI issue' should use sentence-style capitalization.
content/en/includes/known-issues/ki-lambda-ui-caching.md|3 col 227| [Google.Spacing] 'n. I' should have one space.
content/en/includes/known-issues/ki-aws-image-cache.md|1 col 6| [Google.Headings] 'AWS image caching' should use sentence-style capitalization.
content/en/includes/known-issues/ki-aws-image-cache.md|13 col 254| [Google.WordList] Use 'regular expression' instead of 'regex'.