Merge pull request #99939 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/Microsoft/azure-docs (branch master)

Author: huypub

articles/azure-functions/durable/durable-functions-event-publishing.md

@@ -81,7 +81,7 @@ Add `eventGridTopicEndpoint` and `eventGridKeySettingName` in a `durableTask` pr
 
 The possible Azure Event Grid configuration properties can be found in the [host.json documentation](../functions-host-json.md#durabletask). After you configure the `host.json` file, your function app sends lifecycle events to the event grid topic. This works when you run your function app both locally and in Azure.```
 
-Set the app setting for the topic key in the Function App and `local.setting.json`. The following JSON is a sample of the `local.settings.json` for local debugging. Replace `<topic_key>` with the topic key.  
+Set the app setting for the topic key in the Function App and `local.settings.json`. The following JSON is a sample of the `local.settings.json` for local debugging. Replace `<topic_key>` with the topic key.  
 
 ```json
 {
@@ -280,4 +280,4 @@ To test locally, use [ngrok](../functions-bindings-event-grid.md#local-testing-w
 > [Learn instance management in Durable Functions](durable-functions-instance-management.md)
 
 > [!div class="nextstepaction"]
-> [Learn versioning in Durable Functions](durable-functions-versioning.md)
+> [Learn versioning in Durable Functions](durable-functions-versioning.md)

articles/azure-functions/functions-consumption-costs.md

@@ -8,7 +8,7 @@ ms.topic: conceptual
 
 # Estimating Consumption plan costs
 
-There are currently three types of hosting plans for an app that run in Azure Functions, with each plan having its own pricing model: 
+There are currently three types of hosting plans for an app that runs in Azure Functions, with each plan having its own pricing model: 
 
 | Plan | Description |
 | ---- | ----------- |
@@ -81,11 +81,11 @@ Use [Azure Monitor metrics explorer](../azure-monitor/platform/metrics-getting-s
 
 1. Select **Apply** to choose your function app as the resource to monitor.
 
-1. From **Metric**, choose **Function execution count** and **Sum** for **Aggregation**. This adds the sum of the execution counts during chosen period to the chart.
+1. From **Metric**, choose **Function Execution Count** and **Sum** for **Aggregation**. This adds the sum of the execution counts during chosen period to the chart.
 
     ![Define a functions app metric to add to the chart](media/functions-consumption-costing/monitor-metrics-add-metric.png)
 
-1. Select **Add metric** and repeat steps 2-4 to add **Function execution units** to the chart. 
+1. Select **Add metric** and repeat steps 2-4 to add **Function Execution Units** to the chart. 
 
 The resulting chart contains the totals for both execution metrics in the chosen time range, which in this case is two hours.
 
@@ -184,7 +184,7 @@ This command returns a JSON payload that looks like the following example:
   ]
 }
 ```
-This particular response shows that from `2019-09-11T21:46` to `2019-09-11T23:18`, during which the app consumed 1110000000 MB-milliseconds (1083.98 GB-seconds).
+This particular response shows that from `2019-09-11T21:46` to `2019-09-11T23:18`, the app consumed 1110000000 MB-milliseconds (1083.98 GB-seconds).
 
 ## Determine memory usage
 

articles/azure-functions/functions-develop-vs-code.md

@@ -140,7 +140,7 @@ Following are example prompts to define a new storage output binding:
 | **Select binding with direction** | `Azure Queue Storage` | The binding is an Azure Storage queue binding. |
 | **The name used to identify this binding in your code** | `msg` | Name that identifies the binding parameter referenced in your code. |
 | **The queue to which the message will be sent** | `outqueue` | The name of the queue that the binding writes to. When the *queueName* doesn't exist, the binding creates it on first use. |
-| **Select setting from "local.setting.json"** | `MyStorageConnection` | The name of an application setting that contains the connection string for the storage account. The `AzureWebJobsStorage` setting contains the connection string for the storage account you created with the function app. |
+| **Select setting from "local.settings.json"** | `MyStorageConnection` | The name of an application setting that contains the connection string for the storage account. The `AzureWebJobsStorage` setting contains the connection string for the storage account you created with the function app. |
 
 In this example, the following binding is added to the `bindings` array in your function.json file:
 

articles/azure-functions/ip-addresses.md

@@ -76,15 +76,15 @@ For example, this is what the Western Europe JSON fragment might look like:
 
  For information about when this file is updated and when the IP addresses change, expand the **Details** section of the [Download Center page](https://www.microsoft.com/en-us/download/details.aspx?id=56519).
 
-## Inbound IP address changes
+## <a name="inbound-ip-address-changes"></a>Inbound IP address changes
 
 The inbound IP address **might** change when you:
 
 - Delete a function app and recreate it in a different resource group.
 - Delete the last function app in a resource group and region combination, and re-create it.
-- Delete an SSL binding, such as during [certificate renewal](../app-service/configure-ssl-certificate.md#renew-certificate)).
+- Delete an SSL binding, such as during [certificate renewal](../app-service/configure-ssl-certificate.md#renew-certificate).
 
-When your function app runs in a [Consumption plan](functions-scale.md#consumption-plan), the inbound IP address might also change when you haven't taken any actions such as the ones listed.
+When your function app runs in a [Consumption plan](functions-scale.md#consumption-plan), the inbound IP address might also change even when you haven't taken any actions such as the ones [listed above](#inbound-ip-address-changes).
 
 ## Outbound IP address changes
 
@@ -93,7 +93,7 @@ The set of available outbound IP addresses for a function app might change when
 * Take any action that can change the inbound IP address.
 * Change your App Service plan pricing tier. The list of all possible outbound IP addresses your app can use, for all pricing tiers, is in the `possibleOutboundIPAddresses` property. See [Find outbound IPs](#find-outbound-ip-addresses).
 
-When your function app runs in a [Consumption plan](functions-scale.md#consumption-plan), the outbound IP address might also change when you haven't taken any actions such as the ones listed.
+When your function app runs in a [Consumption plan](functions-scale.md#consumption-plan), the outbound IP address might also change even when you haven't taken any actions such as the ones [listed above](#inbound-ip-address-changes).
 
 To deliberately force an outbound IP address change: