Final review and clean-up

Author: ggailey777

articles/azure-functions/migrate-version-1-version-4.md

@@ -3,7 +3,7 @@ title: Migrate apps from Azure Functions version 1.x to 4.x
 description: This article shows you how to upgrade your existing function apps running on version 1.x of the Azure Functions runtime to be able to run on version 4.x of the runtime. 
 ms.service: azure-functions
 ms.topic: how-to 
-ms.date: 10/19/2022
+ms.date: 11/05/2022
 ms.custom: template-how-to-pattern 
 zone_pivot_groups: programming-languages-set-functions
 ---
@@ -365,7 +365,7 @@ To update your project to Azure Functions 4.x:
 
 1. Move to one of the [Node.js versions supported on version 4.x](functions-reference-node.md#node-version).
 
-1. Add both `version` and `extensionBundle` elements to the host.json, so that it looks like the following:
+1. Add both `version` and `extensionBundle` elements to the host.json, so that it looks like the following example:
 
     [!INCLUDE [functions-extension-bundles-json-v3](../../includes/functions-extension-bundles-json-v3.md)]
 
@@ -385,9 +385,9 @@ To update your project to Azure Functions 4.x:
 
     The `AzureWebJobsStorage` setting can be either the Azurite storage emulator or an actual Azure storage account. For more information, see [Local storage emulator](/functions-develop-local.md#local-storage-emulator).
 ::: zone-end  
-
+::: zone pivot="programming-language-javascript,programming-language-csharp"
 [!INCLUDE [functions-migrate-v4](../../includes/functions-migrate-v4.md)]
-
+::: zone-end
 ## Behavior changes after version 1.x
 
 This section details changes made after version 1.x in both trigger and binding behaviors as well as in core Functions features and behaviors.

articles/azure-functions/migrate-version-3-version-4.md

@@ -3,7 +3,7 @@ title: Migrate apps from Azure Functions version 3.x to 4.x
 description: This article shows you how to upgrade your existing function apps running on version 3.x of the Azure Functions runtime to be able to run on version 4.x of the runtime. 
 ms.service: azure-functions
 ms.topic: how-to 
-ms.date: 10/23/2022
+ms.date: 11/05/2022
 zone_pivot_groups: programming-languages-set-functions
 ---
 
@@ -214,7 +214,7 @@ To update your project to Azure Functions 4.x:
 3. If needed, move to one of the [Node.js versions supported on version 4.x](functions-reference-node.md#node-version).
 ::: zone-end  
 ::: zone pivot="programming-language-powershell"  
-3. If needed, upgrade to PowerShell 7.2. For more information, see [PowerShell versions](functions-reference-powershell.md#powershell-versions).
+3. Take this opportunity to upgrade to PowerShell 7.2, which is recommended. For more information, see [PowerShell versions](functions-reference-powershell.md#powershell-versions).
 ::: zone-end  
 ::: zone pivot="programming-language-python"  
 3. If you're using Python 3.6, move to one of the [supported versions](functions-reference-python.md#python-version).
@@ -224,7 +224,7 @@ To update your project to Azure Functions 4.x:
 
 ## Breaking changes between 3.x and 4.x
 
-The following are key breaking changes to be aware of before upgrading a 3.x app to 4.x, including language-specific breaking changes. For a full list, see Azure Functions GitHub issues labeled [*Breaking Change: Approved*](https://github.com/Azure/azure-functions/issues?q=is%3Aissue+label%3A%22Breaking+Change%3A+Approved%22+is%3A%22closed+OR+open%22). More changes are expected during the preview period. Subscribe to [App Service Announcements](https://github.com/Azure/app-service-announcements/issues) for updates.
+The following are key breaking changes to be aware of before upgrading a 3.x app to 4.x, including language-specific breaking changes. For a full list, see Azure Functions GitHub issues labeled [*Breaking Change: Approved*](https://github.com/Azure/azure-functions/issues?q=is%3Aissue+label%3A%22Breaking+Change%3A+Approved%22+is%3A%22closed+OR+open%22). 
 
 If you don't see your programming language, go select it from the [top of the page](#top). 
 
@@ -236,7 +236,7 @@ If you don't see your programming language, go select it from the [top of the pa
 
 - Azure Functions 4.x now enforces [minimum version requirements for extensions](functions-versions.md#minimum-extension-versions). Upgrade to the latest version of affected extensions. For non-.NET languages, [upgrade](./functions-bindings-register.md#extension-bundles) to extension bundle version 2.x or later. ([#1987](https://github.com/Azure/Azure-Functions/issues/1987))
 
-- Default and maximum timeouts are now enforced in 4.x for function app running on Linux in a Consumption plan. ([#1915](https://github.com/Azure/Azure-Functions/issues/1915))
+- Default and maximum timeouts are now enforced in 4.x for function apps running on Linux in a Consumption plan. ([#1915](https://github.com/Azure/Azure-Functions/issues/1915))
 
 - Azure Functions 4.x uses `Azure.Identity` and `Azure.Security.KeyVault.Secrets` for the Key Vault provider and has deprecated the use of Microsoft.Azure.KeyVault. For more information about how to configure function app settings, see the Key Vault option in [Secret Repositories](security-concepts.md#secret-repositories). ([#2048](https://github.com/Azure/Azure-Functions/issues/2048))
 
@@ -272,4 +272,9 @@ If you don't see your programming language, go select it from the [top of the pa
 - Shared memory transfer is enabled by default. ([#1973](https://github.com/Azure/Azure-Functions/issues/1973))
 
 - Default thread count has been updated. Functions that aren't thread-safe or have high memory usage may be impacted. ([#1962](https://github.com/Azure/Azure-Functions/issues/1962))
-::: zone-end
+::: zone-end
+
+## Next steps
+
+> [!div class="nextstepaction"]
+> [Learn more about Functions versions](functions-versions.md)

includes/functions-migrate-v4-linuxfxversion.md

@@ -6,16 +6,16 @@ ms.date: 11/03/2022
 ms.author: glenga
 ---
 ::: zone pivot="programming-language-csharp,programming-language-java,programming-language-javascript,programming-language-typescript,programming-language-python"
-You might also need to update the `linuxFxVersion` site setting to target your specific language language version. If you already have the correct value of `linuxFxVersion` set, you can skip this step. For more information, see [Valid `linuxFxVersion` values](../articles/azure-functions/functions-app-settings.md#valid-linuxfxversion-values).
+You might also need to update the `linuxFxVersion` site setting to target your specific language version. If you already have the correct value of `linuxFxVersion` set, you can skip this step. For more information, see [Valid `linuxFxVersion` values](../articles/azure-functions/functions-app-settings.md#valid-linuxfxversion-values).
 ::: zone-end
 ::: zone pivot="programming-language-powershell"
-PowerShell apps aren't supported on Linux before Functions 4.x. This means you shouldn't need to upgrade a PowerShell function app running on Linux. 
+PowerShell apps aren't supported on Linux before Functions 4.x. This fact means you shouldn't need to upgrade a PowerShell function app running on Linux. 
 ::: zone-end
 ::: zone pivot="programming-language-csharp"
 ```azurecli
 az functionapp config set --name <APP_NAME> --resource-group <RESOURCE_GROUP_NAME> --linux-fx-version "DOTNET|6.0"
 ```
-If you are migrating to .NET Functions isolated worker process, use either `DOTNET-ISOLATED|6.0` or `DOTNET-ISOLATED|7.0` for `--linux-fx-version`. 
+If you're migrating to .NET Functions isolated worker process, use either `DOTNET-ISOLATED|6.0` or `DOTNET-ISOLATED|7.0` for `--linux-fx-version`. 
 :::zone-end
 ::: zone pivot="programming-language-java"
 ```azurecli

includes/functions-migrate-v4.md

@@ -29,7 +29,7 @@ Update-AzFunctionAppSetting -AppSetting @{"FUNCTIONS_EXTENSION_VERSION" = "~4"}
 ```
 ---
 
-During upgrade, you must also set an additional setting, which differs between Windows and Linux.
+During upgrade, you must also set another setting, which differs between Windows and Linux.
 
 # [Windows](#tab/windows/azure-cli)