Merge pull request #106711 from burkeholland/burke-cosmos-quickstart

Final updates to quickstart

Author: ShannonLeavitt

articles/cosmos-db/create-sql-api-nodejs.md

@@ -12,12 +12,12 @@ ms.author: dech
 # Quickstart: Use Node.js to connect and query data from Azure Cosmos DB SQL API account
 
 > [!div class="op_single_selector"]
-> * [.NET V3](create-sql-api-dotnet.md)
-> * [.NET V4](create-sql-api-dotnet-V4.md)
-> * [Java](create-sql-api-java.md)
-> * [Node.js](create-sql-api-nodejs.md)
-> * [Python](create-sql-api-python.md)
-> * [Xamarin](create-sql-api-xamarin-dotnet.md)
+> - [.NET V3](create-sql-api-dotnet.md)
+> - [.NET V4](create-sql-api-dotnet-V4.md)
+> - [Java](create-sql-api-java.md)
+> - [Node.js](create-sql-api-nodejs.md)
+> - [Python](create-sql-api-python.md)
+> - [Xamarin](create-sql-api-xamarin-dotnet.md)
 
 In this quickstart, you create and manage an Azure Cosmos DB SQL API account from the Azure portal, and by using a Node.js app cloned from GitHub. Azure Cosmos DB is a multi-model database service that lets you quickly create and query document, table, key-value, and graph databases with global distribution and horizontal scale capabilities.
 
