--- a/paq/prov-aq.html	Tue Mar 26 20:17:15 2013 +0000
+++ b/paq/prov-aq.html	Tue Mar 26 21:45:03 2013 +0000
@@ -411,7 +411,7 @@
           </tr>
           <tr style="vertical-align: top;">
             <td><a class="internalDFN">Pingback-URI</a></td>
-            <td>A provenance pingback service.  This is a service to which provenance pingback information can be submitted using an HTTP POST operation per <a href="#forward-provenance" class="sectionRef"></a>.  No other operations are specified.</td>
+            <td>A provenance pingback service.  This is a service to which provenance pingback information can be submitted using an HTTP POST operation per <a href="#provenance-pingback" class="sectionRef"></a>.  No other operations are specified.</td>
             <td>None specified (the owner of a provenance pingback URI may choose to return useful information, but is not required to do so.)</td>
           </tr>
         </table>
@@ -1106,7 +1106,7 @@
       <p>Provenance may be used by audits to establish accountability for information use [[INFO-ACC]] and to verify use of proper processes in information processing activities.  Thus, provenance management systems can provide mechanisms to support auditing and enforcement of information handling policies. In such cases, provenance itself may be a valuable target for attack by malicious agents, and care must be taken to ensure it is stored securely and in a fashion that resists attempts to tamper with it.
       </p>
       <p>
-        The pingback service described in <a href="#forward-provenance" class="sectionRef"></a> might be abused for "link spamming" (similar to the way that weblog ping-backs have been used to direct viewers to spam sites).  As with many such services, an application needs to find a balance between maintaining ease of submission for useful information and blocking unwanted information.  We have no easy solutions for this problem, and the caveats noted above about establishing integrity of provenance records apply similarly to information provided by ping-back calls.
+        The pingback service described in <a href="#provenance-pingback" class="sectionRef"></a> might be abused for "link spamming" (similar to the way that weblog ping-backs have been used to direct viewers to spam sites).  As with many such services, an application needs to find a balance between maintaining ease of submission for useful information and blocking unwanted information.  We have no easy solutions for this problem, and the caveats noted above about establishing integrity of provenance records apply similarly to information provided by ping-back calls.
       </p>
       <p>
         When clients and servers are retrieving submitted URIs such as provenance descriptions and following or registering links; reasonable care should be taken to prevent malicious use such as distributed denial of service attacks (DDoS), cross-site request forgery (CSRF), spamming and hosting of inappropriate materials. Reasonable preventions might include same-origin policy, HTTP authorization, SSL, rate-limiting, spam filters, moderation queues, user acknowledgements and validation. It is out of scope for this document to specify how such mechanisms work and should be applied.
@@ -1182,7 +1182,7 @@
         <tr style="vertical-align: top;">
           <td><code>pingback</code></td>
           <td>Relates a resource to a provenance pingback service that may receive additional provenance links about the resource.</td>
-          <td><a href="#forward-provenance" class="sectionRef"></a></td>
+          <td><a href="#provenance-pingback" class="sectionRef"></a></td>
         </tr>
 
         <!--