File 0406-erts-Cleanup.patch of Package erlang

From c4bed61d9345e3e86d291a234f7489d7456273d9 Mon Sep 17 00:00:00 2001
From: Micael Karlberg <bmk@erlang.org>
Date: Tue, 29 Apr 2025 14:11:06 +0200
Subject: [PATCH 2/2] [erts] Cleanup

OTP-19617
---
 erts/emulator/nifs/win32/win_socket_asyncio.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/erts/emulator/nifs/win32/win_socket_asyncio.c b/erts/emulator/nifs/win32/win_socket_asyncio.c
index 9b4d5cbb99..803cb6507a 100644
--- a/erts/emulator/nifs/win32/win_socket_asyncio.c
+++ b/erts/emulator/nifs/win32/win_socket_asyncio.c
@@ -8134,7 +8134,7 @@ void esaio_completion_send_completed(ErlNifEnv*       env,
              * that is; size (length) of I/O vector > IOV_MAX.
              * This is *only* possible for *sendv*!
              * sendmsg also has the data in an I/O vector, but is only
-             * supported for DGRAM, where *all* of the I/O vector must
+             * supported for DGRAM, where *all* of the I/O vector *must*
              * fit in one message.
              */
 
@@ -8341,7 +8341,7 @@ void esaio_completion_send_fail(ErlNifEnv*       env,
  *
  *     CompletionInfo:   {CompletionHandle, CompletionStatus}
  *     CompletionHandle: reference()
- *     Result:           ok | {ok, Written} | {error, Reason}
+ *     CompletionStatus: ok | {ok, Written} | {error, Reason}
  *
  * Note that the normal result is 'ok', but if the attempt was to send
  * an I/O vector with length > IOV_MAX, then the vector will be cut
-- 
2.43.0