@@ -33,34 +33,34 @@ For this quickstart purpose, you can use the [try Azure Cosmos DB for free](http
 
 1. Navigate to the [try Azure Cosmos DB for free](https://azure.microsoft.com/try/cosmosdb/) page.
 
-1. Choose the **SQL** API account and select **Create**. Sign-in using your Microsoft account such as outlook.
+1. Choose the **SQL** API account and select **Create**. Sign-in using your Microsoft account.
 
 1. After the sign-in is successful, your Azure Cosmos account should be ready. Select **Open in the Azure portal** to open the newly created account.
 
 The "try Azure Cosmos DB for free" option doesn't require an Azure subscription and it offers you an Azure Cosmos account for a limited period of 30 days. If you want to use the Azure Cosmos account for a longer period, you should instead [create the account](create-cosmosdb-resources-portal.md#create-an-azure-cosmos-db-account) within your Azure subscription.
 
 ## Add a container
 
-You can now use the Data Explorer tool in the Azure portal to create a database and container. 
+You can now use the Data Explorer tool in the Azure portal to create a database and container.
 
-1. Select **Data Explorer** > **New Container**. 
-    
-    The **Add Container** area is displayed on the far right, you may need to scroll right to see it.
+1. Select **Data Explorer** > **New Container**.
 
-    ![The Azure portal Data Explorer, Add Container pane](./media/create-sql-api-nodejs/azure-cosmosdb-data-explorer.png)
+   The **Add Container** area is displayed on the far right, you may need to scroll right to see it.
+
+   ![The Azure portal Data Explorer, Add Container pane](./media/create-sql-api-nodejs/azure-cosmosdb-data-explorer.png)
 
 2. In the **Add container** page, enter the settings for the new container.
 
-    |Setting|Suggested value|Description
-    |---|---|---|
-    |**Database ID**|Tasks|Enter *Tasks* as the name for the new database. Database names must contain from 1 through 255 characters, and they cannot contain `/, \\, #, ?`, or a trailing space. Check the **Provision database throughput** option, it allows you to share the throughput provisioned to the database across all the containers within the database. This option also helps with cost savings. |
-    |**Throughput**|400|Leave the throughput at 400 request units per second (RU/s). If you want to reduce latency, you can scale up the throughput later.| 
-    |**Container ID**|Items|Enter *Items* as the name for your new container. Container IDs have the same character requirements as database names.|
-    |**Partition key**| /category| The sample described in this article uses */category* as the partition key.|
-    
-    In addition to the preceding settings, you can optionally add **Unique keys** for the container. Let's leave the field empty in this example. Unique keys provide developers with the ability to add a layer of data integrity to the database. By creating a unique key policy while creating a container, you ensure the uniqueness of one or more values per partition key. To learn more, refer to the [Unique keys in Azure Cosmos DB](unique-keys.md) article.
-    
-    Select **OK**. The Data Explorer displays the new database and container.
+   | Setting           | Suggested value | Description                                                                                                                                                                                                                                                                                                                                                                           |
+   | ----------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+   | **Database ID**   | Tasks           | Enter _Tasks_ as the name for the new database. Database names must contain from 1 through 255 characters, and they cannot contain `/, \\, #, ?`, or a trailing space. Check the **Provision database throughput** option, it allows you to share the throughput provisioned to the database across all the containers within the database. This option also helps with cost savings. |
+   | **Throughput**    | 400             | Leave the throughput at 400 request units per second (RU/s). If you want to reduce latency, you can scale up the throughput later.                                                                                                                                                                                                                                                    |
+   | **Container ID**  | Items           | Enter _Items_ as the name for your new container. Container IDs have the same character requirements as database names.                                                                                                                                                                                                                                                               |
+   | **Partition key** | /category       | The sample described in this article uses _/category_ as the partition key.                                                                                                                                                                                                                                                                                                           |
+
+   In addition to the preceding settings, you can optionally add **Unique keys** for the container. Let's leave the field empty in this example. Unique keys provide developers with the ability to add a layer of data integrity to the database. By creating a unique key policy while creating a container, you ensure the uniqueness of one or more values per partition key. To learn more, refer to the [Unique keys in Azure Cosmos DB](unique-keys.md) article.
+
+   Select **OK**. The Data Explorer displays the new database and container.
 
 ## Add sample data
 
@@ -86,9 +86,21 @@ This step is optional. If you're interested in learning how the Azure Cosmos dat
 
 If you're familiar with the previous version of the SQL JavaScript SDK, you may be used to seeing the terms _collection_ and _document_. Because Azure Cosmos DB supports [multiple API models](introduction.md), [version 2.0+ of the JavaScript SDK](https://www.npmjs.com/package/@azure/cosmos) uses the generic terms _container_, which may be a collection, graph, or table, and _item_ to describe the content of the container.
 
+The Cosmos DB JavaScript SDK is called "@azure/cosmos" and can be installed from npm...
+
+```bash
+npm install @azure/cosmos
+```
+
 The following snippets are all taken from the _app.js_ file.
 
-- The `CosmosClient` object is initialized.
+- The `CosmosClient` is imported from the `@azure/cosmos` npm package.
+
+  ```javascript
+  const CosmosClient = require("@azure/cosmos").CosmosClient;
+  ```
+
+- A new `CosmosClient` object is initialized.
 
   ```javascript
   const client = new CosmosClient({ endpoint, key });
@@ -117,8 +129,6 @@ The following snippets are all taken from the _app.js_ file.
   const { resources: results } = await container.items
     .query(querySpec)
     .fetchAll();
-
-  return results;
   ```
 
 - Create a new item
@@ -136,8 +146,6 @@ The following snippets are all taken from the _app.js_ file.
   const { resource: itemToUpdate } = await container
     .item(id, category)
     .replace(itemToUpdate);
-
-  return result;
   ```
 
 - Delete an item
@@ -169,11 +177,13 @@ Now go back to the Azure portal to get the connection string details of your Azu
 
 ## Run the app
 
-1. Run `npm install` in a terminal to install required npm modules
+1. Run `npm install` in a terminal to install the "@azure/cosmos" npm package
 
 2. Run `node app.js` in a terminal to start your node application.
 
-You can now go back to Data Explorer, modify, and work with this new data.
+3. The two items that you created earlier in this quickstart are listed out. A new item is created. The "isComplete" flag on that item is updated to "true" and then finally, the item is deleted.
+
+You can continue to experiment with this sample application or go back to Data Explorer, modify, and work with your data.
 
 ## Review SLAs in the Azure portal
 
@@ -184,4 +194,4 @@ You can now go back to Data Explorer, modify, and work with this new data.
 In this quickstart, you've learned how to create an Azure Cosmos DB account, create a container using the Data Explorer, and run a Node.js app. You can now import additional data to your Azure Cosmos DB account.
 
 > [!div class="nextstepaction"]
-> [Import data into Azure Cosmos DB](import-data.md)
+> [import data into azure cosmos db](import-data.md)

includes/cosmos-db-create-sql-api-query-data.md

@@ -11,7 +11,7 @@
 ---
 You can use queries in Data Explorer to retrieve and filter your data.
 
-1. At the top of the **Documents** tab in Data Explorer, review the default query `SELECT * FROM c`. This query retrieves and displays all documents in the collection in ID order. 
+1. At the top of the **Items** tab in Data Explorer, review the default query `SELECT * FROM c`. This query retrieves and displays all documents in the collection in ID order. 
 
    ![Default query in Data Explorer is `SELECT * FROM c`](./media/cosmos-db-create-sql-api-query-data/azure-cosmosdb-data-explorer-query.png)