Line edits2

Author: lootle1

learn-pr/azure/chain-azure-functions-data-using-bindings/includes/3-explore-input-and-output-binding-types-portal-lab.md

@@ -28,7 +28,7 @@ Let's create a function app that we can use throughout this module. A function a
 
 1. On the resource menu or from the **Home** page, select **Create a resource**. The **Create a resource** pane appears.
 
-1. In the **Create a resource** menu, select **Compute**, and in the results list select **Function App**. You might need to search for **Function App** in the *Search services and marketplace* window.
+1. In the **Create a resource** menu, select **Web**, and in the results list select **Function App**. You might need to search for **Function App** in the *Search services and marketplace* window.
 
 1. Select **Consumption**, then select the **Select** button. The **Create Function App** pane appears.
 
@@ -207,7 +207,7 @@ Now that we have a function app, let's create a function. Each function has a tr
 
 1. In the command bar, select **Get Function Url**. The **Get Function Url** dialog box appears.
 
-1. Select **default (function key)** from the dropdown list, then select the *Copy to clipboard* icon at the end of the URL, and then select **OK** to close the dialog box.
+1. On the **default (function key)** select the *Copy to clipboard* icon at the end of the URL, and then select **Close** to close the dialog box.
 
 1. In the address bar of a new browser tab, paste the function URL you copied. Press <kbd>Enter</kbd> to run the request in your browser. The response might take a couple of minutes as the function app initializes. If you receive a timeout error, refresh to resend the request.
 

learn-pr/azure/chain-azure-functions-data-using-bindings/includes/5-read-data-with-input-bindings-portal-lab.md

@@ -11,7 +11,7 @@ You need to store the data somewhere. In the previous flowchart, the data store
 ## Create an Azure Cosmos DB account
 
 > [!NOTE]
-> This exercise is not intended to be a tutorial on Azure Cosmos DB. If you're interested in learning more, see the complete learning path about Azure Cosmos DB at the end of this module.
+> This exercise isn't intended to be a tutorial on Azure Cosmos DB. If you're interested in learning more, see the complete learning path about Azure Cosmos DB at the end of this module.
 
 ### Create a database account
 
@@ -28,6 +28,7 @@ A database account is a container for managing one or more databases. Before we
     | Setting | Value | Description |
     |---|---|---|
     | **Project Details** |
+    | Workload Type | Development/Testing | Ensures optimal performance and cost efficiency.
     | Subscription | Concierge Subscription | The Azure subscription that works with the resources in the sandbox. |
     | Resource Group | From the drop-down list, select <rgn>[sandbox resource group name]</rgn> | The resource group for your sandbox. |
     | **Instance Details** |
@@ -61,7 +62,7 @@ Let's use the Data Explorer tool to create a database and container.
     | Setting | Value | Description |
     |---|---|---|
     | Database id | Select **Create new**, and enter *func-io-learn-db* for the Database id | Database names can be 1 to 255 characters long, and can't contain `/, \\, #, ?`, or a trailing space.<br>You can enter whatever you want, but we're using *func-io-learn-db* in this module. |
-    | Database Max RU/s | 4000 |Accept the default throughput of 4000 request units per second (RU/s). To reduce latency, you can scale up the performance later. |
+    | Database Max RU/s | Manual |Adjust to Manual and accept the default of 400 request units per second (RU/s). To reduce latency, you can scale up the performance later. |
     | Container id | *Bookmarks* | Container IDs have the same character requirements as database names. We're using *Bookmarks* in this module.|
     | Partition key | /id  | The partition key specifies how the documents in Azure Cosmos DB collections are distributed across logical data partitions. We use the *Partition key* setting as a convenience here because we're not concerned with database performance in this module. To learn more about Azure Cosmos DB partition key strategies, explore the Microsoft Learn Azure Cosmos DB modules. |
 
@@ -71,7 +72,7 @@ Let's use the Data Explorer tool to create a database and container.
 
     When complete, the Data Explorer displays **func-io-learn-db** in **DATA** under **NOSQL API**.
 
-1. Select **func-io-learn-db** to expand it. Notice that your **func-io-learn-db** database contains several child members, including Scale and Bookmarks.
+1. Select **func-io-learn-db** to expand it. Notice that your **func-io-learn-db** database contains child members, including Bookmarks.
 
 1. Expand the **Bookmarks** container. Notice that several child members already prepopulate it.
 
@@ -162,7 +163,7 @@ You can verify our progress so far by testing the new function.
 
 1. In the command bar, select **Get Function Url**. The **Get Function Url** dialog box appears.
 
-1. Select **default (function key)** from the drop-down list, then select the *Copy to clipboard* icon, and select **OK**.
+1. On the **default (function key)**, select the *Copy to clipboard* icon, and select **Close**.
 
 1. Paste the function URL you copied into the address bar of a new browser tab. Append the query string value `&name=<your name>` to the end of the URL, replacing `<your  name>` with your name, and then press <kbd>Enter</kbd>. The Azure function should return a personalized response in the browser.
 
