code syntax

Author: spelluru

articles/event-hubs/event-hubs-availability-and-consistency.md

@@ -49,6 +49,8 @@ For use cases that require the maximum up time, this model is preferred.
 In some scenarios, the ordering of events can be important. For example, you may want your back-end system to process an update command before a delete command. In this instance, you can either set the partition key on an event, or use a `PartitionSender` object (if you are using the old Microsoft.Azure.Messaging library) to only send events to a certain partition. Doing so ensures that when these events are read from the partition, they are read in order. If you are using the **Azure.Messaging.EventHubs** library and for more information, see [Migrating code from PartitionSender to EventHubProducerClient for publishing events to a partition](https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/eventhub/Azure.Messaging.EventHubs/MigrationGuide.md#migrating-code-from-partitionsender-to-eventhubproducerclient-for-publishing-events-to-a-partition).
 
 #### [Azure.Messaging.EventHubs (5.0.0 or later)](#tab/latest)
+
+```csharp
 var connectionString = "<< CONNECTION STRING FOR THE EVENT HUBS NAMESPACE >>";
 var eventHubName = "<< NAME OF THE EVENT HUB >>";
 
@@ -61,7 +63,11 @@ await using (var producerClient = new EventHubProducerClient(connectionString, e
 
     await producerClient.SendAsync(eventBatch);
 }
+```
+
 #### [Microsoft.Azure.EventHubs (4.1.0 or earlier)](#tab/old)
+
+```csharp
 var connectionString = "<< CONNECTION STRING FOR THE EVENT HUBS NAMESPACE >>";
 var eventHubName = "<< NAME OF THE EVENT HUB >>";
 
@@ -81,6 +87,7 @@ finally
     await partitionSender.CloseAsync();
     await eventHubClient.CloseAsync();
 }
+```
 
 ---