From aae22b340eedf300cd37470eb56326f53ebc609f Mon Sep 17 00:00:00 2001
From: david <david@e0a8ed71-7df4-0310-8962-fdc924857419>
Date: Wed, 26 May 2010 05:20:12 +0000
Subject: [PATCH] Update the description of UDP payloads to point to a new
 section on nmap-payloads instead of referring to payload.cc.

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

diff --git a/docs/refguide.xml b/docs/refguide.xml
index 437e1cfc8..29da5a2ba 100644
--- a/docs/refguide.xml
+++ b/docs/refguide.xml
@@ -630,9 +630,8 @@ you would expect.</para>
           packet will be empty, though for a few a protocol-specific
           payload will be sent that is more likely to get a
           response.<indexterm><primary>protocol-specific payloads</primary><secondary>UDP</secondary></indexterm>
-          See the file
-          <filename>payload.cc</filename><indexterm><primary><filename>payload.cc</filename></primary></indexterm>
-          for exactly which ports have payloads. The
+          See <xref linkend="nmap-payloads"/>
+          for a description of the database of payloads. The
           <option>--data-length</option><indexterm><primary><option>--data-length</option></primary></indexterm>
           option sends a fixed-length random payload for all ports.</para>