fix few typos

Author: timsander1

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

@@ -4,17 +4,17 @@ description: Learn about the SQL syntax, and example for FROM clause for Azure C
 author: timsander1
 ms.service: cosmos-db
 ms.topic: conceptual
-ms.date: 12/02/2019
+ms.date: -5/08/2020
 ms.author: tisande
 
 ---
 # FROM clause in Azure Cosmos DB
 
 The FROM (`FROM <from_specification>`) clause is optional, unless the source is filtered or projected later in the query. A query like `SELECT * FROM Families` enumerates over the entire `Families` container. You can also use the special identifier ROOT for the container instead of using the container name.
 
-The FROM clause enforces the following rules per query:
+The `FROM` clause enforces the following rules per query:
 
-* The container can be aliased, such as `SELECT f.id FROM Families AS f` or simply `SELECT f.id FROM Families f`. Here `f` is the alias for `Families`. AS is an optional keyword to [alias](sql-query-aliasing.md) the identifier.  
+* The container can be aliased, such as `SELECT f.id FROM Families AS f` or simply `SELECT f.id FROM Families f`. Here `f` is the alias for `Families`. AS is an optional keyword to [alias](sql-query-working-with-json.md#aliasing) the identifier.  
 
 * Once aliased, the original source name cannot be bound. For example, `SELECT Families.id FROM Families f` is syntactically invalid because the identifier `Families` has been aliased and can't be resolved anymore.  
 
@@ -25,15 +25,15 @@ The FROM clause enforces the following rules per query:
 ```sql  
 FROM <from_specification>  
 
-<from_specification> ::=   
+<from_specification> ::=
         <from_source> {[ JOIN <from_source>][,...n]}  
 
-<from_source> ::=   
+<from_source> ::=
           <container_expression> [[AS] input_alias]  
         | input_alias IN <container_expression>  
 
-<container_expression> ::=   
-        ROOT   
+<container_expression> ::=
+        ROOT
      | container_name  
      | input_alias  
      | <container_expression> '.' property_name  
@@ -46,9 +46,9 @@ FROM <from_specification>
 
   Specifies a data source, with or without an alias. If alias is not specified, it will be inferred from the `<container_expression>` using following rules:  
 
-  -  If the expression is a container_name, then container_name will be used as an alias.  
+-  If the expression is a container_name, then container_name will be used as an alias.  
 
-  -  If the expression is `<container_expression>`, then property_name, then property_name will be used as an alias. If the expression is a container_name, then container_name will be used as an alias.  
+-  If the expression is `<container_expression>`, then property_name, then property_name will be used as an alias. If the expression is a container_name, then container_name will be used as an alias.  
 
 - AS `input_alias`  
 
@@ -94,9 +94,9 @@ If a container expression accesses properties or array elements and that value d
 
 A container expression may be container-scoped or document-scoped:  
 
--   An expression is container-scoped, if the underlying source of the container expression is either ROOT or `container_name`. Such an expression represents a set of documents retrieved from the container directly, and is not dependent on the processing of other container expressions.  
+- An expression is container-scoped, if the underlying source of the container expression is either ROOT or `container_name`. Such an expression represents a set of documents retrieved from the container directly, and is not dependent on the processing of other container expressions.  
 
--   An expression is document-scoped, if the underlying source of the container expression is `input_alias` introduced earlier in the query. Such an expression represents a set of documents obtained by evaluating the container expression in the scope of each document belonging to the set associated with the aliased container.  The resulting set will be a union of sets obtained by evaluating the container expression for each of the documents in the underlying set. 
+- An expression is document-scoped, if the underlying source of the container expression is `input_alias` introduced earlier in the query. Such an expression represents a set of documents obtained by evaluating the container expression in the scope of each document belonging to the set associated with the aliased container. The resulting set will be a union of sets obtained by evaluating the container expression for each of the documents in the underlying set.
 
 ## Examples
 
@@ -142,7 +142,7 @@ The results are:
     ]
 ```
 
-The preceding query used an array as the source, but you can also use an object as the source. The query considers any valid, defined JSON value in the source for inclusion in the result. The following example would exclude `Families` that don’t have an `address.state` value.
+The preceding query used an array as the source, but you can also use an object as the source. The query considers any valid, defined JSON value in the source for inclusion in the result. The following example would exclude `Families` that don't have an `address.state` value.
 
 ```sql
     SELECT *

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

@@ -10,7 +10,7 @@ ms.author: tisande
 
 # SELECT clause in Azure Cosmos DB
 
-Every query consists of a SELECT clause and optional [FROM](sql-query-from.md) and [WHERE](sql-query-where.md) clauses, per ANSI SQL standards. Typically, the source in the FROM clause is enumerated, and the WHERE clause applies a filter on the source to retrieve a subset of JSON items. The SELECT clause then projects the requested JSON values in the select list.
+Every query consists of a `SELECT` clause and optional [FROM](sql-query-from.md) and [WHERE](sql-query-where.md) clauses, per ANSI SQL standards. Typically, the source in the `FROM` clause is enumerated, and the `WHERE` clause applies a filter on the source to retrieve a subset of JSON items. The `SELECT` clause then projects the requested JSON values in the select list.
 
 ## Syntax
 
@@ -24,7 +24,6 @@ SELECT <select_specification>
 
 <object_property_list> ::=
 { <scalar_expression> [ [ AS ] property_alias ] } [ ,...n ]  
-  
 ```  
 
 ## Arguments

articles/cosmos-db/sql-query-working-with-json.md

@@ -8,14 +8,17 @@ ms.date: 05/08/2020
 ms.author: tisande
 ---
 
+# Working with JSON in Azure Cosmos DB
+
 In Azure Cosmos DB's SQL (Core) API, items are stored as JSON. The type system and expressions are restricted to deal only with JSON types. For more information, see the [JSON specification](https://www.json.org/).
 
 We'll summarize some important aspects of working with JSON.
-    - JSON objects always begin with a `{` left brace and end with a `}` right brace
-    - You can have JSON properties [nested](#nested-properties) within one another
-    - JSON properties can have arrays values
-    - JSON properties are case sensitive
-    - JSON properties can have any string value (including spaces or characters that aren't letters)
+
+- JSON objects always begin with a `{` left brace and end with a `}` right brace
+- You can have JSON properties [nested](#nested-properties) within one another
+- JSON properties can have arrays values
+- JSON properties are case sensitive
+- JSON properties can have any string value (including spaces or characters that aren't letters)
 
 ## Nested properties
 
@@ -39,7 +42,7 @@ Here's a document with nested JSON:
 
 In this case, the `state`, `country`, and `city` properties are all nested within the `address` property.
 
-The following example projects two nested properties, `f.address.state` and `f.address.city`.
+The following example projects two nested properties: `f.address.state` and `f.address.city`.
 
 ```sql
     SELECT f.address.state, f.address.city
@@ -90,7 +93,7 @@ FROM Families f
 WHERE f.children[0].givenName = "Jesse"
 ```
 
-In most cases however, you'll use a [subquery](sql-query-subquery.md) or [self-join](sql-query-join.md) when working with arrays.
+In most cases, however, you'll use a [subquery](sql-query-subquery.md) or [self-join](sql-query-join.md) when working with arrays.
 
 For example, here's a document that shows the bank account balance of a customer over each month during 2020.
 
@@ -119,7 +122,7 @@ For example, here's a document that shows the bank account balance of a customer
 }
 ```
 
-If you wanted to run a query that showed all the customers that had a negative balance at some point during 2020, it would use [EXISTS](sql-query-subquery.md#exists-expression) with a subquery and look like this:
+If you wanted to run a query that showed all the customers that had a negative balance at some point during 2020, it would use [EXISTS](sql-query-subquery.md#exists-expression) with a subquery:
 
 ```sql
 SELECT c.id
@@ -133,7 +136,7 @@ WHERE EXISTS(
 
 ## Reserved keywords and special characters in JSON
 
-You can access properties using the quoted property operator []. For example, `SELECT c.grade` and `SELECT c["grade"]` are equivalent. This syntax is useful to escape a property that contains spaces, special characters, or has the same name as a SQL keyword or reserved word.
+You can access properties using the quoted property operator `[]`. For example, `SELECT c.grade` and `SELECT c["grade"]` are equivalent. This syntax is useful to escape a property that contains spaces, special characters, or has the same name as a SQL keyword or reserved word.
 
 For example, here's a document with a property named `order` and a property `price($)` that contains special characters:
 
@@ -229,7 +232,7 @@ You can explicitly alias values in queries. If a query has two properties with t
 
 ### Examples
 
-The AS keyword used for aliasing is optional, as shown in the following example when projecting the second value as `NameInfo`:
+The `AS` keyword used for aliasing is optional, as shown in the following example when projecting the second value as `NameInfo`:
 
 ```sql
     SELECT
@@ -253,7 +256,7 @@ The results are:
     }]
 ```
 
-You can't use alias to project a value as a property name with a space, special character, or reserved word. If you wanted to change a value's projection to, for example, have a property name with a space, you could use a [JSON expression](#json-expressions).
+You can't use aliasing to project a value as a property name with a space, special character, or reserved word. If you wanted to change a value's projection to, for example, have a property name with a space, you could use a [JSON expression](#json-expressions).
 
 Here's an example:
 
@@ -268,5 +271,5 @@ Here's an example:
 ## Next steps
 
 - [Getting started](sql-query-getting-started.md)
-- [Azure Cosmos DB .NET samples](https://github.com/Azure/azure-cosmos-dotnet-v3)
+- [SELECT clause](sql-query-select.md)
 - [WHERE clause](sql-query-where.md)