Apply suggestions from code review

Co-authored-by: lilyjma <[email protected]>

Author: AnatoliB

articles/azure-functions/durable/durable-functions-instance-management.md

@@ -776,7 +776,7 @@ Resume-DurableOrchestration -InstanceId $InstanceId -Reason $ResumeReason
 ```
 
 > [!NOTE]
-> This feature is available in the standalone [Durable Functions PowerShell SDK](https://www.powershellgallery.com/packages/AzureFunctions.PowerShell.Durable.SDK) only. If you are not using it yet, see the [migration guide](durable-functions-powershell-v2-sdk-migration-guide.md) for usage instructions.
+> This feature is available in the standalone [Durable Functions PowerShell SDK](https://www.powershellgallery.com/packages/AzureFunctions.PowerShell.Durable.SDK) only. See the difference between the standalone SDK and the legacy built-in SDK along with [migration guide](durable-functions-powershell-v2-sdk-migration-guide.md).
 
 # [Java](#tab/java)
 

articles/azure-functions/durable/durable-functions-packages.md

@@ -55,7 +55,7 @@ Users of [Extension Bundles](../extension-bundles.md) (the recommended Azure Fun
 * PowerShell: The [AzureFunctions.PowerShell.Durable.SDK](https://www.powershellgallery.com/packages/AzureFunctions.PowerShell.Durable.SDK) module.
 
 > [!NOTE]
-> For PowerShell users: the standalone [AzureFunctions.PowerShell.Durable.SDK](https://www.powershellgallery.com/packages/AzureFunctions.PowerShell.Durable.SDK) module is now generally available (GA) and is the recommended approach. See the [migration guide](./durable-functions-powershell-v2-sdk-migration-guide.md) for details. The legacy SDK is also built into the Azure Functions PowerShell language worker for backward compatibility. However, the legacy SDK may not receive new features or bug fixes, and it may be eventually removed from the worker.
+> For PowerShell users: the standalone [AzureFunctions.PowerShell.Durable.SDK](https://www.powershellgallery.com/packages/AzureFunctions.PowerShell.Durable.SDK) module is now generally available (GA) and is recommended over the legacy SDK that's built into the Azure Functions PowerShell language worker. Going forward, the legacy SDK may not receive new features or bug fixes, and may eventually be removed from the worker. See [migration guide](./durable-functions-powershell-v2-sdk-migration-guide.md) for details on migrating to the standalone SDK. 
 
 ## GitHub repositories
 

articles/azure-functions/durable/durable-functions-powershell-v2-sdk-migration-guide.md

@@ -195,6 +195,6 @@ In this section, we describe the interface and behavioral changes you can expect
 * Exceptions thrown by activities scheduled with `Wait-DurableTask` (as in the Fan-Out/Fan-In pattern) are no longer silently ignored. Instead, on an exception, the cmdlet propagates that exception to the orchestrator so that it may be handled by user-code.
 * Null values are no longer dropped from the result list of a `Wait-DurableTask` (i.e., WhenAll) invocation. This means that a successful invocation of `Wait-DurableTask` without the `-Any` flag should return an array of the same size as the number of tasks it scheduled.
 
-### Where to get support, provide feedback, and suggest changes
+### Get support and provide feedbsck
 
 Please report any feedback and suggestions to the SDK's [_GitHub repo_](https://github.com/Azure/azure-functions-durable-powershell).

articles/azure-functions/durable/durable-functions-sub-orchestrations.md

@@ -16,7 +16,7 @@ An orchestrator function can call another orchestrator function using the *"call
 Sub-orchestrator functions behave just like activity functions from the caller's perspective. They can return a value and throw an exception as the parent orchestrator function anticipates them.
 
 > [!NOTE]
-> In PowerShell, sub-orchestrations are supported in the [standalone Durable Functions PowerShell SDK](durable-functions-powershell-v2-sdk-migration-guide.md) only.
+> In PowerShell, sub-orchestrations are supported in the standalone SDK only: [`AzureFunctions.PowerShell.Durable.SDK`](https://www.powershellgallery.com/packages/AzureFunctions.PowerShell.Durable.SDK). See the difference between the standalone SDK and the legacy built-in SDK along with [migration guide](durable-functions-powershell-v2-sdk-migration-guide.md).
  
 [!INCLUDE [functions-nodejs-durable-model-description](../../../includes/functions-nodejs-durable-model-description.md)]
 

articles/azure-functions/durable/quickstart-powershell-vscode.md

@@ -149,7 +149,7 @@ You added an HTTP-triggered function that starts an orchestration. Open *HttpSta
 You now have a Durable Functions app that you can run locally and deploy to Azure.
 
 > [!TIP]
-> This quickstart uses the standalone Durable Functions PowerShell SDK, which is now generally available and provides the best performance and latest features. For more information about the SDK and migration from the built-in version, see the [standalone PowerShell SDK guide](./durable-functions-powershell-v2-sdk-migration-guide.md).
+> This quickstart uses the standalone Durable Functions PowerShell SDK, which is now generally available and provides the best performance and latest features. For more information about the SDK and migration from the legacy built-in version, see the [standalone PowerShell SDK guide](./durable-functions-powershell-v2-sdk-migration-guide.md).
 
 ## Test the function locally