[OpenSearch.Spelling] Error: Ubi. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.

[OpenSearch.Spelling] Error: Ubi. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.

[OpenSearch.LinksEndSlash] Add a trailing slash to the link '({{site.url}}{{site.baseurl}}/search-plugins/ubi/schemas)'.

[OpenSearch.HeadingCapitalization] 'Persist a Client-Side Event into a UBI store' is a heading and should be in sentence case.

[OpenSearch.HeadingCapitalization] 'Example Queries' is a heading and should be in sentence case.

[Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.

[Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.

[OpenSearch.TableHeadings] 'query' is a table heading and should be in sentence case.

[OpenSearch.TableHeadings] 'timestamp' is a table heading and should be in sentence case.

[OpenSearch.Spelling] Error: Blanditiis. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.

[OpenSearch.Spelling] Error: sint. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.

[OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.

[OpenSearch.TableHeadings] 'EventTotal' is a table heading and should be in sentence case.

[OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.

[OpenSearch.Range] Use an en dash (--) with no space on either side in a range of numbers.

[Vale.Terms] Use 'OpenSearch' instead of 'opensearch'.

[OpenSearch.Exclamation] Don't use exclamation points in documentation.

[OpenSearch.HeadingCapitalization] '4) Add a "Tag Cloud" vizualization to your dashboard' is a heading and should be in sentence case.

[OpenSearch.Spelling] Error: javascript. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.

[Vale.Terms] Use 'JavaScript' instead of 'javascript'.

[OpenSearch.Spelling] Error: javascript. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.

[Vale.Terms] Use 'JavaScript' instead of 'javascript'.

[OpenSearch.Spelling] Error: th. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.

[OpenSearch.Exclamation] Don't use exclamation points in documentation.

[OpenSearch.HeadingPunctuation] Don't use punctuation at the end of a heading.

[OpenSearch.Spelling] Error: Katas. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.

[OpenSearch.HeadingCapitalization] 'Sample Client data structures' is a heading and should be in sentence case.

[OpenSearch.LinksEndSlash] Add a trailing slash to the link '({{site.url}}{{site.baseurl}}/search-plugins/ubi/schemas)'.

[OpenSearch.Spelling] Error: onClick. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.

[Vale.Terms] Use 'JSON' instead of 'json'.

[OpenSearch.Spelling] Error: unix. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.

[OpenSearch.SpacingPunctuation] There should be no space before and one space after the punctuation mark in 'automatically. The'.

[OpenSearch.SpacingPunctuation] There should be no space before and one space after the punctuation mark in 's. This'.

[OpenSearch.HeadingCapitalization] '2) UBI Events' is a heading and should be in sentence case.

[Vale.Terms] Use 'Amazon' instead of 'amazon'.

[OpenSearch.SpacingPunctuation] There should be no space before and one space after the punctuation mark in 'event. For'.

[Vale.Terms] Use 'JavaScript' instead of 'javascript'.

[OpenSearch.Spelling] Error: javascript. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.

[OpenSearch.SpacingPunctuation] There should be no space before and one space after the punctuation mark in 'formalized. A'.

[OpenSearch.SpacingPunctuation] There should be no space before and one space after the punctuation mark in 'query. Either'.

[OpenSearch.Spelling] Error: unix. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.

[OpenSearch.SpacingPunctuation] There should be no space before and one space after the punctuation mark in 'entry. For'.

[OpenSearch.SpacingPunctuation] There should be no space before and one space after the punctuation mark in 'x,y'.

[OpenSearch.Spelling] Error: th. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.

[OpenSearch.Spelling] Error: th. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.

[OpenSearch.SubstitutionsError] Use 'indexes' instead of 'indices'.

[OpenSearch.Spelling] Error: amd. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.

[OpenSearch.Spelling] Error: ssn. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.

[OpenSearch.Spelling] Error: isbn. If you are referencing a setting, variable, format, function, or repository, surround it with tic marks.

[OpenSearch.Please] Using 'Please' is unnecessary. Remove.

[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.

[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.

[OpenSearch.LatinismsElimination] Using 'etc.' is unnecessary. Remove.

[OpenSearch.Simple] Don't use 'just' because it's not neutral in tone. If you mean 'only', use 'only' instead.

[OpenSearch.LatinismsElimination] Using 'etc.' is unnecessary. Remove.

[OpenSearch.Simple] Don't use 'just' because it's not neutral in tone. If you mean 'only', use 'only' instead.

[OpenSearch.AcronymParentheses] 'UBI': 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.

[OpenSearch.AcronymParentheses] 'UBI': 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.

[OpenSearch.AcronymParentheses] 'UBI': 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.

[OpenSearch.AcronymParentheses] 'UBI': 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.

[OpenSearch.AcronymParentheses] 'UBI': 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.

[OpenSearch.LatinismsElimination] Using 'etc.' is unnecessary. Remove.

[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.

[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.

[OpenSearch.LatinismsSubstitution] Use 'using, through, by accessing, or by choosing' instead of 'via'.

[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.

[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.

[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.

[OpenSearch.LatinismsElimination] Using 'etc.' is unnecessary. Remove.