_data-prepper/pipelines/configuration/sinks/opensearch.md|92 col 98| [OpenSearch.Spelling] Error: aws. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_data-prepper/pipelines/configuration/sinks/opensearch.md|92 col 98| [OpenSearch.HeadingCapitalization] 'aws' is a heading and should be in sentence case.

.github/ISSUE_TEMPLATE/issue_template.md|19 col 99| [OpenSearch.LatinismsElimination] Using 'etc.' is unnecessary. Remove.
.github/PULL_REQUEST_TEMPLATE.md|4 col 5| [OpenSearch.HeadingCapitalization] 'Issues Resolved' is a heading and should be in sentence case.
.github/PULL_REQUEST_TEMPLATE.md|10 col 1| [OpenSearch.SubstitutionsError] Use 'for more information about' instead of 'For more information on'.
.github/PULL_REQUEST_TEMPLATE.md|10 col 97| [OpenSearch.Please] Using 'please' is unnecessary. Remove.
.github/ISSUE_TEMPLATE/broken_links.md|7 col 1| [OpenSearch.Please] Using 'Please' is unnecessary. Remove.
.github/vale/tests/test-headings.md|37 col 10| [OpenSearch.HeadingColon] Capitalize the word after a colon in ': should'.
.github/vale/tests/test-headings.md|41 col 12| [OpenSearch.HeadingColon] Capitalize the word after a colon in ': should'.
.github/vale/tests/test-headings.md|45 col 30| [OpenSearch.HeadingColon] Capitalize the word after a colon in ': should'.
.github/vale/tests/test-headings.md|49 col 30| [OpenSearch.HeadingColon] Capitalize the word after a colon in ': should'.
.github/vale/tests/test-headings.md|53 col 10| [OpenSearch.HeadingColon] Capitalize the word after a colon in ': with'.
.github/vale/tests/test-headings.md|57 col 3| [OpenSearch.HeadingCapitalization] 'this should be flagged' is a heading and should be in sentence case.
.github/vale/tests/test-headings.md|61 col 3| [OpenSearch.HeadingCapitalization] 'This Should Be Flagged' is a heading and should be in sentence case.
.github/vale/tests/test-style-pos.md|5 col 21| [OpenSearch.Spelling] Error: cyber. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
.github/vale/tests/test-style-pos.md|5 col 21| [OpenSearch.Cyber] Use 'cyber' as a prefix. Remove spaces or hyphens in 'cyber security'.
.github/vale/tests/test-style-pos.md|7 col 21| [OpenSearch.DashSpacing] There should be no spaces around the dash in 'dash --- spacing'.
.github/vale/tests/test-style-pos.md|9 col 25| [OpenSearch.DirectionAboveBelow] Use 'preceding table' instead of 'table above' for versions or orientation within a document. Use 'above' and 'below' only for physical space or screen descriptions.
.github/vale/tests/test-style-pos.md|9 col 49| [OpenSearch.DirectionAboveBelow] Use 'earlier' instead of '1.2 and below' for versions or orientation within a document. Use 'above' and 'below' only for physical space or screen descriptions.
.github/vale/tests/test-style-pos.md|11 col 21| [OpenSearch.DirectionTopBottom] Use 'upper-right' instead of 'top-right' for window, page, or pane references to features or controls. Use 'top' and 'bottom' only as a general screen reference.
.github/vale/tests/test-style-pos.md|11 col 35| [OpenSearch.DirectionTopBottom] Use 'lower left' instead of 'bottom left' for window, page, or pane references to features or controls. Use 'top' and 'bottom' only as a general screen reference.
.github/vale/tests/test-style-pos.md|13 col 33| [OpenSearch.Exclamation] Don't use exclamation points in documentation.
.github/vale/tests/test-style-pos.md|15 col 21| [OpenSearch.FailoverNoun] Use 'failover' as an adjective or noun instead of 'fail-over'.
.github/vale/tests/test-style-pos.md|15 col 35| [OpenSearch.FailoverVerb] Use 'fail over' as a verb instead of 'failover'.
.github/vale/tests/test-style-pos.md|19 col 40| [OpenSearch.HeadingAcronyms] '(HA)': Don't define acronyms in headings.
.github/vale/tests/test-style-pos.md|21 col 70| [OpenSearch.Inclusive] Use 'stop, end, clear, remove, or cancel' instead of 'kill' because the latter is an offensive term.
.github/vale/tests/test-style-pos.md|23 col 4| [OpenSearch.HeadingCapitalization] 'This heading tests Capitalization' is a heading and should be in sentence case.
.github/vale/tests/test-style-pos.md|25 col 40| [OpenSearch.LatinismsElimination] Using 'etc.' is unnecessary. Remove.
.github/vale/tests/test-style-pos.md|27 col 41| [OpenSearch.HeadingPunctuation] Don't use punctuation at the end of a heading.
.github/vale/tests/test-style-pos.md|29 col 40| [OpenSearch.LatinismsSubstitution] Use 'using, through, by accessing, or by choosing' instead of 'via'.
.github/vale/tests/test-style-pos.md|31 col 16| [OpenSearch.HeadingColon] Capitalize the word after a colon in ': tests'.
.github/vale/tests/test-style-pos.md|33 col 46| [OpenSearch.LinksDoubleParentheses] Remove double parentheses from the link '](({{site.url}}{{site.baseurl}}/opensearch/))'.
.github/vale/tests/test-style-pos.md|35 col 41| [OpenSearch.LinksDoubleSlash] Remove double slashes from the link '({{site.url}}{{site.baseurl}}/opensearch//double-slash/)'.
.github/vale/tests/test-style-pos.md|37 col 38| [OpenSearch.LinksEndSlash] Add a trailing slash to the link '({{site.url}}{{site.baseurl}}/opensearch)'.
.github/vale/tests/test-style-pos.md|39 col 38| [OpenSearch.LinksMidSlash] Add a slash after '{{site.url}}/{{site.baseurl}}' in '({{site.url}}{{site.baseurl}}opensearch)'.
.github/vale/tests/test-style-pos.md|41 col 21| [OpenSearch.LoginNoun] Use 'login' as an adjective or noun instead of 'log-in'.
.github/vale/tests/test-style-pos.md|41 col 42| [OpenSearch.LoginVerb] Use 'log in' as a verb instead of 'login'.
.github/vale/tests/test-style-pos.md|45 col 21| [OpenSearch.OxfordComma] Add an Oxford comma in 'periods, colons and commas.'.
.github/vale/tests/test-style-pos.md|49 col 1| [OpenSearch.Please] Using 'Please' is unnecessary. Remove.
.github/vale/tests/test-style-pos.md|51 col 31| [OpenSearch.DashSpacing] There should be no spaces around the dash in '2 -- 5'.
.github/vale/tests/test-style-pos.md|53 col 21| [OpenSearch.Repetition] 'repetition' is repeated.
.github/vale/tests/test-style-pos.md|55 col 21| [OpenSearch.RolloverNoun] Use 'rollover' as an adjective or noun instead of 'roll-over'.
.github/vale/tests/test-style-pos.md|55 col 45| [OpenSearch.RolloverVerb] Use 'roll over' as a verb instead of 'rollover'.
.github/vale/tests/test-style-pos.md|57 col 21| [OpenSearch.SetupNoun] Use 'setup' as an adjective or noun instead of 'set-up'.
.github/vale/tests/test-style-pos.md|57 col 42| [OpenSearch.SetupVerb] Use 'set up' as a verb instead of 'setup'.
.github/vale/tests/test-style-pos.md|59 col 21| [OpenSearch.SignatureV4] 'AWS Signature Version 4': Use 'AWS Signature Version 4' instead of 'AWS SigV4' on first appearance. Then, Signature Version 4 may be used. Only use SigV4 when space is limited.
.github/vale/tests/test-style-pos.md|59 col 35| [OpenSearch.SignatureV4] 'Signature Version 4': Use 'AWS Signature Version 4' instead of 'sigv4' on first appearance. Then, Signature Version 4 may be used. Only use SigV4 when space is limited.
.github/vale/tests/test-style-pos.md|61 col 15| [OpenSearch.Simple] Don't use 'simply' because it's not neutral in tone. If you mean 'only', use 'only' instead.
.github/vale/tests/test-style-pos.md|61 col 49| [OpenSearch.Simple] Don't use 'just' because it's not neutral in tone. If you mean 'only', use 'only' instead.
.github/vale/tests/test-style-pos.md|63 col 11| [OpenSearch.SpacingPunctuation] There should be no space before and one space after the punctuation mark in 'sentences. Test'.
.github/vale/tests/test-style-pos.md|65 col 25| [OpenSearch.SpacingSlash] When using '/' between words, do not insert space on either side of it.
.github/vale/tests/test-style-pos.md|67 col 15| [OpenSearch.SpacingWords] There should be once space between words in 'tests word'.
.github/vale/tests/test-style-pos.md|69 col 21| [OpenSearch.Spelling] Error: splling. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
.github/vale/tests/test-style-pos.md|73 col 1| [OpenSearch.StackedHeadings] Do not stack headings. Insert an introductory sentence between headings.
.github/vale/tests/test-style-pos.md|75 col 58| [OpenSearch.SubstitutionsError] Use 'indexes' instead of 'indices'.
.github/vale/tests/test-style-pos.md|79 col 1| [OpenSearch.TableHeadings] 'This Table' is a table heading and should be in sentence case.
.github/vale/tests/test-style-pos.md|79 col 14| [OpenSearch.TableHeadings] 'tests capitalization' is a table heading and should be in sentence case.
.github/vale/tests/test-style-pos.md|83 col 21| [OpenSearch.TimeoutNoun] Use 'timeout' as an adjective or noun instead of 'time-out'.
.github/vale/tests/test-style-pos.md|83 col 44| [OpenSearch.TimeoutVerb] Use 'time out' as a verb instead of 'timeout'.
.github/vale/tests/test-style-pos.md|85 col 23| [OpenSearch.UnitsNames] Use 'KB' instead of 'kb'.
.github/vale/tests/test-style-pos.md|87 col 21| [OpenSearch.UnitsSpacing] Put a space between the number and the units in '2KB '.
.github/vale/tests/test-style-pos.md|89 col 21| [OpenSearch.Version] In 'v1.2', spell out 'version'.
.github/vale/tests/test-style-pos.md|91 col 36| [Vale.Terms] Use 'Security plugin' instead of 'security plugin'.
_automating-configurations/api/create-workflow.md|81 col 70| [OpenSearch.HeadingAcronyms] '(YAML)': Don't define acronyms in headings.
_reporting/rep-cli-index.md|35 col 15| [OpenSearch.AcronymParentheses] 'CLI': Spell out acronyms the first time that you use them on a page and follow them with the acronym in parentheses. Subsequently, use the acronym alone.
_reporting/rep-cli-index.md|35 col 195| [OpenSearch.AcronymParentheses] 'CLI': Spell out acronyms the first time that you use them on a page and follow them with the acronym in parentheses. Subsequently, use the acronym alone.
_reporting/rep-cli-index.md|37 col 46| [OpenSearch.AcronymParentheses] 'CLI': Spell out acronyms the first time that you use them on a page and follow them with the acronym in parentheses. Subsequently, use the acronym alone.
_reporting/rep-cli-install.md|13 col 69| [OpenSearch.Spelling] Error: npm. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_reporting/rep-cli-install.md|15 col 25| [OpenSearch.Spelling] Error: npm. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_reporting/rep-cli-install.md|15 col 57| [OpenSearch.Spelling] Error: npm. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_reporting/rep-cli-install.md|17 col 54| [OpenSearch.Spelling] Error: npm. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_reporting/rep-cli-install.md|19 col 48| [OpenSearch.Spelling] Error: npm. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_reporting/rep-cli-env-var.md|73 col 99| [OpenSearch.AcronymParentheses] 'SMTP': Spell out acronyms the first time that you use them on a page and follow them with the acronym in parentheses. Subsequently, use the acronym alone.
_reporting/rep-cli-env-var.md|96 col 9| [OpenSearch.Spelling] Error: zsh. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_monitoring-your-cluster/index.md|19 col 4| [Vale.Terms] Use 'Performance Analyzer' instead of 'Performance analyzer'.
_reporting/rep-cli-create.md|17 col 117| [OpenSearch.Spelling] Error: Shapshot. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_reporting/rep-cli-options.md|24 col 79| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_reporting/rep-cli-options.md|28 col 65| [OpenSearch.AcronymParentheses] 'SMTP': Spell out acronyms the first time that you use them on a page and follow them with the acronym in parentheses. Subsequently, use the acronym alone.
_reporting/rep-cli-options.md|28 col 90| [OpenSearch.AcronymParentheses] 'SMTP': Spell out acronyms the first time that you use them on a page and follow them with the acronym in parentheses. Subsequently, use the acronym alone.
_reporting/rep-cli-options.md|29 col 66| [OpenSearch.AcronymParentheses] 'SMTP': Spell out acronyms the first time that you use them on a page and follow them with the acronym in parentheses. Subsequently, use the acronym alone.
_reporting/rep-cli-options.md|29 col 91| [OpenSearch.AcronymParentheses] 'SMTP': Spell out acronyms the first time that you use them on a page and follow them with the acronym in parentheses. Subsequently, use the acronym alone.
_reporting/rep-cli-options.md|30 col 86| [OpenSearch.AcronymParentheses] 'SMTP': Spell out acronyms the first time that you use them on a page and follow them with the acronym in parentheses. Subsequently, use the acronym alone.
_reporting/rep-cli-lambda.md|107 col 59| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_reporting/rep-cli-lambda.md|122 col 91| [Vale.Terms] Use 'Lambda' instead of 'lambda'.
_reporting/rep-cli-lambda.md|123 col 57| [OpenSearch.UnitsSpacing] Put a space between the number and the units in '1024MB.'.
_monitoring-your-cluster/pa/rca/api.md|13 col 1| [OpenSearch.StackedHeadings] Do not stack headings. Insert an introductory sentence between headings.
_monitoring-your-cluster/pa/rca/shard-hotspot.md|92 col 136| [OpenSearch.Spelling] Error: cpu. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_monitoring-your-cluster/pa/rca/shard-hotspot.md|93 col 125| [OpenSearch.Spelling] Error: cpu. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_monitoring-your-cluster/pa/rca/shard-hotspot.md|93 col 159| [OpenSearch.Spelling] Error: alloc. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_monitoring-your-cluster/pa/rca/shard-hotspot.md|93 col 175| [OpenSearch.Spelling] Error: alloc. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_monitoring-your-cluster/job-scheduler/index.md|21 col 164| [OpenSearch.AcronymParentheses] 'README': Spell out acronyms the first time that you use them on a page and follow them with the acronym in parentheses. Subsequently, use the acronym alone.
_monitoring-your-cluster/job-scheduler/index.md|76 col 14| [OpenSearch.Spelling] Error: isEnabled. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_monitoring-your-cluster/job-scheduler/index.md|122 col 3| [OpenSearch.Spelling] Error: getName. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_monitoring-your-cluster/job-scheduler/index.md|125 col 3| [OpenSearch.Spelling] Error: getSchedule. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_monitoring-your-cluster/job-scheduler/index.md|128 col 3| [OpenSearch.Spelling] Error: getJitter. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_monitoring-your-cluster/pa/dashboards.md|98 col 84| [OpenSearch.SpacingPunctuation] There should be no space before and one space after the punctuation mark in 'tables. To'.
_monitoring-your-cluster/pa/dashboards.md|103 col 107| [OpenSearch.Simple] Don't use 'just' because it's not neutral in tone. If you mean 'only', use 'only' instead.
_tuning-your-cluster/availability-and-recovery/snapshots/searchable_snapshot.md|44 col 1| [OpenSearch.TableHeadings] 'Request Field' is a table heading and should be in sentence case.
_monitoring-your-cluster/pa/reference.md|189 col 68| [OpenSearch.Spelling] Error: fielddata. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_monitoring-your-cluster/pa/reference.md|195 col 11| [OpenSearch.Spelling] Error: Fielddata. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_monitoring-your-cluster/pa/reference.md|671 col 137| [Vale.Terms] Use 'Point in Time' instead of 'point in time'.
_monitoring-your-cluster/pa/reference.md|783 col 50| [OpenSearch.Spelling] Error: n. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_monitoring-your-cluster/pa/reference.md|783 col 119| [OpenSearch.Spelling] Error: n. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_monitoring-your-cluster/pa/reference.md|849 col 50| [OpenSearch.Spelling] Error: n. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_monitoring-your-cluster/pa/reference.md|849 col 120| [OpenSearch.Spelling] Error: n. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_tuning-your-cluster/availability-and-recovery/search-backpressure.md|123 col 4| [OpenSearch.HeadingCapitalization] 'Search Backpressure Stats API' is a heading and should be in sentence case.
_tuning-your-cluster/availability-and-recovery/search-backpressure.md|127 col 44| [OpenSearch.LinksEndSlash] Add a trailing slash to the link '({{site.url}}{{site.baseurl}}/api-reference/nodes-apis/nodes-stats)'.
_tuning-your-cluster/availability-and-recovery/search-backpressure.md|223 col 1| [OpenSearch.TableHeadings] 'Field Name' is a table heading and should be in sentence case.
_tuning-your-cluster/availability-and-recovery/search-backpressure.md|242 col 1| [OpenSearch.TableHeadings] 'Field Name' is a table heading and should be in sentence case.
_tuning-your-cluster/availability-and-recovery/search-backpressure.md|252 col 1| [OpenSearch.TableHeadings] 'Field Name' is a table heading and should be in sentence case.
_tuning-your-cluster/availability-and-recovery/search-backpressure.md|263 col 1| [OpenSearch.TableHeadings] 'Field Name' is a table heading and should be in sentence case.
_tuning-your-cluster/availability-and-recovery/search-backpressure.md|273 col 1| [OpenSearch.TableHeadings] 'Field Name' is a table heading and should be in sentence case.
_tuning-your-cluster/availability-and-recovery/snapshots/sm-api.md|12 col 3| [OpenSearch.HeadingCapitalization] 'Snapshot Management API' is a heading and should be in sentence case.
_tuning-your-cluster/availability-and-recovery/snapshots/sm-api.md|190 col 63| [OpenSearch.SubstitutionsError] Use 'key-value' instead of 'key/value'.
_tuning-your-cluster/availability-and-recovery/snapshots/sm-api.md|202 col 126| [OpenSearch.LinksEndSlash] Add a trailing slash to the link '({{site.url}}{{site.baseurl}}/notifications-plugin/api)'.
_tuning-your-cluster/availability-and-recovery/snapshots/sm-api.md|356 col 77| [OpenSearch.DirectionAboveBelow] Use 'following or later' instead of 'below' for versions or orientation within a document. Use 'above' and 'below' only for physical space or screen descriptions.
_tuning-your-cluster/availability-and-recovery/snapshots/sm-api.md|357 col 77| [OpenSearch.DirectionAboveBelow] Use 'following or later' instead of 'below' for versions or orientation within a document. Use 'above' and 'below' only for physical space or screen descriptions.
_tuning-your-cluster/availability-and-recovery/snapshots/sm-api.md|365 col 108| [OpenSearch.DirectionAboveBelow] Use 'previous, preceding, or earlier' instead of 'above' for versions or orientation within a document. Use 'above' and 'below' only for physical space or screen descriptions.
_tuning-your-cluster/availability-and-recovery/remote-store/remote-store-stats-api.md|9 col 3| [OpenSearch.HeadingCapitalization] 'Remote Store Stats API' is a heading and should be in sentence case.
_tuning-your-cluster/availability-and-recovery/remote-store/remote-store-stats-api.md|268 col 6| [OpenSearch.HeadingCapitalization] 'routing' is a heading and should be in sentence case.
_tuning-your-cluster/availability-and-recovery/remote-store/remote-store-stats-api.md|277 col 6| [OpenSearch.HeadingCapitalization] 'segment' is a heading and should be in sentence case.
_tuning-your-cluster/availability-and-recovery/remote-store/snapshot-interoperability.md|15 col 1| [OpenSearch.Repetition] 'to' is repeated.
_tuning-your-cluster/availability-and-recovery/snapshots/snapshot-management.md|14 col 222| [OpenSearch.LinksEndSlash] Add a trailing slash to the link '({{site.url}}{{site.baseurl}}/im-plugin)'.
_tuning-your-cluster/availability-and-recovery/snapshots/snapshot-management.md|60 col 99| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_tuning-your-cluster/availability-and-recovery/snapshots/snapshot-management.md|61 col 155| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_tuning-your-cluster/availability-and-recovery/snapshots/snapshot-management.md|62 col 77| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_tuning-your-cluster/availability-and-recovery/snapshots/snapshot-management.md|63 col 77| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_tuning-your-cluster/availability-and-recovery/snapshots/snapshot-management.md|64 col 74| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_tuning-your-cluster/availability-and-recovery/snapshots/snapshot-management.md|65 col 71| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_tuning-your-cluster/availability-and-recovery/snapshots/snapshot-management.md|70 col 56| [OpenSearch.LinksEndSlash] Add a trailing slash to the link '({{site.url}}{{site.baseurl}}/opensearch/snapshots/sm-api)'.
_tuning-your-cluster/availability-and-recovery/snapshots/snapshot-restore.md|40 col 104| [OpenSearch.Simple] Don't use 'just' because it's not neutral in tone. If you mean 'only', use 'only' instead.
_tuning-your-cluster/availability-and-recovery/snapshots/snapshot-restore.md|166 col 42| [OpenSearch.DirectionAboveBelow] Use 'previous, preceding, or earlier' instead of 'above' for versions or orientation within a document. Use 'above' and 'below' only for physical space or screen descriptions.
_tuning-your-cluster/availability-and-recovery/snapshots/snapshot-restore.md|313 col 1| [OpenSearch.Simple] Don't use 'Just' because it's not neutral in tone. If you mean 'only', use 'only' instead.
_tuning-your-cluster/availability-and-recovery/snapshots/snapshot-restore.md|360 col 276| [OpenSearch.Simple] Don't use 'just' because it's not neutral in tone. If you mean 'only', use 'only' instead.
_tuning-your-cluster/availability-and-recovery/shard-indexing-backpressure.md|26 col 82| [OpenSearch.Simple] Don't use 'just' because it's not neutral in tone. If you mean 'only', use 'only' instead.
_tuning-your-cluster/availability-and-recovery/remote-store/index.md|63 col 45| [OpenSearch.LinksDoubleSlash] Remove double slashes from the link '({{site.url}}{{site.baseurl}}//api-reference/cluster-api/cluster-settings/)'.
_tuning-your-cluster/cluster-manager-task-throttling.md|22 col 150| [OpenSearch.LinksEndSlash] Add a trailing slash to the link '({{site.url}}{{site.baseurl}}/api-reference/cluster-settings)'.
_tuning-your-cluster/cluster-manager-task-throttling.md|44 col 1| [OpenSearch.TableHeadings] 'Field Name' is a table heading and should be in sentence case.
_tuning-your-cluster/replication-plugin/getting-started.md|190 col 239| [OpenSearch.DashSpacing] There should be no spaces around the dash in 'scratch -- you'.
_tuning-your-cluster/replication-plugin/getting-started.md|240 col 35| [OpenSearch.HeadingCapitalization] 'index' is a heading and should be in sentence case.
_tools/grafana.md|10 col 92| [OpenSearch.SubstitutionsError] Use 'for information about' instead of 'For information on'.
_tools/k8s-operator.md|8 col 54| [OpenSearch.Spelling] Error: kubernetes. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_tools/k8s-operator.md|8 col 54| [Vale.Terms] Use 'Kubernetes' instead of 'kubernetes'.
_tools/k8s-operator.md|53 col 4| [OpenSearch.Spelling] Error: minikube. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_tools/k8s-operator.md|53 col 4| [Vale.Terms] Use 'Minikube' instead of 'minikube'.
_tools/k8s-operator.md|55 col 125| [OpenSearch.Spelling] Error: minikube. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_tools/k8s-operator.md|55 col 125| [Vale.Terms] Use 'Minikube' instead of 'minikube'.
_tools/k8s-operator.md|62 col 43| [Vale.Terms] Use 'Minikube' instead of 'minikube'.
_tools/k8s-operator.md|62 col 43| [OpenSearch.Spelling] Error: minikube. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_tuning-your-cluster/performance.md|121 col 53| [OpenSearch.Spelling] Error: NVMe. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_tools/index.md|43 col 2| [OpenSearch.Simple] Don't use 'Just' because it's not neutral in tone. If you mean 'only', use 'only' instead.
_tools/index.md|59 col 137| [OpenSearch.DirectionAboveBelow] Use 'following or later' instead of 'below' for versions or orientation within a document. Use 'above' and 'below' only for physical space or screen descriptions.
_tools/index.md|85 col 31| [OpenSearch.LatinismsSubstitution] Use 'using, through, by accessing, or by choosing' instead of 'via'.
_tools/index.md|85 col 57| [OpenSearch.LatinismsSubstitution] Use 'using, through, by accessing, or by choosing' instead of 'via'.
_tools/index.md|90 col 5| [OpenSearch.HeadingCapitalization] 'Compatibility matrix for Beats' is a heading and should be in sentence case.
_tools/index.md|98 col 31| [OpenSearch.LatinismsSubstitution] Use 'using, through, by accessing, or by choosing' instead of 'via'.
_tools/index.md|98 col 57| [OpenSearch.LatinismsSubstitution] Use 'using, through, by accessing, or by choosing' instead of 'via'.
_tools/index.md|114 col 44| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_tuning-your-cluster/index.md|23 col 28| [OpenSearch.Inclusive] Use 'cluster manager' instead of 'master' because the latter is an offensive term.
_tuning-your-cluster/index.md|126 col 213| [OpenSearch.Spelling] Error: loopback. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_tuning-your-cluster/index.md|150 col 61| [OpenSearch.Spelling] Error: unicast. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_tuning-your-cluster/index.md|168 col 88| [OpenSearch.Spelling] Error: systemd. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_tuning-your-cluster/index.md|195 col 1| [OpenSearch.StackedHeadings] Do not stack headings. Insert an introductory sentence between headings.
_tuning-your-cluster/index.md|199 col 240| [OpenSearch.Simple] Don't use 'just' because it's not neutral in tone. If you mean 'only', use 'only' instead.
_tuning-your-cluster/index.md|251 col 70| [OpenSearch.Spelling] Error: hotspots. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_tuning-your-cluster/index.md|353 col 1| [OpenSearch.Repetition] 'to' is repeated.
_tools/logstash/common-filters.md|14 col 4| [OpenSearch.HeadingCapitalization] 'mutate' is a heading and should be in sentence case.
_tools/logstash/common-filters.md|103 col 4| [OpenSearch.HeadingCapitalization] 'grok' is a heading and should be in sentence case.
_tools/logstash/common-filters.md|105 col 57| [OpenSearch.Repetition] 'and' is repeated.
_tools/logstash/read-from-opensearch.md|14 col 238| [OpenSearch.Spelling] Error: ingestions. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_tools/logstash/read-from-opensearch.md|21 col 131| [OpenSearch.DirectionAboveBelow] Use 'following example' instead of 'example below' for versions or orientation within a document. Use 'above' and 'below' only for physical space or screen descriptions.
_tools/logstash/execution-model.md|18 col 126| [OpenSearch.Spelling] Error: batchers. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_tools/logstash/ship-to-opensearch.md|81 col 4| [OpenSearch.HeadingCapitalization] 'Adding different Authentication mechanisms in the Output plugin' is a heading and should be in sentence case.
_tools/logstash/ship-to-opensearch.md|83 col 1| [OpenSearch.StackedHeadings] Do not stack headings. Insert an introductory sentence between headings.
_tools/logstash/ship-to-opensearch.md|83 col 14| [OpenSearch.HeadingCapitalization] 'to support different authentication mechanisms' is a heading and should be in sentence case.
_tools/logstash/ship-to-opensearch.md|110 col 28| [Vale.Terms] Use 'OpenSearch' instead of 'Opensearch'.
_tools/logstash/ship-to-opensearch.md|110 col 76| [OpenSearch.Simple] Don't use 'simply' because it's not neutral in tone. If you mean 'only', use 'only' instead.
_tools/logstash/ship-to-opensearch.md|110 col 117| [OpenSearch.DirectionAboveBelow] Use 'following or later' instead of 'below' for versions or orientation within a document. Use 'above' and 'below' only for physical space or screen descriptions.
_tools/logstash/ship-to-opensearch.md|130 col 5| [OpenSearch.HeadingCapitalization] 'Required Parameters' is a heading and should be in sentence case.
_tools/logstash/ship-to-opensearch.md|133 col 14| [OpenSearch.Spelling] Error: Json. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_tools/logstash/ship-to-opensearch.md|133 col 14| [Vale.Terms] Use 'JSON' instead of 'Json'.
_tools/logstash/ship-to-opensearch.md|138 col 80| [OpenSearch.LatinismsElimination] Using 'etc.' is unnecessary. Remove.
_tools/logstash/ship-to-opensearch.md|140 col 83| [OpenSearch.Spelling] Error: https. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_tools/logstash/ship-to-opensearch.md|142 col 5| [OpenSearch.HeadingCapitalization] 'Optional Parameters' is a heading and should be in sentence case.
_tools/logstash/ship-to-opensearch.md|149 col 38| [Vale.Terms] Use 'Logstash' instead of 'logstash'.
_tools/logstash/ship-to-opensearch.md|149 col 92| [Vale.Terms] Use 'OpenSearch' instead of 'Opensearch'.
_tools/logstash/ship-to-opensearch.md|151 col 20| [Vale.Terms] Use 'Boolean' instead of 'boolean'.
_tools/logstash/ship-to-opensearch.md|151 col 120| [OpenSearch.LatinismsSubstitution] Use 'using, through, by accessing, or by choosing' instead of 'via'.
_tools/logstash/ship-to-opensearch.md|151 col 129| [OpenSearch.Spelling] Error: _template. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_tools/logstash/ship-to-opensearch.md|151 col 183| [OpenSearch.LatinismsSubstitution] Use 'using, through, by accessing, or by choosing' instead of 'via'.
_tools/logstash/ship-to-opensearch.md|156 col 110| [OpenSearch.SubstitutionsError] Use 'time-series data' instead of 'time series data'.
_tools/logstash/ship-to-opensearch.md|161 col 47| [Vale.Terms] Use 'Logstash' instead of 'logstash'.
_tools/logstash/ship-to-opensearch.md|161 col 220| [OpenSearch.DirectionAboveBelow] Use 'following or later' instead of 'below' for versions or orientation within a document. Use 'above' and 'below' only for physical space or screen descriptions.
_data-prepper/migrate-open-distro.md|15 col 98| [Vale.Terms] Use 'Elasticsearch' instead of 'ElasticSearch'.
_tools/logstash/advanced-config.md|179 col 12| [OpenSearch.SubstitutionsError] Use 'time zone' instead of 'timezone'.
_tools/cli.md|12 col 44| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_tools/cli.md|14 col 12| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_tools/cli.md|14 col 252| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_tools/cli.md|16 col 96| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_tools/cli.md|78 col 1| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_tools/logstash/index.md|46 col 139| [OpenSearch.Spelling] Error: syslog. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_tools/logstash/index.md|46 col 176| [OpenSearch.Spelling] Error: stdin. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_data-prepper/managing-data-prepper/extensions/geoip_service.md|28 col 4| [OpenSearch.Spelling] Error: maxmind. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_data-prepper/managing-data-prepper/extensions/geoip_service.md|28 col 4| [OpenSearch.HeadingCapitalization] 'maxmind' is a heading and should be in sentence case.
_data-prepper/managing-data-prepper/extensions/geoip_service.md|43 col 21| [OpenSearch.HeadingCapitalization] 'database' is a heading and should be in sentence case.
_data-prepper/managing-data-prepper/extensions/geoip_service.md|47 col 15| [OpenSearch.Spelling] Error: aws. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.