Fix warnings

Author: AnatoliB

articles/azure-functions/durable/durable-functions-orchestration-versioning.md

@@ -1,7 +1,7 @@
 ---
 title: Orchestration Versioning in Durable Functions - Azure
 description: Learn how to use the Orchestration Versioning feature in Durable Functions for zero-downtime deployments with breaking changes.
-author: azfuncdf
+author: AnatoliB
 ms.topic: conceptual
 ms.date: 07/03/2025
 ms.author: azfuncdf
@@ -342,6 +342,10 @@ By default, all new orchestration instances are created with the current `defaul
 
 You can override the default version by providing a specific version value when creating new orchestration instances using the orchestration client APIs. This allows fine-grained control over which version each new orchestration instance uses.
 
+# [C# (In-process)](#tab/csharp)
+
+This feature is not supported in the in-process model.
+
 # [C# (Isolated)](#tab/csharp-isolated)
 
 ```csharp
@@ -428,6 +432,3 @@ Over time, you may want to remove legacy code paths from your orchestrator funct
 
 > [!div class="nextstepaction"]
 > [Learn about general versioning strategies](durable-functions-versioning.md)
-
-> [!div class="nextstepaction"]
-> [Configure host.json settings for Durable Functions](../../../includes/functions-host-json-durabletask.md)

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

@@ -206,15 +206,15 @@ Because of these potential failures, the "do nothing" strategy is not recommende
 > [!NOTE]
 > Orchestration Versioning is currently in public preview.
 
-Orchestration Versioning is a built-in feature that enables [zero-downtime deployments](durable-functions-zero-downtime-deployments.md) with breaking changes. This approach allows different versions of orchestrations to coexist and execute concurrently without conflicts.
+Orchestration Versioning is a built-in feature that enables [zero-downtime deployments](durable-functions-zero-downtime-deployment.md) with breaking changes. This approach allows different versions of orchestrations to coexist and execute concurrently without conflicts.
 
 With Orchestration Versioning:
 - Each orchestration instance gets a version permanently associated with it when created
 - Orchestrator functions can examine their version and branch execution accordingly  
 - Workers running newer orchestrator function versions can continue executing orchestration instances created by older versions
 - The runtime prevents workers running older orchestrator function versions from executing orchestrations started by newer versions
 
-This strategy is recommended for applications that need to support breaking changes while maintaining [zero-downtime deployments](durable-functions-zero-downtime-deployments.md). The feature is currently available for .NET in-process and .NET isolated programming models.
+This strategy is recommended for applications that need to support breaking changes while maintaining [zero-downtime deployments](durable-functions-zero-downtime-deployment.md). The feature is currently available for .NET in-process and .NET isolated programming models.
 
 For detailed configuration and implementation guidance, see [Orchestration Versioning in Durable Functions](durable-functions-orchestration-versioning.md).