More Pesala fixes

Author: ggailey777

articles/azure-functions/durable/durable-functions-dotnet-isolated-overview.md

@@ -86,16 +86,20 @@ public class MyOrchestration : TaskOrchestrator<string, string>
 ```
 
 ## Durable entities
-Durable entities are supported in the .NET isolated worker. See [developer's guide](./durable-functions-dotnet-entities.md).
+
+Durable entities are supported in the .NET isolated worker. For more information, see the [developer's guide](./durable-functions-dotnet-entities.md).
 
 ## Migration guide
 
-#### [Migrate to .NET 8.0](https://learn.microsoft.com/en-us/azure/azure-functions/migrate-dotnet-to-isolated-model?tabs=net8#choose-your-target-net-version)
-This guide assumes you're starting with a .NET Durable Functions 2.x project.
+This process assumes you're starting with a .NET Durable Functions 2.x project running in-process with the Functions host. When 
+
+### Migrate your project
+
+The first step is to [migrate your .NET project to the isolated worker process](../migrate-dotnet-to-isolated-model.md). 
 
-### Update your project
+### Update package reference 
 
-The first step is to update your project to [Azure Functions .NET isolated](../migrate-dotnet-to-isolated-model.md). Then, update your Durable Functions NuGet package references.
+After you've migrated your app to use the isolate worker process, you must update your Durable Functions NuGet package to reference the isolated worker-specific package, like in this example:
 
 Old:
 

articles/azure-functions/functions-bindings-http-webhook-trigger.md

@@ -1108,12 +1108,12 @@ Most HTTP trigger templates require an access key in the request. So your HTTP r
 https://<APP_NAME>.azurewebsites.net/api/<FUNCTION_NAME>?code=<API_KEY>
 ```
 
+Function apps that run in containers use the domain of the container host. For an example HTTP endpoint hosted in Azure Container Apps, see the example in [this Container Apps hosting article](functions-deploy-container-apps.md#verify-your-functions-on-azure).
+
 The key can be included in a query string variable named `code`, as mentioned earlier. It can also be included in an `x-functions-key` HTTP header. The value of the key can be any function key defined for the function, or any host key.
 
 You can allow anonymous requests, which don't require keys. You can also require that the master key is used. You change the default authorization level by using the `authLevel` property in the binding JSON. 
 
-#### [Azure function app with Azure container apps](https://learn.microsoft.com/en-us/azure/azure-functions/functions-deploy-container-apps?tabs=acr%2Cbash&pivots=programming-language-powershell#verify-your-functions-on-azure)
-
 > [!NOTE]
 > When running functions locally, authorization is disabled regardless of the specified authorization level setting. After publishing to Azure, the `authLevel` setting in your trigger is enforced. Keys are still required when running [locally in a container](functions-create-container-registry.md#build-the-container-image-and-verify-locally).