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

[DOC] Fix format issue and refresh content #5477

Merged
merged 13 commits into from
Nov 2, 2023

Update outdated content and screenshots

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

[DOC] Fix format issue and refresh content #5477

Update outdated content and screenshots
4bd47ac
Select commit
Loading
Failed to load commit list.
GitHub Actions / vale completed Nov 2, 2023 in 1s

reviewdog [vale] report

reported by reviewdog 🐶

Findings (6)

_dashboards/management/multi-data-sources.md|10 col 3| [OpenSearch.HeadingCapitalization] 'Configuring and using multiple data sources' is a heading and should be in sentence case.
_dashboards/management/multi-data-sources.md|22 col 5| [OpenSearch.HeadingCapitalization] 'Step 1: Modify the YAML file settings' is a heading and should be in sentence case.
_dashboards/management/multi-data-sources.md|46 col 18| [OpenSearch.Ampersand] Don't use an ampersand in place of 'and' in documentation.
_dashboards/management/multi-data-sources.md|47 col 11| [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.
_dashboards/management/multi-data-sources.md|63 col 25| [OpenSearch.Ampersand] Don't use an ampersand in place of 'and' in documentation.
_dashboards/management/multi-data-sources.md|65 col 18| [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.

Filtered Findings (3598)

_query-dsl/full-text/match-phrase-prefix.md|148 col 471| [OpenSearch.Spelling] Error: reorderings. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_query-dsl/full-text/match-phrase.md|189 col 56| [OpenSearch.Spelling] Error: reorderings. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_query-dsl/full-text/match-phrase.md|273 col 471| [OpenSearch.Spelling] Error: reorderings. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_query-dsl/geo-and-xy/index.md|14 col 338| [OpenSearch.LinksEndSlash] Add a trailing slash to the link '({{site.url}}{{site.baseurl}}/opensearch/supported-field-types/geographic)'.
_query-dsl/geo-and-xy/index.md|26 col 127| [OpenSearch.LinksEndSlash] Add a trailing slash to the link '({{site.url}}{{site.baseurl}}/opensearch/supported-field-types/geo-point)'.
_query-dsl/geo-and-xy/index.md|26 col 257| [OpenSearch.LinksEndSlash] Add a trailing slash to the link '({{site.url}}{{site.baseurl}}/opensearch/supported-field-types/geo-shape)'.
_query-dsl/geo-and-xy/xy.md|21 col 26| [OpenSearch.TableHeadings] 'Supporting xy Field Type' is a table heading and should be in sentence case.
_query-dsl/full-text/intervals.md|154 col 13| [OpenSearch.TableHeadings] 'Required/Optional' is a table heading and should be in sentence case.
_query-dsl/full-text/intervals.md|161 col 329| [OpenSearch.Spelling] Error: unstemmed. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_query-dsl/full-text/intervals.md|161 col 395| [OpenSearch.Spelling] Error: unstemmed. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_query-dsl/full-text/intervals.md|167 col 13| [OpenSearch.TableHeadings] 'Required/Optional' is a table heading and should be in sentence case.
_query-dsl/full-text/intervals.md|177 col 13| [OpenSearch.TableHeadings] 'Required/Optional' is a table heading and should be in sentence case.
_query-dsl/full-text/intervals.md|190 col 13| [OpenSearch.TableHeadings] 'Required/Optional' is a table heading and should be in sentence case.
_query-dsl/full-text/intervals.md|203 col 13| [OpenSearch.TableHeadings] 'Required/Optional' is a table heading and should be in sentence case.
_query-dsl/full-text/intervals.md|214 col 13| [OpenSearch.TableHeadings] 'Required/Optional' is a table heading and should be in sentence case.
_query-dsl/full-text/intervals.md|223 col 13| [OpenSearch.TableHeadings] 'Required/Optional' is a table heading and should be in sentence case.
_query-dsl/full-text/multi-match.md|915 col 471| [OpenSearch.Spelling] Error: reorderings. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_query-dsl/index.md|18 col 3| [OpenSearch.HeadingCapitalization] 'Query DSL' is a heading and should be in sentence case.
_query-dsl/index.md|54 col 4| [OpenSearch.HeadingCapitalization] 'A note on Unicode special characters in text fields' is a heading and should be in sentence case.
_query-dsl/term-vs-full-text.md|17 col 34| [OpenSearch.Simple] Don't use 'simply' because it's not neutral in tone. If you mean 'only', use 'only' instead.
_query-dsl/term-vs-full-text.md|23 col 4| [OpenSearch.HeadingCapitalization] 'Should I use a full-text or a term-level query?' is a heading and should be in sentence case.
_query-dsl/term-vs-full-text.md|23 col 50| [OpenSearch.HeadingPunctuation] Don't use punctuation at the end of a heading.
_query-dsl/term-vs-full-text.md|82 col 90| [OpenSearch.Simple] Don't use 'just' because it's not neutral in tone. If you mean 'only', use 'only' instead.
_query-dsl/term-vs-full-text.md|149 col 61| [OpenSearch.LinksEndSlash] Add a trailing slash to the link '({{site.url}}{{site.baseurl}}/opensearch/query-dsl/full-text/index)'.
_query-dsl/full-text/query-string.md|142 col 37| [OpenSearch.TableHeadings] 'Query in Discover' is a table heading and should be in sentence case.
_query-dsl/query-filter-context.md|75 col 124| [OpenSearch.LinksEndSlash] Add a trailing slash to the link '({{site.url}}{{site.baseurl}}/opensearch/search/sort)'.
_query-dsl/term/regexp.md|61 col 109| [OpenSearch.Spelling] Error: determinized. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_query-dsl/term/term.md|27 col 143| [OpenSearch.Spelling] Error: lowercasing. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_query-dsl/compound/function-score.md|85 col 288| [OpenSearch.Spelling] Error: irreproducible. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_query-dsl/compound/function-score.md|659 col 26| [Vale.Terms] Use 'Lambda' instead of 'lambda'.
_query-dsl/compound/function-score.md|661 col 10| [Vale.Terms] Use 'Lambda' instead of 'lambda'.
_query-dsl/compound/function-score.md|663 col 4| [Vale.Terms] Use 'Lambda' instead of 'lambda'.
_reporting/index.md|9 col 3| [OpenSearch.HeadingCapitalization] 'Reporting' is a heading and should be in sentence case.
_reporting/rep-cli-index.md|10 col 3| [OpenSearch.HeadingCapitalization] 'Reporting using the CLI' is a heading and should be in sentence case.
_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-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-create.md|23 col 6| [OpenSearch.HeadingCapitalization] 'Example: Requesting a PNG file' is a heading and should be in sentence case.
_reporting/rep-cli-create.md|31 col 6| [OpenSearch.HeadingCapitalization] 'Example: Requesting a PDF file' is a heading and should be in sentence case.
_reporting/rep-cli-create.md|43 col 6| [OpenSearch.HeadingCapitalization] 'Example: Requesting a CSV file' is a heading and should be in sentence case.
_reporting/report-dashboard-index.md|10 col 3| [OpenSearch.HeadingCapitalization] 'Reporting using OpenSearch Dashboards' is a heading and should be in sentence case.
_reporting/rep-cli-env-var.md|11 col 3| [OpenSearch.HeadingCapitalization] 'Use environment variables with the Reporting CLI' is a heading and should be in sentence case.
_reporting/rep-cli-env-var.md|28 col 6| [OpenSearch.HeadingCapitalization] 'Example: Requesting a PNG report with environment variables set' is a heading and should be in sentence case.
_reporting/rep-cli-env-var.md|38 col 4| [OpenSearch.HeadingCapitalization] 'Using Amazon SES to request an email with a report attachment' is a heading and should be in sentence case.
_reporting/rep-cli-env-var.md|71 col 6| [OpenSearch.HeadingCapitalization] 'Example: Sending a report to an email address with SMTP' is a heading and should be in sentence case.
_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-install.md|11 col 3| [OpenSearch.HeadingCapitalization] 'Download and install the Reporting CLI tool' is a heading and should be in sentence case.
_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 4| [OpenSearch.HeadingCapitalization] 'Downloading and installing the Reporting CLI from npm' is a heading and should be in sentence case.
_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-install.md|25 col 4| [OpenSearch.HeadingCapitalization] 'Downloading and installing the Reporting CLI from' is a heading and should be in sentence case.
_reporting/rep-cli-options.md|11 col 3| [OpenSearch.HeadingCapitalization] 'Reporting CLI options' is a heading and should be in sentence case.
_reporting/rep-cli-options.md|24 col 79| [Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.
_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 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 113| [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|11 col 3| [OpenSearch.HeadingCapitalization] 'Scheduling reports with AWS Lambda' is a heading and should be in sentence case.
_reporting/rep-cli-lambda.md|93 col 4| [OpenSearch.HeadingCapitalization] 'Step 2: Create a private repository with Amazon ECR' is a heading and should be in sentence case.
_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.'.
_reporting/rep-cli-lambda.md|144 col 4| [OpenSearch.HeadingCapitalization] 'Step 5: Add the trigger to start the AWS Lambda function' is a heading and should be in sentence case.
_reporting/rep-cli-lambda.md|152 col 4| [OpenSearch.HeadingCapitalization] '(Optional) Step 6: Add the role permission for Amazon SES' is a heading and should be in sentence case.
_field-types/supported-field-types/keyword.md|13 col 3| [OpenSearch.HeadingCapitalization] 'Keyword field type' is a heading and should be in sentence case.
_field-types/supported-field-types/keyword.md|54 col 98| [OpenSearch.SpacingWords] There should be once space between words in 'A value'.
_field-types/supported-field-types/keyword.md|56 col 109| [OpenSearch.SubstitutionsError] Use 'white space' instead of 'whitespace'.
_field-types/supported-field-types/keyword.md|57 col 125| [OpenSearch.Spelling] Error: _source. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/object.md|77 col 228| [OpenSearch.Spelling] Error: _source. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/object.md|150 col 170| [OpenSearch.Spelling] Error: _source. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/xy.md|23 col 1| [OpenSearch.TableHeadings] 'Field Data type' is a table heading and should be in sentence case.
_field-types/supported-field-types/geo-point.md|112 col 158| [OpenSearch.Spelling] Error: _source. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/geo-point.md|113 col 98| [OpenSearch.SpacingWords] There should be once space between words in 'A value'.
_field-types/supported-field-types/search-as-you-type.md|210 col 125| [OpenSearch.Spelling] Error: _source. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/rank.md|12 col 3| [OpenSearch.HeadingCapitalization] 'Rank field types' is a heading and should be in sentence case.
_field-types/supported-field-types/rank.md|24 col 4| [OpenSearch.HeadingCapitalization] 'Rank feature' is a heading and should be in sentence case.
_field-types/supported-field-types/rank.md|85 col 4| [OpenSearch.HeadingCapitalization] 'Rank feature query' is a heading and should be in sentence case.
_field-types/supported-field-types/rank.md|171 col 4| [OpenSearch.HeadingCapitalization] 'Rank features' is a heading and should be in sentence case.
_field-types/supported-field-types/range.md|64 col 4| [OpenSearch.HeadingCapitalization] 'IP address ranges' is a heading and should be in sentence case.
_field-types/supported-field-types/range.md|66 col 146| [OpenSearch.AcronymParentheses] 'CIDR': 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.
_field-types/supported-field-types/range.md|159 col 125| [OpenSearch.Spelling] Error: _source. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/xy-point.md|105 col 158| [OpenSearch.Spelling] Error: _source. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/xy-point.md|106 col 98| [OpenSearch.SpacingWords] There should be once space between words in 'A value'.
_field-types/supported-field-types/token-count.md|13 col 3| [OpenSearch.HeadingCapitalization] 'Token count field type' is a heading and should be in sentence case.
_field-types/supported-field-types/token-count.md|121 col 98| [OpenSearch.SpacingWords] There should be once space between words in 'A value'.
_field-types/supported-field-types/token-count.md|122 col 125| [OpenSearch.Spelling] Error: _source. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/binary.md|54 col 125| [OpenSearch.Spelling] Error: _source. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/alias.md|58 col 4| [OpenSearch.HeadingCapitalization] 'Using aliases in search API operations' is a heading and should be in sentence case.
_field-types/supported-field-types/alias.md|70 col 4| [OpenSearch.HeadingCapitalization] 'Using aliases in field capabilities API operations' is a heading and should be in sentence case.
_field-types/supported-field-types/alias.md|84 col 9| [OpenSearch.Spelling] Error: _source. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/xy-shape.md|15 col 1| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/xy-shape.md|51 col 34| [OpenSearch.TableHeadings] 'WKT type' is a table heading and should be in sentence case.
_field-types/supported-field-types/xy-shape.md|255 col 4| [OpenSearch.HeadingCapitalization] 'Multilinestring' is a heading and should be in sentence case.
_field-types/supported-field-types/xy-shape.md|403 col 158| [OpenSearch.Spelling] Error: _source. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/completion.md|321 col 340| [OpenSearch.SpacingPunctuation] There should be no space before and one space after the punctuation mark in 'match. Default'.
_field-types/supported-field-types/completion.md|345 col 34| [OpenSearch.Spelling] Error: abcde. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/join.md|38 col 1| [OpenSearch.AdverbsOfTime] Don't use a comma after single-word adverbs of time at the beginning of a sentence in 'Then,'.
_field-types/supported-field-types/index.md|49 col 4| [OpenSearch.HeadingCapitalization] 'Multifields' is a heading and should be in sentence case.
_field-types/supported-field-types/index.md|77 col 114| [OpenSearch.AdverbsOfTime] Don't use a comma after single-word adverbs of time at the beginning of a sentence in ' Then,'.
_field-types/supported-field-types/index.md|103 col 28| [OpenSearch.Spelling] Error: testindex. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/nested.md|162 col 1| [OpenSearch.AdverbsOfTime] Don't use a comma after single-word adverbs of time at the beginning of a sentence in 'Then,'.
_field-types/supported-field-types/text.md|15 col 293| [OpenSearch.LatinismsElimination] Using 'etc.' is unnecessary. Remove.
_field-types/supported-field-types/numeric.md|112 col 98| [OpenSearch.SpacingWords] There should be once space between words in 'A value'.
_field-types/supported-field-types/numeric.md|113 col 125| [OpenSearch.Spelling] Error: _source. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/date.md|57 col 125| [OpenSearch.Spelling] Error: _source. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/date.md|69 col 299| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|69 col 328| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|102 col 67| [OpenSearch.Spelling] Error: yyyyMMdd. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/date.md|102 col 111| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|104 col 89| [OpenSearch.Spelling] Error: yyyyMMdd. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/date.md|106 col 160| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|107 col 82| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|109 col 84| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|112 col 107| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|116 col 164| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|122 col 117| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|127 col 203| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|127 col 223| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|127 col 246| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|127 col 273| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|128 col 369| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|128 col 389| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|128 col 412| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|129 col 118| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|129 col 138| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|130 col 156| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|130 col 173| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|131 col 255| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|131 col 292| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|132 col 231| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|133 col 185| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|134 col 136| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|135 col 118| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|136 col 108| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|137 col 128| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|138 col 101| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|139 col 54| [OpenSearch.Spelling] Error: yyyy. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/date.md|141 col 188| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|141 col 220| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|142 col 154| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|149 col 211| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|149 col 244| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|150 col 179| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|152 col 158| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|153 col 193| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|154 col 150| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|156 col 412| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|156 col 447| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/date.md|157 col 398| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/boolean.md|78 col 98| [OpenSearch.SpacingWords] There should be once space between words in 'A value'.
_field-types/supported-field-types/boolean.md|79 col 125| [OpenSearch.Spelling] Error: _source. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/ip.md|12 col 3| [OpenSearch.HeadingCapitalization] 'IP address field type' is a heading and should be in sentence case.
_field-types/supported-field-types/ip.md|14 col 4| [OpenSearch.Spelling] Error: ip. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/ip.md|61 col 4| [OpenSearch.HeadingCapitalization] 'Searching for an IP address and its associated network mask' is a heading and should be in sentence case.
_field-types/supported-field-types/ip.md|109 col 54| [OpenSearch.Spelling] Error: ip. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/ip.md|117 col 98| [OpenSearch.SpacingWords] There should be once space between words in 'A value'.
_field-types/supported-field-types/ip.md|118 col 125| [OpenSearch.Spelling] Error: _source. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/knn-vector.md|10 col 3| [OpenSearch.HeadingCapitalization] 'k-NN vector' is a heading and should be in sentence case.
_field-types/supported-field-types/knn-vector.md|50 col 313| [OpenSearch.Spelling] Error: nmslib. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/knn-vector.md|50 col 342| [OpenSearch.Spelling] Error: hnsw. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/knn-vector.md|50 col 410| [OpenSearch.Spelling] Error: nmslib. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/knn-vector.md|50 col 448| [OpenSearch.Spelling] Error: hnsw. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/knn-vector.md|172 col 160| [OpenSearch.Spelling] Error: quantizing. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/knn-vector.md|174 col 6| [OpenSearch.HeadingCapitalization] 'Scalar quantization for the L2 space type' is a heading and should be in sentence case.
templates/API_TEMPLATE.md|8 col 3| [OpenSearch.HeadingCapitalization] 'Example API' is a heading and should be in sentence case.
templates/API_TEMPLATE.md|14 col 4| [OpenSearch.HeadingCapitalization] 'Path and HTTP methods' is a heading and should be in sentence case.
_field-types/supported-field-types/geo-shape.md|15 col 1| [OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.
_field-types/supported-field-types/geo-shape.md|15 col 140| [OpenSearch.Spelling] Error: tesselates. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/supported-field-types/geo-shape.md|49 col 34| [OpenSearch.TableHeadings] 'WKT type' is a table heading and should be in sentence case.
_field-types/supported-field-types/geo-shape.md|187 col 278| [OpenSearch.SpacingWords] There should be once space between words in 'because WKT'.
_field-types/supported-field-types/geo-shape.md|255 col 4| [OpenSearch.HeadingCapitalization] 'Multilinestring' is a heading and should be in sentence case.
_field-types/supported-field-types/geo-shape.md|403 col 158| [OpenSearch.Spelling] Error: _source. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/index.md|15 col 11| [OpenSearch.Simple] Don't use 'just' because it's not neutral in tone. If you mean 'only', use 'only' instead.
_field-types/index.md|36 col 1| [OpenSearch.Spelling] Error: boolean. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/index.md|36 col 1| [Vale.Terms] Use 'Boolean' instead of 'boolean'.
_field-types/index.md|36 col 52| [Vale.Terms] Use 'Boolean' instead of 'boolean'.
_field-types/index.md|36 col 52| [OpenSearch.Spelling] Error: boolean. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_field-types/index.md|41 col 85| [OpenSearch.Simple] Don't use 'just' because it's not neutral in tone. If you mean 'only', use 'only' instead.
_field-types/index.md|172 col 8| [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.
_security-analytics/usage/detectors.md|8 col 3| [OpenSearch.HeadingCapitalization] 'Working with detectors' is a heading and should be in sentence case.
_security-analytics/usage/detectors.md|26 col 111| [OpenSearch.Spelling] Error: editig. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_security-analytics/usage/findings.md|8 col 3| [OpenSearch.HeadingCapitalization] 'Working with findings' is a heading and should be in sentence case.
_security-analytics/usage/findings.md|17 col 4| [OpenSearch.HeadingCapitalization] 'The Findings graph' is a heading and should be in sentence case.
_security-analytics/usage/findings.md|44 col 4| [OpenSearch.HeadingCapitalization] 'The Findings list' is a heading and should be in sentence case.
_security-analytics/usage/overview.md|8 col 3| [OpenSearch.HeadingCapitalization] 'The Overview page' is a heading and should be in sentence case.
_security-analytics/usage/correlation-graph.md|8 col 3| [OpenSearch.HeadingCapitalization] 'Working with the correlation graph' is a heading and should be in sentence case.
_security-analytics/usage/correlation-graph.md|13 col 4| [OpenSearch.Spelling] Error: Acccessing. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.
_security-analytics/usage/index.md|11 col 3| [OpenSearch.HeadingCapitalization] 'Using Security Analytics' is a heading and should be in sentence case.
_security-analytics/usage/alerts.md|8 col 3| [OpenSearch.HeadingCapitalization] 'Working with alerts' is a heading and should be in sentence case.
_security-analytics/usage/alerts.md|17 col 4| [OpenSearch.HeadingCapitalization] 'The Alerts graph' is a heading and should be in sentence case.
_security-analytics/usage/alerts.md|43 col 4| [OpenSearch.HeadingCapitalization] 'The Alerts list' is a heading and should be in sentence case.
_security-analytics/security.md|8 col 3| [OpenSearch.HeadingCapitalization] 'OpenSearch Security for Security Analytics' is a heading and should be in sentence case.
_security-analytics/security.md|13 col 4| [OpenSearch.HeadingCapitalization] 'Security Analytics system indexes' is a heading and should be in sentence case.
_security-analytics/security.md|27 col 4| [OpenSearch.HeadingCapitalization] '(Advanced) Limit access by backend role' is a heading and should be in sentence case.
_security-analytics/security.md|96 col 305| [OpenSearch.LinksEndSlash] Add a trailing slash to the link '({{site.url}}{{site.baseurl}}/security/access-control/document-level-security)'.
... (Too many findings. Dropped some findings)

Annotations

Check failure on line 10 in _dashboards/management/multi-data-sources.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] _dashboards/management/multi-data-sources.md#L10

[OpenSearch.HeadingCapitalization] 'Configuring and using multiple data sources' is a heading and should be in sentence case.
Raw output
{"message": "[OpenSearch.HeadingCapitalization] 'Configuring and using multiple data sources' is a heading and should be in sentence case.", "location": {"path": "_dashboards/management/multi-data-sources.md", "range": {"start": {"line": 10, "column": 3}}}, "severity": "ERROR"}

Check failure on line 22 in _dashboards/management/multi-data-sources.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] _dashboards/management/multi-data-sources.md#L22

[OpenSearch.HeadingCapitalization] 'Step 1: Modify the YAML file settings' is a heading and should be in sentence case.
Raw output
{"message": "[OpenSearch.HeadingCapitalization] 'Step 1: Modify the YAML file settings' is a heading and should be in sentence case.", "location": {"path": "_dashboards/management/multi-data-sources.md", "range": {"start": {"line": 22, "column": 5}}}, "severity": "ERROR"}

Check warning on line 46 in _dashboards/management/multi-data-sources.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] _dashboards/management/multi-data-sources.md#L46

[OpenSearch.Ampersand] Don't use an ampersand in place of 'and' in documentation.
Raw output
{"message": "[OpenSearch.Ampersand] Don't use an ampersand in place of 'and' in documentation.", "location": {"path": "_dashboards/management/multi-data-sources.md", "range": {"start": {"line": 46, "column": 18}}}, "severity": "WARNING"}

Check warning on line 47 in _dashboards/management/multi-data-sources.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] _dashboards/management/multi-data-sources.md#L47

[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.
Raw output
{"message": "[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.", "location": {"path": "_dashboards/management/multi-data-sources.md", "range": {"start": {"line": 47, "column": 11}}}, "severity": "WARNING"}

Check warning on line 63 in _dashboards/management/multi-data-sources.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] _dashboards/management/multi-data-sources.md#L63

[OpenSearch.Ampersand] Don't use an ampersand in place of 'and' in documentation.
Raw output
{"message": "[OpenSearch.Ampersand] Don't use an ampersand in place of 'and' in documentation.", "location": {"path": "_dashboards/management/multi-data-sources.md", "range": {"start": {"line": 63, "column": 25}}}, "severity": "WARNING"}

Check warning on line 65 in _dashboards/management/multi-data-sources.md

See this annotation in the file changed.

@github-actions github-actions / vale

[vale] _dashboards/management/multi-data-sources.md#L65

[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.
Raw output
{"message": "[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.", "location": {"path": "_dashboards/management/multi-data-sources.md", "range": {"start": {"line": 65, "column": 18}}}, "severity": "WARNING"}