From 86aa1975ed0d1e8e9f2e6544df1c0335c81ffbd6 Mon Sep 17 00:00:00 2001
From: jasonepperly <31452365+jasonepperly@users.noreply.github.com>
Date: Fri, 15 Sep 2023 13:34:34 -0400
Subject: [PATCH] Update nn-wtsprotocol-iwrdsprotocolconnection.md

Updated the contract to make sure it is clear that if the work is moved to a new thread that the creator of the new thread cannot wait on the thread to complete the work. The entire purpose of making a new thread to do the work is to make the work async, non-blocking.
---
 .../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.