diff --git a/docs/legal-notices.xml b/docs/legal-notices.xml
index eca267ba1..01c3e599e 100644
--- a/docs/legal-notices.xml
+++ b/docs/legal-notices.xml
@@ -196,8 +196,8 @@ Foundation</ulink>.  A modified version of the <ulink role="hidepdf"
 url="http://www.tcpdump.org">Libpcap portable packet capture
 library</ulink><indexterm><primary>libpcap</primary></indexterm>
 is distributed along with Nmap.
-The Windows version of Nmap utilized the Libpcap-derived
-<ulink role="hidepdf" url="http://www.winpcap.org">WinPcap library</ulink><indexterm><primary>WinPcap</primary></indexterm>
+The Windows version of Nmap utilizes the Libpcap-derived
+<ulink role="hidepdf" url="http://www.npcap.org">Ncap library</ulink><indexterm><primary>Npcap</primary></indexterm>
 instead.
 Regular expression support is provided by the
 <ulink role="hidepdf" url="http://www.pcre.org">PCRE library</ulink>,<indexterm><primary>Perl Compatible Regular Expressions (PCRE)</primary></indexterm>
diff --git a/docs/nmap-install.xml b/docs/nmap-install.xml
index eab23d77d..309f7fee2 100644
--- a/docs/nmap-install.xml
+++ b/docs/nmap-install.xml
@@ -717,6 +717,14 @@ quite as efficient as on Unix.  Here are the known limitations:
 <indexterm><primary>Windows</primary><secondary>limitations of</secondary></indexterm>
 <itemizedlist>
 
+<listitem><para>Nmap only supports ethernet interfaces (including most
+802.11 wireless cards and many VPN clients) for raw packet scans.
+Unless you use the <option>-sT -Pn</option> options, RAS connections
+(such as PPP dialups) and certain VPN clients are not supported.  This
+support was dropped when Microsoft removed raw TCP/IP socket support
+in Windows XP SP2.  Now Nmap must send lower-level ethernet frames
+instead.</para></listitem>
+
 <listitem><para>When using Nmap with WinPcap instead of Npcap, you cannot
 generally scan your own machine from itself (using a
 loopback<indexterm><primary>loopback
@@ -728,14 +736,6 @@ connect scan without pinging (<option>-sT -Pn</option>) as that uses
 the high level socket API rather than sending raw
 packets.</para></listitem>
 
-<listitem><para>Nmap only supports ethernet interfaces (including most
-802.11 wireless cards and many VPN clients) for raw packet scans.
-Unless you use the <option>-sT -Pn</option> options, RAS connections
-(such as PPP dialups) and certain VPN clients are not supported.  This
-support was dropped when Microsoft removed raw TCP/IP socket support
-in Windows XP SP2.  Now Nmap must send lower-level ethernet frames
-instead.</para></listitem>
-
 </itemizedlist>
 
 <indexterm><primary>Windows</primary><secondary>performance of</secondary></indexterm>
@@ -787,7 +787,7 @@ self-installer named
 (where <replaceable>version</replaceable> is the version number of the
 specific release).  Most Nmap users choose this option since it is so
 easy.  Another advantage of the self-installer is that it provides the option to install the Zenmap GUI and other tools.  Simply run the installer file and let it walk you through
-panels for choosing an install path and installing WinPcap.  The
+panels for choosing an install path and installing Npcap.  The
 installer was created with the open-source <ulink
 url="http://nsis.sourceforge.net/Main_Page">Nullsoft Scriptable
 Install System</ulink>.  After it completes, read <xref
@@ -1467,7 +1467,7 @@ zenmap</command> as root.  Analogous options are offered by
 most other package managers&mdash;consult their documentation for further
 information.</para>
 
-<para>If you installed Nmap from the Windows installer, simply open the <application>Control Panel</application>, select <quote>Add or Remove Programs</quote> and select the <quote>Remove</quote> button for Nmap.  You can also remove WinPcap unless you need it for other applications such as Wireshark.</para>
+<para>If you installed Nmap from the Windows installer, simply open the <application>Control Panel</application>, select <quote>Add or Remove Programs</quote> and select the <quote>Remove</quote> button for Nmap.  You can also remove Npcap unless you need it for other applications such as Wireshark.</para>
 
 <para>If you installed Nmap from source
 code, removal is slightly more difficult.  If you still have the build
diff --git a/ncat/docs/ncat.xml b/ncat/docs/ncat.xml
index ada7fd572..4c2206565 100644
--- a/ncat/docs/ncat.xml
+++ b/ncat/docs/ncat.xml
@@ -1104,7 +1104,7 @@ url="http://www.tcpdump.org">Libpcap portable packet capture
 library</ulink><indexterm><primary>libpcap</primary></indexterm>
 is distributed along with Ncat.
 The Windows version of Ncat utilized the Libpcap-derived
-<ulink role="hidepdf" url="http://www.winpcap.org">WinPcap library</ulink><indexterm><primary>WinPcap</primary></indexterm>
+<ulink role="hidepdf" url="http://www.npcap.org">Npcap library</ulink><indexterm><primary>Npcap</primary></indexterm>
 instead.
 Certain raw networking functions use the
 <ulink role="hidepdf" url="http://libdnet.sourceforge.net">Libdnet</ulink><indexterm><primary>libdnet</primary></indexterm>