for a few editor's changes that did not get added to previous PR before it was merged

Signed-off-by: alicejw <alicejw@amazon.com>
This commit is contained in:
alicejw 2022-05-17 09:58:41 -07:00
parent 99673dd631
commit 9ec7e253ce
2 changed files with 4 additions and 4 deletions

View File

@ -32,11 +32,11 @@ The following table describes the differences between them.
OpenSearch uses a probabilistic ranking framework called Okapi BM25 to calculate relevance scores. To learn more about Okapi BM25, see [Wikipedia](https://en.wikipedia.org/wiki/Okapi_BM25).
{: .note }
To show the difference between a simple HTTP search versus a search via query DSL, we have an example of each one so that you can see how they differ.
The following examples show the difference between a simple HTTP search and a search with query DSL.
## Example: HTTP simple search
The following request performs a simple search to search for a `speaker` field that has a value of `queen`.
The following request performs a simple search for a `speaker` field that has a value of `queen`.
**Sample request**
```json

View File

@ -216,7 +216,7 @@ The search query “HAMLET” is also searched literally. So, to get a match on
# Term-level query operations
This section provides examples for term-level query operations that you can use for specific search use cases.
This section provides examples of term-level query operations that you can use for specific search use cases.
## Single term
@ -238,7 +238,7 @@ GET shakespeare/_search
## Multiple terms
Use the `terms` operation to search for multiple values for same query field.
Use the `terms` operation to search for multiple value matches for the same query field.
```json
GET shakespeare/_search