human edits

Author: gewarren

docs/core/compatibility/core-libraries/10.0/sigterm-signal-handler.md

@@ -1,13 +1,13 @@
 ---
 title: "Breaking change: .NET runtime no longer provides default SIGTERM signal handler"
 description: "Learn about the breaking change in .NET 10 where the runtime no longer provides a default SIGTERM signal handler."
-ms.date: 01/30/2025
+ms.date: 06/06/2025
 ai-usage: ai-assisted
 ms.custom: https://github.com/dotnet/docs/issues/46226
 ---
 # .NET runtime no longer provides default SIGTERM signal handler
 
-On Unix systems, .NET runtime no longer provides a default SIGTERM signal handler. On Windows, .NET runtime no longer provides default handlers for `CTRL_CLOSE_EVENT` and `CTRL_SHUTDOWN_EVENT` signals that are equivalents of Unix `SIGTERM` signal.
+On Unix systems, the .NET runtime no longer provides a default SIGTERM signal handler. On Windows, the .NET runtime no longer provides default handlers for the [`CTRL_CLOSE_EVENT` and `CTRL_SHUTDOWN_EVENT` signals](/windows/console/handlerroutine), which are equivalents of Unix `SIGTERM` signal.
 
 This change reverts the SIGTERM signal handling behavior to what it used to be in .NET Framework and classic Mono runtime.
 
@@ -17,33 +17,33 @@ This change reverts the SIGTERM signal handling behavior to what it used to be i
 
 ## Previous behavior
 
-Previously, a SIGTERM signal handler registered by .NET runtime by default triggered graceful application exit. <xref:System.AppDomain.ProcessExit?displayProperty=nameWithType> and <xref:System.Runtime.Loader.AssemblyLoadContext.Unloading?displayProperty=nameWithType> events were raised before the application exited.
+Previously, a SIGTERM signal handler registered by the .NET runtime by default triggered graceful application exit. <xref:System.AppDomain.ProcessExit?displayProperty=nameWithType> and <xref:System.Runtime.Loader.AssemblyLoadContext.Unloading?displayProperty=nameWithType> events were raised before the application exited.
 
 ## New behavior
 
-Starting in .NET 10, .NET runtime does not override SIGTERM signal handling provided by the operating system. The typical default SIGTERM signal handler provided by the operating system terminates the application immediately. <xref:System.AppDomain.ProcessExit?displayProperty=nameWithType> and <xref:System.Runtime.Loader.AssemblyLoadContext.Unloading?displayProperty=nameWithType> events are not raised.
+Starting in .NET 10, the .NET runtime does not override SIGTERM signal handling provided by the operating system. The typical default SIGTERM signal handler provided by the operating system terminates the application immediately. <xref:System.AppDomain.ProcessExit?displayProperty=nameWithType> and <xref:System.Runtime.Loader.AssemblyLoadContext.Unloading?displayProperty=nameWithType> events aren't raised.
 
 ## Type of breaking change
 
 This is a [behavioral change](../../categories.md#behavioral-change).
 
 ## Reason for change
 
-The SIGTERM signal handler registered by .NET runtime by default was both insufficient for some app models (for example, console and containerized applications) and incompatible with other app models (for example, Windows services). It's better to leave it to higher level libraries or application code to register signal handlers appropriate for the given app model.
+The SIGTERM signal handler registered by the .NET runtime by default was both insufficient for some app models (for example, console and containerized applications) and incompatible with other app models (for example, Windows services). It's better to leave it to higher-level libraries or application code to register signal handlers appropriate for the given app model.
 
 ## Recommended action
 
-- No action is necessary for typical ASP.NET applications or applications that use higher level APIs such as `HostingHostBuilderExtensions.UseConsoleLifetime` to handle app-model specific concerns. These higher-level APIs register handlers for SIGTERM and other signals as appropriate.
+- No action is necessary for typical ASP.NET applications or applications that use higher-level APIs such as <xref:Microsoft.Extensions.Hosting.HostingHostBuilderExtensions.UseConsoleLifetime*?displayProperty=nameWithType> to handle app-model specific concerns. These higher-level APIs register handlers for SIGTERM and other signals as appropriate.
 
-- Applications that wish to handle SIGTERM signal without taking a dependency on higher level libraries can replicate the old behavior by creating a SIGTERM signal handler in their Main method using <xref:System.Runtime.InteropServices.PosixSignalRegistration.Create%2A?displayProperty=nameWithType> API:
+- If you want to handle SIGTERM signal without taking a dependency on higher-level libraries, you can replicate the previous behavior by creating a SIGTERM signal handler in your `Main` method using the <xref:System.Runtime.InteropServices.PosixSignalRegistration.Create%2A?displayProperty=nameWithType> API:
 
 ```csharp
-using System;
-using System.Runtime.InteropServices;
-
 static void Main()
 {
-    using var termSignalRegistration = PosixSignalRegistration.Create(PosixSignal.SIGTERM, (_) => Environment.Exit(0));
+    using var termSignalRegistration =
+        PosixSignalRegistration.Create(
+            PosixSignal.SIGTERM,
+            (_) => Environment.Exit(0));
 
     // Your application code here
 }

docs/core/compatibility/toc.yml

@@ -28,7 +28,7 @@ items:
                 href: core-libraries/10.0/ldap-directorycontrol-parsing.md
               - name: MacCatalyst version normalization
                 href: core-libraries/10.0/maccatalyst-version-normalization.md
-              - name: .NET runtime no longer provides default SIGTERM signal handler
+              - name: No default SIGTERM signal handler
                 href: core-libraries/10.0/sigterm-signal-handler.md
               - name: System.Linq.AsyncEnumerable included in core libraries
                 href: core-libraries/10.0/asyncenumerable.md
@@ -1414,6 +1414,8 @@ items:
                 href: core-libraries/10.0/ldap-directorycontrol-parsing.md
               - name: MacCatalyst version normalization
                 href: core-libraries/10.0/maccatalyst-version-normalization.md
+              - name: No default SIGTERM signal handler
+                href: core-libraries/10.0/sigterm-signal-handler.md
               - name: System.Linq.AsyncEnumerable included in core libraries
                 href: core-libraries/10.0/asyncenumerable.md
           - name: .NET 9