From fb4738d10908b0a101c349120c20e91d8a14f00c Mon Sep 17 00:00:00 2001
From: Jason E <31452365+jasonepperly@users.noreply.github.com>
Date: Wed, 6 Dec 2023 08:25:36 -0500
Subject: [PATCH] Update nn-wtsprotocol-iwrdsprotocolconnection.md

Update to help Citrix get this right
---
 .../wtsprotocol/nn-wtsprotocol-iwrdsprotocolconnection.md       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sdk-api-src/content/wtsprotocol/nn-wtsprotocol-iwrdsprotocolconnection.md b/sdk-api-src/content/wtsprotocol/nn-wtsprotocol-iwrdsprotocolconnection.md
index a881d6c9ee31..4f5308d02c09 100644
--- a/sdk-api-src/content/wtsprotocol/nn-wtsprotocol-iwrdsprotocolconnection.md
+++ b/sdk-api-src/content/wtsprotocol/nn-wtsprotocol-iwrdsprotocolconnection.md
@@ -156,4 +156,4 @@ The <b>IWRdsProtocolConnection</b> interface inherits from the <a href="/windows
 
 ## -remarks
 
-To avoid a possible deadlock when calling any of the methods on this interface, you should not make any function or method calls that will directly or indirectly result in a Remote Desktop Services API being called. If you need to make any outbound call, you should start a new thread and make the outbound call from the new thread.
+To avoid a possible deadlock when calling any of the methods on this interface, you should not make any function or method calls that will directly or indirectly result in a Remote Desktop Services API being called. If you need to make any outbound call, you should start a new thread and make the outbound call from the new thread. If you make a new thread, do not wait on the thread to complete its work. Doing so defeats the purpose of making the work complete asynchronously.