From 326e4bd0b96f199c90e2d475ea09f0cf1ac92001 Mon Sep 17 00:00:00 2001
From: Aaron Robinson <arobins@microsoft.com>
Date: Wed, 24 Sep 2025 19:01:08 -0700
Subject: [PATCH] Update remarks for UnhandledException event

Added clarification that handlers may be invoked multiple times if exceptions are thrown from different threads.
---
 xml/System/AppDomain.xml | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/xml/System/AppDomain.xml b/xml/System/AppDomain.xml
index 666077d4772..40325728556 100644
--- a/xml/System/AppDomain.xml
+++ b/xml/System/AppDomain.xml
@@ -8821,7 +8821,10 @@ The friendly name of the default application domain is the file name of the proc
       </ReturnValue>
       <Docs>
         <summary>Occurs when an exception is not caught.</summary>
-        <remarks>For more information about this API, see <see href="/dotnet/fundamentals/runtime-libraries/system-appdomain-unhandledexception">Supplemental API remarks for UnhandledException</see>.</remarks>
+        <remarks>
+          Handlers may be invoked multiple times if exceptions are thrown from different threads.
+
+          For more information about this API, see <see href="/dotnet/fundamentals/runtime-libraries/system-appdomain-unhandledexception">Supplemental API remarks for UnhandledException</see>.</remarks>
         <example>
           <format type="text/markdown"><![CDATA[
 The following example demonstrates the <xref:System.AppDomain.UnhandledException> event. It defines an event handler, `MyHandler`, that is invoked whenever an unhandled exception is thrown in the default application domain. It then throws two exceptions. The first is handled by a **try/catch** block. The second is unhandled and invokes the `MyHandle` routine before the application terminates.