honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #14296 from Dwaligon/master 

Fixing misspelled words in documentation
This commit is contained in:
Clinton Gormley 2015-10-29 20:24:23 +01:00
parent dd2a6310a8 86c21f3c39
commit 16fb84bc34
6 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/reference/analysis/tokenfilters/common-grams-tokenfilter.asciidoc
View File

@ -1,7 +1,7 @@
[[analysis-common-grams-tokenfilter]] [[analysis-common-grams-tokenfilter]]
=== Common Grams Token Filter === Common Grams Token Filter
Token filter that generates bigrams for frequently occuring terms. Token filter that generates bigrams for frequently occurring terms.
Single terms are still indexed. It can be used as an alternative to the Single terms are still indexed. It can be used as an alternative to the
<<analysis-stop-tokenfilter,Stop <<analysis-stop-tokenfilter,Stop
Token Filter>> when we don't want to completely ignore common terms. Token Filter>> when we don't want to completely ignore common terms.

2
docs/reference/index-modules/analysis.asciidoc
View File

@ -7,6 +7,6 @@ which are:
* added to the inverted index in order to make the document searchable * added to the inverted index in order to make the document searchable
* used by high level queries such as the <<query-dsl-match-query,`match` query>> * used by high level queries such as the <<query-dsl-match-query,`match` query>>
to generate seach terms. to generate search terms.
See <<analysis>> for configuration details. See <<analysis>> for configuration details.

2
docs/reference/index-modules/translog.asciidoc
View File

@ -68,7 +68,7 @@ update, or bulk request. This setting accepts the following parameters:
(default) `fsync` and commit after every request. In the event (default) `fsync` and commit after every request. In the event
of hardware failure, all acknowledged writes will already have been of hardware failure, all acknowledged writes will already have been
commited to disk. committed to disk.
`async`:: `async`::

2
docs/reference/migration/migrate_3_0.asciidoc
View File

@ -291,7 +291,7 @@ Also reusing new Operator enum.
Removed `MoreLikeThisQueryBuilder.Item#id(String id)`, `Item#doc(BytesReference doc)`, Removed `MoreLikeThisQueryBuilder.Item#id(String id)`, `Item#doc(BytesReference doc)`,
`Item#doc(XContentBuilder doc)`. Use provided constructors instead. `Item#doc(XContentBuilder doc)`. Use provided constructors instead.
Removed `MoreLikeThisQueryBuilder#addLike` in favor of texts and/or items beeing provided Removed `MoreLikeThisQueryBuilder#addLike` in favor of texts and/or items being provided
at construction time. Using arrays there instead of lists now. at construction time. Using arrays there instead of lists now.
Removed `MoreLikeThisQueryBuilder#addUnlike` in favor to using the `unlike` methods Removed `MoreLikeThisQueryBuilder#addUnlike` in favor to using the `unlike` methods

2
docs/reference/modules/snapshots.asciidoc
View File

@ -142,7 +142,7 @@ This setting supports wildcards in the place of host, path, query, and fragment.
repositories.url.allowed_urls: ["http://www.example.org/root/*", "https://*.mydomain.com/*?*#*"] repositories.url.allowed_urls: ["http://www.example.org/root/*", "https://*.mydomain.com/*?*#*"]
----------------------------------- -----------------------------------
URL repositories with `file:` URLs can only point to locations registered in the `path.repo` setting similiar to URL repositories with `file:` URLs can only point to locations registered in the `path.repo` setting similar to
shared file system repository. shared file system repository.
[float] [float]

2
docs/reference/setup/cluster_restart.asciidoc
View File

@ -64,7 +64,7 @@ upgraded following the same procedure described in <<upgrade-node>>.
If you have dedicated master nodes -- nodes with `node.master` set to If you have dedicated master nodes -- nodes with `node.master` set to
`true`(the default) and `node.data` set to `false` -- then it is a good idea `true`(the default) and `node.data` set to `false` -- then it is a good idea
to start them first. Wait for them to form a cluster and to elect a master to start them first. Wait for them to form a cluster and to elect a master
before proceding with the data nodes. You can check progress by looking at the before proceeding with the data nodes. You can check progress by looking at the
logs. logs.
As soon as the <<master-election,minimum number of master-eligible nodes>> As soon as the <<master-election,minimum number of master-eligible nodes>>