final tweaks

Author: ggailey777

articles/azure-functions/create-first-function-azd-cli.md

@@ -15,7 +15,7 @@ The project source uses the Azure Developer CLI (azd) to simplify deploying your
 
 [!INCLUDE [functions-flex-preview-note](../../includes/functions-flex-preview-note.md)]
 
-By default, the Flex Consumption plan follows a _pay for what you use_ billing model, which means completing this quickstart incurs a small cost of a few USD cents or less in your Azure account.
+By default, the Flex Consumption plan follows a _pay-for-what-you-use_ billing model, which means to complete this quickstart incurs a small cost of a few USD cents or less in your Azure account.
 
 ## Prerequisites
 
@@ -155,9 +155,10 @@ You can use the `azd init` command to create a local Azure Functions code projec
 
 3. Run this command in the root folder:
 
-    ```bash
+    ```console
     func init --worker-runtime python 
     ```
+
     This command restores the _local.settings.json_ file in the root folder, which is required when running locally.
 
 ## Create and activate a virtual environment
@@ -217,7 +218,7 @@ py -m venv .venv
 
 1. From your HTTP test tool in a new terminal, send an HTTP POST request with a JSON payload like in this example:
 
-    :::code language="http" source="~/functions-quickstart-dotnet-azd/http/test.http" range="5-11" :::
+    :::code language="http" source="~/functions-quickstart-dotnet-azd/http/test.http" range="9-15" :::
 
     You can find examples of both HTTP requests in the _test.http_ project file. 
 
@@ -286,7 +287,7 @@ After you verify your functions locally, it's time to publish them to Azure.
 This project is configured to use the `azd up` command to deploy this project to a new function app in a Flex Consumption plan in Azure.
 
 >[!TIP]
->This project includes a set of Bicep files that `azd` uses to create a best practices secure deployment to a Flex consumption plan.
+>This project includes a set of Bicep files that `azd` uses to create a secure deployment to a Flex consumption plan that follows best practices.
 
 1. Run this command to create the Azure resources and deploy your app to Azure.
 
@@ -298,8 +299,10 @@ This project is configured to use the `azd up` command to deploy this project to
 
 1. When prompted, provide these required deployment parameters:
 
-    + _Azure subscription_: Subscription in which your resources are created. 
-    + _Azure location_: Azure region in which to create the resource group that contains the new Azure resources. Only regions that currently support the Flex Consumption plan are shown.
+    | Parameter | Description |
+    | ---- | ---- |
+    | _Azure subscription_ | Subscription in which your resources are created.|
+    | _Azure location_ | Azure region in which to create the resource group that contains the new Azure resources. Only regions that currently support the Flex Consumption plan are shown.|
     
     The `azd up` command uses your response to these prompts with the Bicep configuration files to complete these deployment tasks:
 
@@ -333,9 +336,12 @@ You can use the Core Tools to obtain the URL endpoints of your functions running
 
 ## Redeploy your code
 
-Your responses to `azd` prompts and other environment variables generated by `azd` are stored in your named environment. This means that you can run the `azd up` command as many times as you need to both reprovision your function app and deploy updates to your source code. During subsequent executions, existing resources are skipped. Deployed code files are always overwritten by the latest deployment package. 
+You can run the `azd up` command as many times as you need to both provision your Azure resources and deploy code updates to your function app. 
+
+>[!NOTE]
+>Deployed code files are always overwritten by the latest deployment package.
 
-Use the `azd env get-values` command to review all of the variables in your environment that were used when creating Azure resources. 
+Your initial responses to `azd` prompts and any environment variables generated by `azd` are stored locally in your named environment. Use the `azd env get-values` command to review all of the variables in your environment that were used when creating Azure resources. 
 
 ## Clean up resources
 

includes/functions-quickstart-azd-env.md

@@ -8,4 +8,4 @@ ms.author: glenga
 
 2. Enter an environment name when prompted, such as `flexquickstart`. In `azd`, the environment is used to maintain a unique deployment context for your app, and you can define more than one. It's also used in the name of the resource group you create in Azure. 
 
-    After you specify the environment, `azd` clones the template files to your machine and initializes a local project in your current folder.
+    After you specify the environment, `azd` downloads project files from the template and initializes a local project in your current folder.