Merge pull request #108067 from timsander1/master

adding BETWEEN keyword udpate

Author: PRMerger9

articles/cosmos-db/sql-query-keywords.md

@@ -4,24 +4,25 @@ description: Learn about SQL keywords for Azure Cosmos DB.
 author: markjbrown
 ms.service: cosmos-db
 ms.topic: conceptual
-ms.date: 06/20/2019
+ms.date: 03/17/2020
 ms.author: mjbrown
 
 ---
 # Keywords in Azure Cosmos DB
+
 This article details keywords which may be used in Azure Cosmos DB SQL queries.
 
 ## BETWEEN
 
-As in ANSI SQL, you can use the BETWEEN keyword to express queries against ranges of string or numerical values. For example, the following query returns all items in which the first child's grade is 1-5, inclusive.
+You can use the `BETWEEN` keyword to express queries against ranges of string or numerical values. For example, the following query returns all items in which the first child's grade is 1-5, inclusive.
 
 ```sql
     SELECT *
     FROM Families.children[0] c
     WHERE c.grade BETWEEN 1 AND 5
 ```
 
-Unlike in ANSI SQL, you can also use the BETWEEN clause in the FROM clause, as in the following example.
+You can also use the `BETWEEN` keyword in the `SELECT` clause, as in the following example.
 
 ```sql
     SELECT (c.grade BETWEEN 0 AND 10)
@@ -31,11 +32,11 @@ Unlike in ANSI SQL, you can also use the BETWEEN clause in the FROM clause, as i
 In SQL API, unlike ANSI SQL, you can express range queries against properties of mixed types. For example, `grade` might be a number like `5` in some items and a string  like `grade4` in others. In these cases, as in JavaScript, the comparison between the two different types results in `Undefined`, so the item is skipped.
 
 > [!TIP]
-> For faster query execution times, create an indexing policy that uses a range index type against any numeric properties or paths that the BETWEEN clause filters.
+> For faster query execution times, create an indexing policy that uses a range index type against any numeric properties or paths that the `BETWEEN` clause filters.
 
 ## DISTINCT
 
-The DISTINCT keyword eliminates duplicates in the query's projection.
+The `DISTINCT` keyword eliminates duplicates in the query's projection.
 
 In this example, the query projects values for each last name:
 
@@ -97,7 +98,7 @@ The results are:
 ]
 ```
 
-Queries with an aggregate system function and a subquery with DISTINCT are not supported. For example, the following query is not supported:
+Queries with an aggregate system function and a subquery with `DISTINCT` are not supported. For example, the following query is not supported:
 
 ```sql
 SELECT COUNT(1) FROM (SELECT DISTINCT f.lastName FROM f)
@@ -127,7 +128,7 @@ If you include your partition key in the `IN` filter, your query will automatica
 
 ## TOP
 
-The TOP keyword returns the first `N` number of query results in an undefined order. As a best practice, use TOP with the ORDER BY clause to limit results to the first `N` number of ordered values. Combining these two clauses is the only way to predictably indicate which rows TOP affects.
+The TOP keyword returns the first `N` number of query results in an undefined order. As a best practice, use TOP with the `ORDER BY` clause to limit results to the first `N` number of ordered values. Combining these two clauses is the only way to predictably indicate which rows TOP affects.
 
 You can use TOP with a constant value, as in the following example, or with a variable value using parameterized queries.