Merge pull request #187234 from MicrosoftDocs/repo_sync_working_branch

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

Author: huypub

articles/azure-functions/functions-identity-based-connections-tutorial.md

@@ -10,7 +10,7 @@ ms.date: 10/20/2021
 
 # Tutorial: Create a function app that connects to Azure services using identities instead of secrets
 
-This tutorial shows you how to configure a function app using Azure Active Directory identities instead of secrets or connection strings, where possible. Using identities helps you avoid accidentally leaking sensitive secrets and can provide better visibility into how data is accessed. To learn more about identity-based connections, see [configure an identity-based connection.](functions-reference.md#configure-an-identity-based-connection).
+This tutorial shows you how to configure a function app using Azure Active Directory identities instead of secrets or connection strings, where possible. Using identities helps you avoid accidentally leaking sensitive secrets and can provide better visibility into how data is accessed. To learn more about identity-based connections, see [configure an identity-based connection](functions-reference.md#configure-an-identity-based-connection).
 
 While the procedures shown work generally for all languages, this tutorial currently supports C# class library functions on Windows specifically. 
 
@@ -106,7 +106,7 @@ In order to use Azure Key Vault, your app will need to have an identity that can
 
 1. Select **Save**. It might take a minute or two for the role to show up when you refresh the role assignments list for the identity.
 
-The identity will now be able to read secrets stored in the vault. Later in the tutorial, you will add additional role assignments for different purposes.
+The identity will now be able to read secrets stored in the key vault. Later in the tutorial, you will add additional role assignments for different purposes.
 
 ### Generate a template for creating a function app
 
@@ -304,7 +304,7 @@ Next you will update your function app to use its system-assigned identity when
     | Option      | Suggested value  | Description |
     | ------------ | ---------------- | ----------- |
     | **Name** |  AzureWebJobsStorage__accountName | Update the name from **AzureWebJobsStorage** to the exact name `AzureWebJobsStorage__accountName`. This setting tells the host to use the identity instead of looking for a stored secret. The new setting uses a double underscore (`__`), which is a special character in application settings.  |
-    | **Value** | Your account name | Update the name from the connection string to just your **AccountName**. |
+    | **Value** | Your account name | Update the name from the connection string to just your **StorageAccountName**. |
 
     This configuration will let the system know that it should use an identity to connect to the resource.
 

articles/azure-functions/functions-infrastructure-as-code.md

@@ -296,7 +296,7 @@ On Linux, the function app must have its `kind` set to `functionapp,linux`, and
 }
 ```
 
-The [`WEBSITE_CONTENTAZUREFILECONNECTIONSTRING`](functions-app-settings.md#website_contentazurefileconnectionstring) and [`WEBSITE_CONTENTSHARE`](functions-app-settings.md#website_contentshare) settings aren't supported on Linux.
+The [`WEBSITE_CONTENTAZUREFILECONNECTIONSTRING`](functions-app-settings.md#website_contentazurefileconnectionstring) and [`WEBSITE_CONTENTSHARE`](functions-app-settings.md#website_contentshare) settings aren't supported on a Linux Consumption plan.
 
 <a name="premium"></a>
 ## Deploy on Premium plan

articles/azure-functions/functions-openapi-definition.md

@@ -36,7 +36,7 @@ To create an API Management instance linked to your function app:
 
     ![Create new API Management service](media/functions-openapi-definitions/new-apim-service-openapi.png)
 
-1. Choose **Create** to create the API Management instance, which may take several minutes.
+1. Choose **Export** to create the API Management instance, which may take several minutes.
 
 1. After Azure creates the instance, it enables the **Enable Application Insights** option on the page. Select it to send logs to the same place as the function application.
 

articles/azure-functions/functions-run-local.md

@@ -215,7 +215,7 @@ The following considerations apply to project initialization:
 
 + When you don't provide a project name, the current folder is initialized. 
 
-+ If you plan to publish your project to a custom Linux container, use the `--dockerfile` option to make sure that a Dockerfile is generated for your project. To learn more, see [Create a function on Linux using a custom image](functions-create-function-linux-custom-image.md). 
++ If you plan to publish your project to a custom Linux container, use the `--docker` option to make sure that a Dockerfile is generated for your project. To learn more, see [Create a function on Linux using a custom image](functions-create-function-linux-custom-image.md). 
 
 Certain languages may have additional considerations:
 

articles/azure-functions/media/functions-openapi-definitions/new-apim-service-openapi.png

@@ -188,7 +188,7 @@ For more information about the function of the different certificates on an IoT
 For these two automatically generated certificates, you have the option of setting a flag in the config file to configure the number of days for the lifetime of the certificates.
 
 >[!NOTE]
->There is a third auto-generated certificate that the IoT Edge security manager creates, the **IoT Edge hub server certificate**. This certificate always has a 90 day lifetime, but is automatically renewed before expiring. The auto-generated CA lifetime value set in the config file doesn't affect this certificate.
+>There is a third auto-generated certificate that the IoT Edge security manager creates, the **IoT Edge hub server certificate**. This certificate always has a 30 day lifetime, but is automatically renewed before expiring. The auto-generated CA lifetime value set in the config file doesn't affect this certificate.
 
 Upon expiry after the specified number of days, IoT Edge has to be restarted to regenerate the device CA certificate. The device CA certificate won't be renewed automatically.