From 6fadd16d6a804184457745fb6c935f8e255a837f Mon Sep 17 00:00:00 2001
From: dmiller <dmiller@e0a8ed71-7df4-0310-8962-fdc924857419>
Date: Sun, 17 Jan 2021 16:19:58 +0000
Subject: [PATCH] Document iocp nsock engine in Nmap man page; note the default
 for --nsock-engine

---
 docs/refguide.xml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/docs/refguide.xml b/docs/refguide.xml
index 4671c0291..7071de373 100644
--- a/docs/refguide.xml
+++ b/docs/refguide.xml
@@ -2964,7 +2964,7 @@ worth the extra time.</para>
 
       <varlistentry>
         <term><option>--nsock-engine
-        epoll|kqueue|poll|select</option>
+        iocp|epoll|kqueue|poll|select</option>
         <indexterm><primary><option>--nsock-engine</option></primary></indexterm>
         <indexterm><primary>Nsock IO engine</primary></indexterm>
         </term>
@@ -2976,7 +2976,8 @@ available on your system.  Engines are named after the name of the IO
 management facility they leverage.  Engines currently implemented are
 <literal>epoll</literal>, <literal>kqueue</literal>, <literal>poll</literal>,
 and <literal>select</literal>, but not all will be present on any platform.
-Use <command>nmap -V</command> to see which engines are supported.</para>
+By default, Nmap will use the "best" engine, i.e. the first one in this list that is supported.
+Use <command>nmap -V</command> to see which engines are supported on your platform.</para>
 
         </listitem>
       </varlistentry>