From 91bfa6ea3ece3bf9ba0f167c8c97f8e06cf1192d Mon Sep 17 00:00:00 2001
From: Min Huang <huangmin@microsoft.com>
Date: Thu, 25 Jan 2024 14:26:49 +0800
Subject: [PATCH] Update QueueClientOptions.xml

---
 xml/Azure.Storage.Queues/QueueClientOptions.xml | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/xml/Azure.Storage.Queues/QueueClientOptions.xml b/xml/Azure.Storage.Queues/QueueClientOptions.xml
index a65f3f853051..40af215f385f 100644
--- a/xml/Azure.Storage.Queues/QueueClientOptions.xml
+++ b/xml/Azure.Storage.Queues/QueueClientOptions.xml
@@ -169,6 +169,9 @@
              the event handler itself.</para><para>The handler is potentially invoked by both synchronous and asynchronous receive and peek APIs. Therefore implementation of the handler should align with
              <see cref="T:Azure.Storage.Queues.QueueClient" /> APIs that are being used.
              See <see cref="T:Azure.Core.SyncAsyncEventHandler`1" /> about how to implement handler correctly. The example below shows a handler with all possible cases explored.
+             </para></summary>
+        <remarks>To be added.</remarks>
+        <example>
              <code snippet="Snippet:Azure_Storage_Queues_Samples_Sample03_MessageEncoding_MessageDecodingFailedHandlerAsync" language="csharp">
              QueueClientOptions queueClientOptions = new QueueClientOptions()
              {
@@ -197,8 +200,8 @@
              };
             
              QueueClient queueClient = new QueueClient(connectionString, queueName, queueClientOptions);
-             </code></para></summary>
-        <remarks>To be added.</remarks>
+             </code>
+        </example>
       </Docs>
     </Member>
     <Member MemberName="MessageEncoding">