updating service bus sdk type content

Author: mattchenderson

articles/azure-functions/dotnet-isolated-process-guide.md

@@ -246,7 +246,7 @@ Each trigger and binding extension also has its own minimum version requirement,
 
 <sup>1</sup> For output scenarios in which you would use an SDK type, you should create and work with SDK clients directly instead of using an output binding.
 
-<sup>2</sup> The preview for the Service Bus trigger does not yet support message settlement scenarios.
+<sup>2</sup> The Service Bus trigger does not yet support message settlement scenarios for the isolated model.
 
 <sup>3</sup> The Cosmos DB trigger uses the [Azure Cosmos DB change feed](../cosmos-db/change-feed.md) and exposes change feed items as JSON-serializable types. The absence of SDK types is by-design for this scenario.
 

articles/azure-functions/functions-bindings-service-bus.md

@@ -164,7 +164,7 @@ Functions 1.x exposed types from the deprecated [Microsoft.ServiceBus.Messaging]
 
 # [Extension 5.x+](#tab/extensionv5/isolated-process)
 
-The isolated worker process supports parameter types according to the tables below. Support for binding to types from [Azure.Messaging.ServiceBus] is in preview.
+The isolated worker process supports parameter types according to the tables below. Support for binding to types from [Azure.Messaging.ServiceBus] is in preview. Current support does not yet include message settlement scenarios for triggers.
 
 **Service Bus trigger**
 

includes/functions-bindings-service-bus-trigger-dotnet-isolated-types.md

@@ -21,12 +21,9 @@ When you want the function to process a batch of messages, the Service Bus trigg
 | --- | --- |
 | `T[]` where `T` is one of the single message types  | An array of events from the batch. Each entry represents one event. |
 
-The isolated process model does not yet support message settlement scenarios for Service Bus triggers.
-
 <sup>1</sup> To use these types, you need to reference [Microsoft.Azure.Functions.Worker.Extensions.ServiceBus 5.10.0-preview2 or later](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.ServiceBus/5.10.0-preview2) and the [common dependencies for SDK type bindings](../articles/azure-functions/dotnet-isolated-process-guide.md#sdk-types). [Version 5.12.0-preview1 and later](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Extensions.ServiceBus/5.12.0-preview1) requires moving the common dependencies forward to their GA versions. Specifically, you should use [Microsoft.Azure.Functions.Worker 1.18.0 or later](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker/1.18.0) and [Microsoft.Azure.Functions.Worker.Sdk 1.12.0 or later](https://www.nuget.org/packages/Microsoft.Azure.Functions.Worker.Sdk/1.12.0).
 
-[Azure.Messaging.ServiceBus]: /dotnet/api/azure.messaging.servicebus
+> [!NOTE]
+> The isolated process model does not yet support message settlement scenarios for Service Bus triggers.
+
 [ServiceBusReceivedMessage]: /dotnet/api/azure.messaging.servicebus.servicebusreceivedmessage
-[ServiceBusMessage]: /dotnet/api/azure.messaging.servicebus.servicebusmessage
-[ServiceBusClient]: /dotnet/api/azure.messaging.servicebus.servicebusclient
-[ServiceBusSender]: /dotnet/api/azure.messaging.servicebus.servicebussender