Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Backport 2.12] fix(security): explicitly add keys required in security config #6820

Merged
merged 1 commit into from
Apr 2, 2024

fix(security): explicitly add keys required in security config (#6805)

d478da3
Select commit
Loading
Failed to load commit list.
Sign in for the full log view
Merged

[Backport 2.12] fix(security): explicitly add keys required in security config #6820

fix(security): explicitly add keys required in security config (#6805)
d478da3
Select commit
Loading
Failed to load commit list.
GitHub Actions / vale succeeded Apr 1, 2024 in 1s

reviewdog [vale] report

reported by reviewdog 🐶

Findings (0)
Filtered Findings (2546)

_about/version-history.md|14 col 506| [OpenSearch.Spelling] Error: toolset. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_about/version-history.md|17 col 340| [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.
_about/version-history.md|19 col 134| [Vale.Terms] Use 'Simple Schema for Observability' instead of 'simple schema for observability'.
_about/version-history.md|19 col 428| [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.
_about/version-history.md|21 col 172| [Vale.Terms] Use 'Gradle' instead of 'gradle'.
_about/version-history.md|23 col 595| [OpenSearch.Spelling] Error: maketime. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_about/version-history.md|23 col 608| [OpenSearch.Spelling] Error: makedate. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_about/version-history.md|23 col 617| [OpenSearch.Spelling] Error: datetime. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_about/version-history.md|24 col 134| [Vale.Terms] Use 'Gradle' instead of 'gradle'.
_about/version-history.md|24 col 167| [Vale.Terms] Use 'Gradle' instead of 'gradle'.
_about/version-history.md|25 col 245| [OpenSearch.Spelling] Error: Nmslib. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_about/version-history.md|40 col 172| [Vale.Terms] Use 'Gradle' instead of 'gradle'.
_about/version-history.md|44 col 225| [OpenSearch.Spelling] Error: protostuff. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_about/version-history.md|45 col 483| [OpenSearch.Spelling] Error: backport. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_about/version-history.md|46 col 250| [OpenSearch.Spelling] Error: gson. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_about/version-history.md|47 col 228| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_about/version-history.md|49 col 327| [Vale.Terms] Use 'Anomaly Detection plugin' instead of 'anomaly detection plugin'.
_about/index.md|31 col 22| [OpenSearch.HeadingPunctuation] Don't use punctuation at the end of a heading.
_about/index.md|51 col 69| [OpenSearch.Spelling] Error: underperformance. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_about/index.md|62 col 4| [OpenSearch.SubstitutionsError] Use 'k-NN' instead of 'KNN'.
_about/index.md|64 col 80| [Vale.Terms] Use 'Piped Processing Language' instead of 'piped processing language'.
_about/index.md|66 col 98| [OpenSearch.SubstitutionsError] Use 'machine learning' instead of 'machine-learning'.
_about/index.md|74 col 27| [OpenSearch.HeadingPunctuation] Don't use punctuation at the end of a heading.
_about/index.md|85 col 182| [Vale.Terms] Use 'Elasticsearch' instead of 'ELASTICSEARCH'.
_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.
_about/breaking-changes.md|8 col 4| [OpenSearch.HeadingCapitalization] '1.x' is a heading and should be in sentence case.
_about/breaking-changes.md|10 col 1| [OpenSearch.StackedHeadings] Do not stack headings. Insert an introductory sentence between headings.
_about/breaking-changes.md|19 col 1| [OpenSearch.StackedHeadings] Do not stack headings. Insert an introductory sentence between headings.
_about/breaking-changes.md|27 col 4| [OpenSearch.Inclusive] Use 'allow list' instead of 'Whitelist' because the latter is an offensive term.
_about/breaking-changes.md|28 col 4| [OpenSearch.Inclusive] Use 'deny list' instead of 'Blacklist' because the latter is an offensive term.
_about/breaking-changes.md|29 col 4| [OpenSearch.Inclusive] Use 'cluster manager' instead of 'Master' because the latter is an offensive term.
_about/breaking-changes.md|31 col 5| [OpenSearch.HeadingCapitalization] 'Add OpenSearch Notifications plugins' is a heading and should be in sentence case.
_about/breaking-changes.md|42 col 1| [OpenSearch.StackedHeadings] Do not stack headings. Insert an introductory sentence between headings.
_about/quickstart.md|35 col 155| [Vale.Terms] Use 'Docker' instead of 'docker'.
_about/quickstart.md|43 col 105| [OpenSearch.Simple] Don't use 'just' because it's not neutral in tone. If you mean 'only', use 'only' instead.
_about/quickstart.md|59 col 5| [OpenSearch.SubstitutionsError] Use 'example response' instead of 'Sample response'.
_about/quickstart.md|127 col 36| [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.
_about/quickstart.md|150 col 26| [OpenSearch.HeadingColon] Capitalize the word after a colon in ': docker'.
_about/quickstart.md|150 col 28| [Vale.Terms] Use 'Docker' instead of 'docker'.
_about/quickstart.md|150 col 42| [OpenSearch.HeadingColon] Capitalize the word after a colon in ': command'.
_about/quickstart.md|154 col 21| [Vale.Terms] Use 'Docker' instead of 'docker'.
_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.
_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-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-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.'.
_about/intro.md|23 col 431| [OpenSearch.SubstitutionsError] Use 'for more information about' instead of 'For more information on'.
_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.
_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/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.
_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/index.md|19 col 4| [Vale.Terms] Use 'Performance Analyzer' instead of 'Performance analyzer'.
_benchmark/tutorials/sigv4.md|8 col 3| [OpenSearch.HeadingCapitalization] 'Running OpenSearch Benchmark with AWS Signature Version 4' is a heading and should be in sentence case.
_benchmark/tutorials/sigv4.md|12 col 68| [OpenSearch.AcronymParentheses] 'IAM': 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.
_benchmark/tutorials/sigv4.md|17 col 34| [OpenSearch.AcronymParentheses] 'IAM': 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.
_benchmark/tutorials/sigv4.md|18 col 38| [OpenSearch.AcronymParentheses] 'IAM': 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.
_benchmark/tutorials/sigv4.md|27 col 34| [OpenSearch.AcronymParentheses] 'IAM': 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.
_benchmark/tutorials/sigv4.md|28 col 38| [OpenSearch.AcronymParentheses] 'IAM': 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/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/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.
_benchmark/user-guide/index.md|8 col 3| [OpenSearch.HeadingCapitalization] 'OpenSearch Benchmark User Guide' is a heading and should be in sentence case.
_benchmark/user-guide/contributing-workloads.md|21 col 72| [OpenSearch.Spelling] Error: data's. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/user-guide/contributing-workloads.md|27 col 61| [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.
_benchmark/user-guide/contributing-workloads.md|37 col 23| [Vale.Terms] Use 'JSON' instead of 'json'.
_benchmark/user-guide/creating-custom-workloads.md|86 col 22| [Vale.Terms] Use 'JSON' instead of 'json'.
_benchmark/user-guide/creating-custom-workloads.md|118 col 55| [OpenSearch.Spelling] Error: Zemeckis. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/user-guide/creating-custom-workloads.md|119 col 119| [OpenSearch.SpacingWords] There should be once space between words in 'out of'.
_benchmark/user-guide/creating-custom-workloads.md|120 col 54| [OpenSearch.Spelling] Error: Wes. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/user-guide/creating-custom-workloads.md|257 col 1| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_benchmark/user-guide/creating-custom-workloads.md|265 col 1| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_benchmark/user-guide/creating-custom-workloads.md|291 col 1| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_benchmark/user-guide/creating-custom-workloads.md|373 col 220| [Vale.Terms] Use 'JSON' instead of 'json'.
_benchmark/user-guide/creating-custom-workloads.md|390 col 78| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_benchmark/user-guide/configuring-benchmark.md|34 col 119| [OpenSearch.Spelling] Error: asyncio. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/user-guide/configuring-benchmark.md|35 col 74| [OpenSearch.Spelling] Error: asyncio. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/user-guide/configuring-benchmark.md|102 col 4| [OpenSearch.Spelling] Error: datastore. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/user-guide/configuring-benchmark.md|205 col 79| [Vale.Terms] Use 'JSON' instead of 'json'.
_benchmark/user-guide/understanding-workloads/choosing-a-workload.md|11 col 6| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_benchmark/user-guide/understanding-workloads/choosing-a-workload.md|13 col 49| [OpenSearch.Spelling] Error: rideshare. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/user-guide/understanding-workloads/choosing-a-workload.md|13 col 73| [OpenSearch.Spelling] Error: rideshare. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/user-guide/understanding-workloads/choosing-a-workload.md|13 col 182| [OpenSearch.Spelling] Error: rideshare. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/user-guide/understanding-workloads/choosing-a-workload.md|21 col 83| [Vale.Terms] Use 'JSON' instead of 'json'.
_benchmark/user-guide/understanding-workloads/choosing-a-workload.md|25 col 111| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_benchmark/user-guide/concepts.md|37 col 313| [OpenSearch.LatinismsSubstitution] Use 'compared to or compared with' instead of 'versus'.
_benchmark/user-guide/concepts.md|43 col 305| [OpenSearch.Spelling] Error: occured. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/user-guide/concepts.md|64 col 103| [OpenSearch.UnitsSpacing] Put a space between the number and the units in '200ms '.
_benchmark/user-guide/concepts.md|71 col 34| [OpenSearch.UnitsSpacing] Put a space between the number and the units in '200ms,'.
_benchmark/user-guide/concepts.md|71 col 70| [OpenSearch.UnitsSpacing] Put a space between the number and the units in '1110ms '.
_benchmark/user-guide/concepts.md|71 col 88| [OpenSearch.UnitsSpacing] Put a space between the number and the units in '400ms,'.
_benchmark/user-guide/concepts.md|71 col 171| [OpenSearch.UnitsSpacing] Put a space between the number and the units in '00s '.
_benchmark/user-guide/concepts.md|71 col 213| [OpenSearch.UnitsSpacing] Put a space between the number and the units in '10s.'.
_benchmark/user-guide/concepts.md|71 col 254| [OpenSearch.UnitsSpacing] Put a space between the number and the units in '10s '.
_benchmark/user-guide/concepts.md|75 col 122| [OpenSearch.UnitsSpacing] Put a space between the number and the units in '200ms,'.
_benchmark/user-guide/concepts.md|77 col 27| [OpenSearch.UnitsSpacing] Put a space between the number and the units in '1100ms.'.
_benchmark/user-guide/concepts.md|78 col 1| [OpenSearch.UnitsSpacing] Put a space between the number and the units in '300ms.'.
_benchmark/user-guide/concepts.md|78 col 7| [OpenSearch.Spelling] Error: subsquent. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/user-guide/concepts.md|78 col 57| [OpenSearch.UnitsSpacing] Put a space between the number and the units in '00s.'.
_benchmark/user-guide/concepts.md|78 col 90| [OpenSearch.UnitsSpacing] Put a space between the number and the units in '100ms,'.
_benchmark/user-guide/concepts.md|78 col 177| [OpenSearch.UnitsSpacing] Put a space between the number and the units in '200ms.'.
_benchmark/user-guide/concepts.md|84 col 60| [OpenSearch.UnitsSpacing] Put a space between the number and the units in '200ms '.
_benchmark/user-guide/concepts.md|93 col 60| [OpenSearch.UnitsSpacing] Put a space between the number and the units in '200ms,'.
_benchmark/user-guide/concepts.md|109 col 38| [OpenSearch.Spelling] Error: asin. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/user-guide/concepts.md|109 col 55| [OpenSearch.UnitsSpacing] Put a space between the number and the units in '100ms '.
_benchmark/reference/workloads/indices.md|14 col 6| [OpenSearch.SubstitutionsError] Use 'indexes' instead of 'indices'.
_benchmark/user-guide/distributed-load.md|24 col 10| [OpenSearch.DashSpacing] There should be no spaces around the dash in '1 -- Coordinator'.
_benchmark/user-guide/distributed-load.md|25 col 10| [OpenSearch.DashSpacing] There should be no spaces around the dash in '2 -- Worker'.
_benchmark/user-guide/distributed-load.md|26 col 10| [OpenSearch.DashSpacing] There should be no spaces around the dash in '3 -- Worker'.
_benchmark/reference/workloads/index.md|14 col 51| [OpenSearch.SubstitutionsError] Use 'indexes' instead of 'indices'.
_benchmark/reference/workloads/index.md|19 col 81| [OpenSearch.LinksDoubleParentheses] Remove double parentheses from the link '](({{site.url}}{{site.baseurl}}/benchmark/understanding-workloads/anatomy-of-a-workload/)'.
_benchmark/reference/workloads/index.md|26 col 13| [OpenSearch.Spelling] Error: unthrottled. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/reference/workloads/index.md|28 col 56| [OpenSearch.Spelling] Error: unthrottled. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/reference/workloads/index.md|111 col 74| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_benchmark/quickstart.md|15 col 123| [OpenSearch.LinksDoubleSlash] Remove double slashes from the link '({{site.url}}{{site.baseurl}}//tuning-your-cluster/index/)'.
_benchmark/quickstart.md|265 col 63| [OpenSearch.SpacingPunctuation] There should be no space before and one space after the punctuation mark in 'endpoint. This'.
_benchmark/quickstart.md|267 col 100| [OpenSearch.SpacingPunctuation] There should be no space before and one space after the punctuation mark in 'cluster. This'.
_benchmark/reference/index.md|8 col 3| [OpenSearch.HeadingCapitalization] 'OpenSearch Benchmark Reference' is a heading and should be in sentence case.
_benchmark/user-guide/understanding-workloads/anatomy-of-a-workload.md|17 col 5| [OpenSearch.Spelling] Error: _operations. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/user-guide/understanding-workloads/anatomy-of-a-workload.md|87 col 4| [OpenSearch.SubstitutionsError] Use 'indexes' instead of 'indices'.
_benchmark/user-guide/understanding-workloads/anatomy-of-a-workload.md|92 col 5| [OpenSearch.SubstitutionsError] Use 'indexes' instead of 'Indices'.
_benchmark/user-guide/understanding-workloads/anatomy-of-a-workload.md|94 col 188| [OpenSearch.SubstitutionsError] Use 'indexes' instead of 'Indices'.
_benchmark/user-guide/understanding-workloads/anatomy-of-a-workload.md|271 col 5| [OpenSearch.HeadingCapitalization] '_operations and _test-procedures' is a heading and should be in sentence case.
_benchmark/user-guide/understanding-workloads/anatomy-of-a-workload.md|271 col 5| [OpenSearch.Spelling] Error: _operations. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/user-guide/installing-benchmark.md|21 col 143| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_benchmark/user-guide/installing-benchmark.md|27 col 3| [OpenSearch.Spelling] Error: eventdata. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/user-guide/installing-benchmark.md|28 col 3| [OpenSearch.Spelling] Error: geonames. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/user-guide/installing-benchmark.md|34 col 3| [OpenSearch.Spelling] Error: noaa. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/user-guide/installing-benchmark.md|37 col 3| [OpenSearch.Spelling] Error: pmc. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/user-guide/installing-benchmark.md|56 col 6| [OpenSearch.Spelling] Error: pyenv. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/user-guide/installing-benchmark.md|145 col 212| [OpenSearch.Spelling] Error: geonames. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/reference/metrics/metric-keys.md|20 col 85| [Vale.Terms] Use 'macOS' instead of 'MacOS'.
CODE_OF_CONDUCT.md|1 col 4| [OpenSearch.HeadingCapitalization] 'Code of Conduct' is a heading and should be in sentence case.
_benchmark/reference/telemetry.md|41 col 118| [OpenSearch.Spelling] Error: GCViewer. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/reference/telemetry.md|60 col 7| [OpenSearch.Spelling] Error: gc. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/reference/telemetry.md|62 col 6| [OpenSearch.Spelling] Error: cgroup. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/reference/telemetry.md|78 col 23| [OpenSearch.Spelling] Error: cgroup. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/reference/workloads/operations.md|252 col 74| [OpenSearch.Spelling] Error: Alwasys. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_benchmark/reference/workloads/operations.md|334 col 106| [OpenSearch.Spelling] Error: gte. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
.github/ISSUE_TEMPLATE/issue_template.md|19 col 99| [OpenSearch.LatinismsElimination] Using 'etc.' 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.
_integrations/index.md|12 col 3| [OpenSearch.HeadingCapitalization] 'OpenSearch Integrations' is a heading and should be in sentence case.
_integrations/index.md|21 col 4| [OpenSearch.HeadingCapitalization] 'Setting up OpenSearch Integrations' is a heading and should be in sentence case.
.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.
_benchmark/reference/commands/command-flags.md|22 col 66| [Vale.Terms] Use 'JSON' instead of 'json'.
.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|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|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.
... (Too many findings. Dropped some findings)