www/server/standards README.webmastering.html

[Jason Self]

CVSROOT:        /web/www
Module name:    www
Changes by:     Jason Self <jxself>     12/12/22 17:43:25

Modified files:
        server/standards: README.webmastering.html 

Log message:
        Please check the broken link report regularly

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.webmastering.html?cvsroot=www&r1=1.153&r2=1.154

Patches:
Index: README.webmastering.html
===================================================================
RCS file: /web/www/www/server/standards/README.webmastering.html,v
retrieving revision 1.153
retrieving revision 1.154
diff -u -b -r1.153 -r1.154
--- README.webmastering.html    2 Dec 2012 15:44:17 -0000       1.153
+++ README.webmastering.html    22 Dec 2012 17:43:24 -0000      1.154
@@ -68,8 +68,9 @@
 
 <ul>
   <li>Fix typos, misspellings, broken links, and the like (a report of
-       broken links in <tt>/home/w/wwj/linc/reports</tt> on Fencepost.
-       The reports are separated by language code.)</li>
+       broken links is available at 
+<a 
href="/server/source/linc/linc-report.html">/server/source/linc/linc-report.html</a>
 
+The reports are separated by language code.)</li>
   <li>Requests from Richard Stallman
        <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>,
        John Sullivan <a 
href="mailto:address@hidden";>&lt;address@hidden&gt;</a>,
@@ -810,16 +811,16 @@
 here.  Only requests which may require non-obvious action are listed.</p>
 
 <h4 id="deadlink">Fixing dead links</h4>
-
-<p>If a link has gone bad because a page has moved, try to find its
-replacement.  If you are successful, re-check the page to ensure that it
-meets our linking criteria, and if so, add it.  If you do not find a
-replacement, remove the link&mdash;if it's central to the page, you may
-need to make a note explaining that the resource is no longer available.
-If the page no longer meets our linking criteria, you'll have to make a
-judgment call, and weigh the value of the link against its problems';
-you may want to mail the person who wrote the page with the link to get
-a second opinion.</p>
+<p>Please check the <a href="/server/source/linc/linc-report.html">broken 
+link  report</a> regularly and handle them. If a link has gone bad because a 
+page has moved, try to find its replacement.  If you are successful, re-check 
+the page to ensure that it meets our linking criteria, and if so, add it.  If 
+you do not find a replacement, remove the link&mdash;if it's central to the 
+page, you may need to make a note explaining that the resource is no longer 
+available. If the page no longer meets our linking criteria, you'll have to 
+make a judgment call, and weigh the value of the link against its problems';
+you may want to mail the person who wrote the page with the link or 
+www-discuss to get a second opinion.</p>
 
 <p>If you do remove a link from a page that we don't maintain&mdash;for
 instance, the page for a piece of software which is kept up-to-date by
@@ -1230,7 +1231,7 @@
 
 <p>Updated:
 <!-- timestamp start -->
-$Date: 2012/12/02 15:44:17 $
+$Date: 2012/12/22 17:43:24 $
 <!-- timestamp end -->
 </p>
 </div>