@@ -199,7 +200,7 @@ To read data from the database, you need to define an input binding. As you see
     | **Partition key** | `/id` | Add the partition key that you defined when you created the _Bookmarks_ Azure Cosmos DB collection. The key entered here (specified in input binding format `<key>`) must match the one in the collection. |
     | **SQL Query (optional)** | _Leave blank_ | You're only retrieving one document at a time based on the ID. So, filtering with the Document ID setting is better than using a SQL Query in this instance. You could craft a SQL Query to return one entry (`SELECT * from b where b.ID = id`). That query would indeed return a document, but it would return it in a document collection. Your code would have to manipulate a collection unnecessarily. Use the SQL Query approach when you want to get multiple documents. |
 
-    To clarify why we're using these settings, we want to look up a bookmark with a specific ID, so we tied the **Document ID** that our function receives in the query string to the input binding. This syntax is known as a *binding expression*. The function is triggered by an HTTP request that uses a query string to specify the ID to look up. Because IDs are unique in our collection, the binding returns either 0 (not found) or 1 (found) documents.
+    To clarify why we're using these settings, we want to look up a bookmark with a specific ID, so we tied the **Document ID** that our function receives in the query string to the input binding. This syntax is known as a *binding expression*. An HTTP request triggers the function that uses a query string to specify the ID to look up. Because IDs are unique in our collection, the binding returns either 0 (not found) or 1 (found) documents.
 
 1. To save this input binding configuration, select **Add**.
 
@@ -388,7 +389,7 @@ Let's examine what this code is doing.
 
 1. In the command bar, select **Get function URL**. The **Get function URL** dialog box appears.
 
-1. From the **Key** drop-down list, select **default** under **Function key**, and then select the *Copy to clipboard* icon at the end of the URL.
+1. On the **default (function key)**, select the *Copy to clipboard* icon.
 
 1. Paste the function key you copied into the address bar of a new browser tab, and then add the query string value `&id=docs` to the end of the URL. The resulting URL should resemble the following example:
 
@@ -404,6 +405,6 @@ Let's examine what this code is doing.
 
 1. Replace `&id=docs` with `&id=missing`, press <kbd>Enter</kbd>, and observe the response. We defined five bookmarks and created a meaningful error response if the requested bookmark doesn't exist.
 
-In this unit, you created your first input binding manually to read from an Azure Cosmos DB database. The amount of code you wrote to search our database and read data was minimal, thanks to bindings. You did most of your work configuring the binding declaratively, and the platform took care of the rest.
+In this unit, you created your first input binding manually to read from an Azure Cosmos DB database. The amount of code you wrote to search our database and read data was minimal because of bindings. You did most of your work configuring the binding declaratively, and the platform took care of the rest.
 
 In the next unit, you'll add more data to our bookmarks collection through an Azure Cosmos DB output binding.

learn-pr/azure/chain-azure-functions-data-using-bindings/includes/7-write-data-with-output-bindings-portal-lab.md

@@ -138,7 +138,7 @@ Let's break down what this code does:
 * Posting a message to our queue is as simple as setting the `context.bindings.newmessage` parameter.
 
 > [!NOTE]
-> The only task you performed was to create a queue binding. You never created the queue explicitly. You are witnessing the power of bindings! As the following notification declares, the queue is automatically created for you if it doesn't exist.
+> The only task you performed was to create a queue binding. You never created the queue explicitly. You're witnessing the power of bindings! As the following notification declares, the queue is automatically created for you if it doesn't exist.
 >
 > :::image type="content" source="../media/7-q-auto-create-small.png" alt-text="Screenshot showing message that the queue will be auto-created.":::.
 >
@@ -209,7 +209,7 @@ So, that's it. Let's see our work in action in the next section.
 
 1. To open the **run.ps1** file in the code editor, select your **HttpTrigger3** function from the breadcrumb at the top of the pane.
 
-1. In the Function menu, under **Developer**, select **Code + Test**. The **Code + Test** pane for your **HttpTrigger3** function appears, displaying the default content of **run.ps1**.
+1. In the Function menu, select **Code + Test**. The **Code + Test** pane for your **HttpTrigger3** function appears, displaying the default content of **run.ps1**.
 
 1. Replace the content in the file with the following code.
 
@@ -250,7 +250,7 @@ Let's break down what this code does:
 * Posting a message to our queue is as simple as calling `Push-OutputBinding` with the name of the queue output binding (`newmessage`) and the value of the `$newBookmark` object.
 
 > [!NOTE]
-> The only task you performed was to create a queue binding. You never created the queue explicitly. You are witnessing the power of bindings! As the following notification declares, the queue is automatically created for you if it doesn't exist.
+> The only task you performed was to create a queue binding. You never created the queue explicitly. You're witnessing the power of bindings! As the following notification declares, the queue is automatically created for you if it doesn't exist.
 >
 > :::image type="content" source="../media/7-q-auto-create-small.png" alt-text="Screenshot showing UI tool tip that the queue will be auto-created." border="false":::