From 7692d37378d6b75a3758d27b3655092ddde0dcda Mon Sep 17 00:00:00 2001
From: Jan Kotas <jkotas@microsoft.com>
Date: Wed, 11 Jun 2025 23:08:46 -0700
Subject: [PATCH] Clarify order of signal handler execution for .NET 10

Follow up on https://github.com/dotnet/runtime/pull/116557
---
 xml/System.Runtime.InteropServices/PosixSignalRegistration.xml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/xml/System.Runtime.InteropServices/PosixSignalRegistration.xml b/xml/System.Runtime.InteropServices/PosixSignalRegistration.xml
index eac1e3bbada..1dfad3a108c 100644
--- a/xml/System.Runtime.InteropServices/PosixSignalRegistration.xml
+++ b/xml/System.Runtime.InteropServices/PosixSignalRegistration.xml
@@ -82,6 +82,7 @@ Raw values can be provided for `signal` on Unix by casting them to <xref:System.
             <xref:System.Runtime.InteropServices.PosixSignal.SIGINT> and <xref:System.Runtime.InteropServices.PosixSignal.SIGQUIT> can be canceled on both
             Windows and on Unix platforms; <xref:System.Runtime.InteropServices.PosixSignal.SIGTERM> can only be canceled on Unix.
             On Unix, terminal configuration can be canceled for <xref:System.Runtime.InteropServices.PosixSignal.SIGCHLD> and <xref:System.Runtime.InteropServices.PosixSignal.SIGCONT>.
+            In .NET 10 and later versions, the handlers are executed in reverse order of their registration.
 
           ]]></format>
         </remarks>