Recompile docs so (hopefully) I can get some feedback on the installation chapter changes.

webtools/bugzilla/docs/html/administration.html

@@ -180,22 +180,22 @@ HREF="cust-templates.html"
 ><DL
 ><DT
 >5.7.1. <A
-HREF="cust-templates.html#AEN1425"
+HREF="cust-templates.html#AEN1524"
 >What to Edit</A
 ></DT
 ><DT
 >5.7.2. <A
-HREF="cust-templates.html#AEN1444"
+HREF="cust-templates.html#AEN1543"
 >How To Edit Templates</A
 ></DT
 ><DT
 >5.7.3. <A
-HREF="cust-templates.html#AEN1454"
+HREF="cust-templates.html#AEN1553"
 >Template Formats</A
 ></DT
 ><DT
 >5.7.4. <A
-HREF="cust-templates.html#AEN1467"
+HREF="cust-templates.html#AEN1566"
 >Particular Templates</A
 ></DT
 ></DL

webtools/bugzilla/docs/html/conventions.html

@@ -81,7 +81,7 @@ NAME="conventions"
 ><DIV
 CLASS="informaltable"
 ><A
-NAME="AEN110"
+NAME="AEN111"
 ></A
 ><P
 ></P

webtools/bugzilla/docs/html/copyright.html

@@ -96,9 +96,9 @@ VALIGN="TOP"
 ><P
 >&#13;	Permission is granted to copy, distribute and/or modify this
 	document under the terms of the GNU Free Documentation
-	License, Version 1.1 or any later version published  by the
+	License, Version 1.1 or any later version published by the
 	Free Software Foundation; with no Invariant Sections, no
-	Front-Cover Texts, and  with no Back-Cover Texts.  A copy of
+	Front-Cover Texts, and with no Back-Cover Texts. A copy of
 	the license is included in <A
 HREF="gfdl.html"
 >Appendix E</A

webtools/bugzilla/docs/html/credits.html

@@ -184,13 +184,13 @@ HREF="news://news.mozilla.org/netscape/public/mozilla/webtools"
 TARGET="_top"
 >news://news.mozilla.org/netscape/public/mozilla/webtools</A
 >
-      newsgroup.  Without your discussions, insight, suggestions, and patches,
+      newsgroup. Without your discussions, insight, suggestions, and patches,
       this could never have happened.
     </P
 ><P
 >&#13;      Thanks also go to the following people for significant contributions 
       to this documentation (in alphabetical order):
-      Andrew Pearson, Ben FrantzDale, Eric Hanson, Gervase Markham, Joe Robins, Kevin Brannen, Ron Teitelbaum, Spencer Smith, Zach Liption
+      Andrew Pearson, Ben FrantzDale, Eric Hanson, Gervase Markham, Joe Robins, Kevin Brannen, Martin Wulffeld, Ron Teitelbaum, Spencer Smith, Zach Liption
       .
     </P
 ></DIV

webtools/bugzilla/docs/html/cust-templates.html

@@ -99,7 +99,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1425"
+NAME="AEN1524"
 ></A
 >5.7.1. What to Edit</H2
 ><P
@@ -214,7 +214,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1444"
+NAME="AEN1543"
 ></A
 >5.7.2. How To Edit Templates</H2
 ><P
@@ -296,7 +296,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1454"
+NAME="AEN1553"
 ></A
 >5.7.3. Template Formats</H2
 ><P
@@ -358,7 +358,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN1467"
+NAME="AEN1566"
 ></A
 >5.7.4. Particular Templates</H2
 ><P

webtools/bugzilla/docs/html/dbdoc.html

@@ -108,7 +108,7 @@ NAME="dbdoc"
 ><P
 >But Certain Death speaks up -- a tiny voice, from the dark corners
     of the conference room. "I have a concern," the voice hisses from the
-    darkness, "about the use of the word 'verified'.</P
+    darkness, "about the use of the word 'verified'."</P
 ><P
 >The room, previously filled with happy chatter, lapses into
     reverential silence as Certain Death (better known as the Vice President
@@ -135,7 +135,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN2091"
+NAME="AEN2190"
 ></A
 >B.2.1. Bugzilla Database Basics</H2
 ><P
@@ -154,14 +154,12 @@ CLASS="QUOTE"
 >"tinyint"</SPAN
 >
 
-      entry in MySQL. I recommend you refer to the MySQL documentation,
+      entry in MySQL. I recommend you refer to the
-      available at 
       <A
-HREF="http://www.mysql.com/doc.html"
+HREF="http://www.mysql.com/documentation/"
 TARGET="_top"
->MySQL.com</A
+>MySQL documentation</A
 >
-
       . Below are the basics you need to know about the Bugzilla database.
       Check the chart above for more details.</P
 ><P
@@ -205,7 +203,7 @@ HREF="http://www.mysql.com/php/manual.php3?section=Privilege_system"
 TARGET="_top"
 >MySQL
             searchable documentation</A
->.            
+>.
             </P
 ></LI
 ><LI
@@ -251,7 +249,7 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="AEN2118"
+NAME="AEN2217"
 ></A
 >B.2.1.1. Bugzilla Database Tables</H3
 ><P
@@ -322,14 +320,14 @@ CLASS="programlisting"
 ><P
 CLASS="literallayout"
 ><br>
-&nbsp;&nbsp;Here's&nbsp;an&nbsp;overview&nbsp;of&nbsp;what&nbsp;each&nbsp;table&nbsp;does.&nbsp;&nbsp;Most&nbsp;columns&nbsp;in&nbsp;each&nbsp;table&nbsp;have<br>
+&nbsp;&nbsp;Here's&nbsp;an&nbsp;overview&nbsp;of&nbsp;what&nbsp;each&nbsp;table&nbsp;does.&nbsp;Most&nbsp;columns&nbsp;in&nbsp;each&nbsp;table&nbsp;have<br>
 descriptive&nbsp;names&nbsp;that&nbsp;make&nbsp;it&nbsp;fairly&nbsp;trivial&nbsp;to&nbsp;figure&nbsp;out&nbsp;their&nbsp;jobs.<br>
 <br>
-attachments:&nbsp;This&nbsp;table&nbsp;stores&nbsp;all&nbsp;attachments&nbsp;to&nbsp;bugs.&nbsp;&nbsp;It&nbsp;tends&nbsp;to&nbsp;be&nbsp;your<br>
+attachments:&nbsp;This&nbsp;table&nbsp;stores&nbsp;all&nbsp;attachments&nbsp;to&nbsp;bugs.&nbsp;It&nbsp;tends&nbsp;to&nbsp;be&nbsp;your<br>
 largest&nbsp;table,&nbsp;yet&nbsp;also&nbsp;generally&nbsp;has&nbsp;the&nbsp;fewest&nbsp;entries&nbsp;because&nbsp;file<br>
 attachments&nbsp;are&nbsp;so&nbsp;(relatively)&nbsp;large.<br>
 <br>
-bugs:&nbsp;&nbsp;This&nbsp;is&nbsp;the&nbsp;core&nbsp;of&nbsp;your&nbsp;system.&nbsp;&nbsp;The&nbsp;bugs&nbsp;table&nbsp;stores&nbsp;most&nbsp;of&nbsp;the<br>
+bugs:&nbsp;&nbsp;This&nbsp;is&nbsp;the&nbsp;core&nbsp;of&nbsp;your&nbsp;system.&nbsp;The&nbsp;bugs&nbsp;table&nbsp;stores&nbsp;most&nbsp;of&nbsp;the<br>
 current&nbsp;information&nbsp;about&nbsp;a&nbsp;bug,&nbsp;with&nbsp;the&nbsp;exception&nbsp;of&nbsp;the&nbsp;info&nbsp;stored&nbsp;in&nbsp;the<br>
 other&nbsp;tables.<br>
 <br>
@@ -337,26 +335,26 @@ bugs_activity:&nbsp;&nbsp;This&nbsp;stores&nbsp;information&nbsp;regarding&nbsp;
 when&nbsp;--&nbsp;a&nbsp;history&nbsp;file.<br>
 <br>
 cc:&nbsp;&nbsp;This&nbsp;tiny&nbsp;table&nbsp;simply&nbsp;stores&nbsp;all&nbsp;the&nbsp;CC&nbsp;information&nbsp;for&nbsp;any&nbsp;bug&nbsp;which&nbsp;has<br>
-any&nbsp;entries&nbsp;in&nbsp;the&nbsp;CC&nbsp;field&nbsp;of&nbsp;the&nbsp;bug.&nbsp;&nbsp;Note&nbsp;that,&nbsp;like&nbsp;most&nbsp;other&nbsp;tables&nbsp;in<br>
+any&nbsp;entries&nbsp;in&nbsp;the&nbsp;CC&nbsp;field&nbsp;of&nbsp;the&nbsp;bug.&nbsp;Note&nbsp;that,&nbsp;like&nbsp;most&nbsp;other&nbsp;tables&nbsp;in<br>
 Bugzilla,&nbsp;it&nbsp;does&nbsp;not&nbsp;refer&nbsp;to&nbsp;users&nbsp;by&nbsp;their&nbsp;user&nbsp;names,&nbsp;but&nbsp;by&nbsp;their&nbsp;unique<br>
 userid,&nbsp;stored&nbsp;as&nbsp;a&nbsp;primary&nbsp;key&nbsp;in&nbsp;the&nbsp;profiles&nbsp;table.<br>
 <br>
 components:&nbsp;This&nbsp;stores&nbsp;the&nbsp;programs&nbsp;and&nbsp;components&nbsp;(or&nbsp;products&nbsp;and<br>
-components,&nbsp;in&nbsp;newer&nbsp;Bugzilla&nbsp;parlance)&nbsp;for&nbsp;Bugzilla.&nbsp;&nbsp;Curiously,&nbsp;the&nbsp;"program"<br>
+components,&nbsp;in&nbsp;newer&nbsp;Bugzilla&nbsp;parlance)&nbsp;for&nbsp;Bugzilla.&nbsp;Curiously,&nbsp;the&nbsp;"program"<br>
 (product)&nbsp;field&nbsp;is&nbsp;the&nbsp;full&nbsp;name&nbsp;of&nbsp;the&nbsp;product,&nbsp;rather&nbsp;than&nbsp;some&nbsp;other&nbsp;unique<br>
 identifier,&nbsp;like&nbsp;bug_id&nbsp;and&nbsp;user_id&nbsp;are&nbsp;elsewhere&nbsp;in&nbsp;the&nbsp;database.<br>
 <br>
 dependencies:&nbsp;Stores&nbsp;data&nbsp;about&nbsp;those&nbsp;cool&nbsp;dependency&nbsp;trees.<br>
 <br>
-fielddefs:&nbsp;&nbsp;A&nbsp;nifty&nbsp;table&nbsp;that&nbsp;defines&nbsp;other&nbsp;tables.&nbsp;&nbsp;For&nbsp;instance,&nbsp;when&nbsp;you<br>
+fielddefs:&nbsp;&nbsp;A&nbsp;nifty&nbsp;table&nbsp;that&nbsp;defines&nbsp;other&nbsp;tables.&nbsp;For&nbsp;instance,&nbsp;when&nbsp;you<br>
 submit&nbsp;a&nbsp;form&nbsp;that&nbsp;changes&nbsp;the&nbsp;value&nbsp;of&nbsp;"AssignedTo"&nbsp;this&nbsp;table&nbsp;allows<br>
 translation&nbsp;to&nbsp;the&nbsp;actual&nbsp;field&nbsp;name&nbsp;"assigned_to"&nbsp;for&nbsp;entry&nbsp;into&nbsp;MySQL.<br>
 <br>
-groups:&nbsp;&nbsp;defines&nbsp;bitmasks&nbsp;for&nbsp;groups.&nbsp;&nbsp;A&nbsp;bitmask&nbsp;is&nbsp;a&nbsp;number&nbsp;that&nbsp;can&nbsp;uniquely<br>
+groups:&nbsp;&nbsp;defines&nbsp;bitmasks&nbsp;for&nbsp;groups.&nbsp;A&nbsp;bitmask&nbsp;is&nbsp;a&nbsp;number&nbsp;that&nbsp;can&nbsp;uniquely<br>
-identify&nbsp;group&nbsp;memberships.&nbsp;&nbsp;For&nbsp;instance,&nbsp;say&nbsp;the&nbsp;group&nbsp;that&nbsp;is&nbsp;allowed&nbsp;to<br>
+identify&nbsp;group&nbsp;memberships.&nbsp;For&nbsp;instance,&nbsp;say&nbsp;the&nbsp;group&nbsp;that&nbsp;is&nbsp;allowed&nbsp;to<br>
 tweak&nbsp;parameters&nbsp;is&nbsp;assigned&nbsp;a&nbsp;value&nbsp;of&nbsp;"1",&nbsp;the&nbsp;group&nbsp;that&nbsp;is&nbsp;allowed&nbsp;to&nbsp;edit<br>
 users&nbsp;is&nbsp;assigned&nbsp;a&nbsp;"2",&nbsp;and&nbsp;the&nbsp;group&nbsp;that&nbsp;is&nbsp;allowed&nbsp;to&nbsp;create&nbsp;new&nbsp;groups&nbsp;is<br>
-assigned&nbsp;the&nbsp;bitmask&nbsp;of&nbsp;"4".&nbsp;&nbsp;By&nbsp;uniquely&nbsp;combining&nbsp;the&nbsp;group&nbsp;bitmasks&nbsp;(much<br>
+assigned&nbsp;the&nbsp;bitmask&nbsp;of&nbsp;"4".&nbsp;By&nbsp;uniquely&nbsp;combining&nbsp;the&nbsp;group&nbsp;bitmasks&nbsp;(much<br>
 like&nbsp;the&nbsp;chmod&nbsp;command&nbsp;in&nbsp;UNIX,)&nbsp;you&nbsp;can&nbsp;identify&nbsp;a&nbsp;user&nbsp;is&nbsp;allowed&nbsp;to&nbsp;tweak<br>
 parameters&nbsp;and&nbsp;create&nbsp;groups,&nbsp;but&nbsp;not&nbsp;edit&nbsp;users,&nbsp;by&nbsp;giving&nbsp;him&nbsp;a&nbsp;bitmask&nbsp;of<br>
 "5",&nbsp;or&nbsp;a&nbsp;user&nbsp;allowed&nbsp;to&nbsp;edit&nbsp;users&nbsp;and&nbsp;create&nbsp;groups,&nbsp;but&nbsp;not&nbsp;tweak<br>
@@ -371,15 +369,15 @@ keywords:&nbsp;Unlike&nbsp;what&nbsp;you'd&nbsp;think,&nbsp;this&nbsp;table&nbsp
 associated&nbsp;with&nbsp;which&nbsp;bug&nbsp;id's.<br>
 <br>
 logincookies:&nbsp;This&nbsp;stores&nbsp;every&nbsp;login&nbsp;cookie&nbsp;ever&nbsp;assigned&nbsp;to&nbsp;you&nbsp;for&nbsp;every<br>
-machine&nbsp;you've&nbsp;ever&nbsp;logged&nbsp;into&nbsp;Bugzilla&nbsp;from.&nbsp;&nbsp;Curiously,&nbsp;it&nbsp;never&nbsp;does&nbsp;any<br>
+machine&nbsp;you've&nbsp;ever&nbsp;logged&nbsp;into&nbsp;Bugzilla&nbsp;from.&nbsp;Curiously,&nbsp;it&nbsp;never&nbsp;does&nbsp;any<br>
-housecleaning&nbsp;--&nbsp;I&nbsp;see&nbsp;cookies&nbsp;in&nbsp;this&nbsp;file&nbsp;I've&nbsp;not&nbsp;used&nbsp;for&nbsp;months.&nbsp;&nbsp;However,<br>
+housecleaning&nbsp;--&nbsp;I&nbsp;see&nbsp;cookies&nbsp;in&nbsp;this&nbsp;file&nbsp;I've&nbsp;not&nbsp;used&nbsp;for&nbsp;months.&nbsp;However,<br>
 since&nbsp;Bugzilla&nbsp;never&nbsp;expires&nbsp;your&nbsp;cookie&nbsp;(for&nbsp;convenience'&nbsp;sake),&nbsp;it&nbsp;makes<br>
 sense.<br>
 <br>
 longdescs:&nbsp;&nbsp;The&nbsp;meat&nbsp;of&nbsp;bugzilla&nbsp;--&nbsp;here&nbsp;is&nbsp;where&nbsp;all&nbsp;user&nbsp;comments&nbsp;are&nbsp;stored!<br>
 You've&nbsp;only&nbsp;got&nbsp;2^24&nbsp;bytes&nbsp;per&nbsp;comment&nbsp;(it's&nbsp;a&nbsp;mediumtext&nbsp;field),&nbsp;so&nbsp;speak<br>
 sparingly&nbsp;--&nbsp;that's&nbsp;only&nbsp;the&nbsp;amount&nbsp;of&nbsp;space&nbsp;the&nbsp;Old&nbsp;Testament&nbsp;from&nbsp;the&nbsp;Bible<br>
-would&nbsp;take&nbsp;(uncompressed,&nbsp;16&nbsp;megabytes).&nbsp;&nbsp;Each&nbsp;comment&nbsp;is&nbsp;keyed&nbsp;to&nbsp;the<br>
+would&nbsp;take&nbsp;(uncompressed,&nbsp;16&nbsp;megabytes).&nbsp;Each&nbsp;comment&nbsp;is&nbsp;keyed&nbsp;to&nbsp;the<br>
 bug_id&nbsp;to&nbsp;which&nbsp;it's&nbsp;attached,&nbsp;so&nbsp;the&nbsp;order&nbsp;is&nbsp;necessarily&nbsp;chronological,&nbsp;for<br>
 comments&nbsp;are&nbsp;played&nbsp;back&nbsp;in&nbsp;the&nbsp;order&nbsp;in&nbsp;which&nbsp;they&nbsp;are&nbsp;received.<br>
 <br>
@@ -387,12 +385,12 @@ milestones:&nbsp;&nbsp;Interesting&nbsp;that&nbsp;milestones&nbsp;are&nbsp;assoc
 in&nbsp;this&nbsp;table,&nbsp;but&nbsp;Bugzilla&nbsp;does&nbsp;not&nbsp;yet&nbsp;support&nbsp;differing&nbsp;milestones&nbsp;by<br>
 product&nbsp;through&nbsp;the&nbsp;standard&nbsp;configuration&nbsp;interfaces.<br>
 <br>
-namedqueries:&nbsp;&nbsp;This&nbsp;is&nbsp;where&nbsp;everybody&nbsp;stores&nbsp;their&nbsp;"custom&nbsp;queries".&nbsp;&nbsp;Very<br>
+namedqueries:&nbsp;&nbsp;This&nbsp;is&nbsp;where&nbsp;everybody&nbsp;stores&nbsp;their&nbsp;"custom&nbsp;queries".&nbsp;Very<br>
 cool&nbsp;feature;&nbsp;it&nbsp;beats&nbsp;the&nbsp;tar&nbsp;out&nbsp;of&nbsp;having&nbsp;to&nbsp;bookmark&nbsp;each&nbsp;cool&nbsp;query&nbsp;you<br>
 construct.<br>
 <br>
 products:&nbsp;&nbsp;What&nbsp;products&nbsp;you&nbsp;have,&nbsp;whether&nbsp;new&nbsp;bug&nbsp;entries&nbsp;are&nbsp;allowed&nbsp;for&nbsp;the<br>
-product,&nbsp;what&nbsp;milestone&nbsp;you're&nbsp;working&nbsp;toward&nbsp;on&nbsp;that&nbsp;product,&nbsp;votes,&nbsp;etc.&nbsp;&nbsp;It<br>
+product,&nbsp;what&nbsp;milestone&nbsp;you're&nbsp;working&nbsp;toward&nbsp;on&nbsp;that&nbsp;product,&nbsp;votes,&nbsp;etc.&nbsp;It<br>
 will&nbsp;be&nbsp;nice&nbsp;when&nbsp;the&nbsp;components&nbsp;table&nbsp;supports&nbsp;these&nbsp;same&nbsp;features,&nbsp;so&nbsp;you<br>
 could&nbsp;close&nbsp;a&nbsp;particular&nbsp;component&nbsp;for&nbsp;bug&nbsp;entry&nbsp;without&nbsp;having&nbsp;to&nbsp;close&nbsp;an<br>
 entire&nbsp;product...<br>
@@ -427,7 +425,7 @@ mysql&#62;&nbsp;show&nbsp;columns&nbsp;from&nbsp;table;<br>
 mysql&#62;&nbsp;select&nbsp;*&nbsp;from&nbsp;table;<br>
 <br>
 &nbsp;&nbsp;--&nbsp;note:&nbsp;this&nbsp;is&nbsp;a&nbsp;very&nbsp;bad&nbsp;idea&nbsp;to&nbsp;do&nbsp;on,&nbsp;for&nbsp;instance,&nbsp;the&nbsp;"bugs"&nbsp;table&nbsp;if<br>
-you&nbsp;have&nbsp;50,000&nbsp;bugs.&nbsp;&nbsp;You'll&nbsp;be&nbsp;sitting&nbsp;there&nbsp;a&nbsp;while&nbsp;until&nbsp;you&nbsp;ctrl-c&nbsp;or<br>
+you&nbsp;have&nbsp;50,000&nbsp;bugs.&nbsp;You'll&nbsp;be&nbsp;sitting&nbsp;there&nbsp;a&nbsp;while&nbsp;until&nbsp;you&nbsp;ctrl-c&nbsp;or<br>
 50,000&nbsp;bugs&nbsp;play&nbsp;across&nbsp;your&nbsp;screen.<br>
 <br>
 &nbsp;&nbsp;You&nbsp;can&nbsp;limit&nbsp;the&nbsp;display&nbsp;from&nbsp;above&nbsp;a&nbsp;little&nbsp;with&nbsp;the&nbsp;command,&nbsp;where<br>
@@ -440,7 +438,7 @@ mysql&#62;&nbsp;select&nbsp;*&nbsp;from&nbsp;table&nbsp;where&nbsp;(column&nbsp;
 mysql&#62;&nbsp;select&nbsp;*&nbsp;from&nbsp;table&nbsp;where&nbsp;(column&nbsp;!=&nbsp;"some&nbsp;info");<br>
 <br>
 &nbsp;&nbsp;Let's&nbsp;take&nbsp;our&nbsp;example&nbsp;from&nbsp;the&nbsp;introduction,&nbsp;and&nbsp;assume&nbsp;you&nbsp;need&nbsp;to&nbsp;change<br>
-the&nbsp;word&nbsp;"verified"&nbsp;to&nbsp;"approved"&nbsp;in&nbsp;the&nbsp;resolution&nbsp;field.&nbsp;&nbsp;We&nbsp;know&nbsp;from&nbsp;the<br>
+the&nbsp;word&nbsp;"verified"&nbsp;to&nbsp;"approved"&nbsp;in&nbsp;the&nbsp;resolution&nbsp;field.&nbsp;We&nbsp;know&nbsp;from&nbsp;the<br>
 above&nbsp;information&nbsp;that&nbsp;the&nbsp;resolution&nbsp;is&nbsp;likely&nbsp;to&nbsp;be&nbsp;stored&nbsp;in&nbsp;the&nbsp;"bugs"<br>
 table.&nbsp;Note&nbsp;we'll&nbsp;need&nbsp;to&nbsp;change&nbsp;a&nbsp;little&nbsp;perl&nbsp;code&nbsp;as&nbsp;well&nbsp;as&nbsp;this&nbsp;database<br>
 change,&nbsp;but&nbsp;I&nbsp;won't&nbsp;plunge&nbsp;into&nbsp;that&nbsp;in&nbsp;this&nbsp;document.&nbsp;Let's&nbsp;verify&nbsp;the<br>
@@ -451,10 +449,10 @@ mysql&#62;&nbsp;show&nbsp;columns&nbsp;from&nbsp;bugs<br>
 &nbsp;&nbsp;(exceedingly&nbsp;long&nbsp;output&nbsp;truncated&nbsp;here)<br>
 |&nbsp;bug_status|&nbsp;enum('UNCONFIRMED','NEW','ASSIGNED','REOPENED','RESOLVED','VERIFIED','CLOSED')||MUL&nbsp;|&nbsp;UNCONFIRMED||<br>
 <br>
-&nbsp;&nbsp;Sorry&nbsp;about&nbsp;that&nbsp;long&nbsp;line.&nbsp;&nbsp;We&nbsp;see&nbsp;from&nbsp;this&nbsp;that&nbsp;the&nbsp;"bug&nbsp;status"&nbsp;column&nbsp;is<br>
+&nbsp;&nbsp;Sorry&nbsp;about&nbsp;that&nbsp;long&nbsp;line.&nbsp;We&nbsp;see&nbsp;from&nbsp;this&nbsp;that&nbsp;the&nbsp;"bug&nbsp;status"&nbsp;column&nbsp;is<br>
 an&nbsp;"enum&nbsp;field",&nbsp;which&nbsp;is&nbsp;a&nbsp;MySQL&nbsp;peculiarity&nbsp;where&nbsp;a&nbsp;string&nbsp;type&nbsp;field&nbsp;can<br>
-only&nbsp;have&nbsp;certain&nbsp;types&nbsp;of&nbsp;entries.&nbsp;&nbsp;While&nbsp;I&nbsp;think&nbsp;this&nbsp;is&nbsp;very&nbsp;cool,&nbsp;it's&nbsp;not<br>
+only&nbsp;have&nbsp;certain&nbsp;types&nbsp;of&nbsp;entries.&nbsp;While&nbsp;I&nbsp;think&nbsp;this&nbsp;is&nbsp;very&nbsp;cool,&nbsp;it's&nbsp;not<br>
-standard&nbsp;SQL.&nbsp;&nbsp;Anyway,&nbsp;we&nbsp;need&nbsp;to&nbsp;add&nbsp;the&nbsp;possible&nbsp;enum&nbsp;field&nbsp;entry<br>
+standard&nbsp;SQL.&nbsp;Anyway,&nbsp;we&nbsp;need&nbsp;to&nbsp;add&nbsp;the&nbsp;possible&nbsp;enum&nbsp;field&nbsp;entry<br>
 'APPROVED'&nbsp;by&nbsp;altering&nbsp;the&nbsp;"bugs"&nbsp;table.<br>
 <br>
 mysql&#62;&nbsp;ALTER&nbsp;table&nbsp;bugs&nbsp;CHANGE&nbsp;bug_status&nbsp;bug_status<br>
@@ -470,15 +468,15 @@ mysql&#62;&nbsp;show&nbsp;columns&nbsp;from&nbsp;bugs;<br>
 <br>
 &nbsp;&nbsp;you'll&nbsp;see&nbsp;that&nbsp;the&nbsp;bug_status&nbsp;field&nbsp;has&nbsp;an&nbsp;extra&nbsp;"APPROVED"&nbsp;enum&nbsp;that's<br>
 available!&nbsp;&nbsp;Cool&nbsp;thing,&nbsp;too,&nbsp;is&nbsp;that&nbsp;this&nbsp;is&nbsp;reflected&nbsp;on&nbsp;your&nbsp;query&nbsp;page&nbsp;as<br>
-well&nbsp;--&nbsp;you&nbsp;can&nbsp;query&nbsp;by&nbsp;the&nbsp;new&nbsp;status.&nbsp;&nbsp;But&nbsp;how's&nbsp;it&nbsp;fit&nbsp;into&nbsp;the&nbsp;existing<br>
+well&nbsp;--&nbsp;you&nbsp;can&nbsp;query&nbsp;by&nbsp;the&nbsp;new&nbsp;status.&nbsp;But&nbsp;how's&nbsp;it&nbsp;fit&nbsp;into&nbsp;the&nbsp;existing<br>
 scheme&nbsp;of&nbsp;things?<br>
 &nbsp;&nbsp;Looks&nbsp;like&nbsp;you&nbsp;need&nbsp;to&nbsp;go&nbsp;back&nbsp;and&nbsp;look&nbsp;for&nbsp;instances&nbsp;of&nbsp;the&nbsp;word&nbsp;"verified"<br>
 in&nbsp;the&nbsp;perl&nbsp;code&nbsp;for&nbsp;Bugzilla&nbsp;--&nbsp;wherever&nbsp;you&nbsp;find&nbsp;"verified",&nbsp;change&nbsp;it&nbsp;to<br>
 "approved"&nbsp;and&nbsp;you're&nbsp;in&nbsp;business&nbsp;(make&nbsp;sure&nbsp;that's&nbsp;a&nbsp;case-insensitive&nbsp;search).<br>
 Although&nbsp;you&nbsp;can&nbsp;query&nbsp;by&nbsp;the&nbsp;enum&nbsp;field,&nbsp;you&nbsp;can't&nbsp;give&nbsp;something&nbsp;a&nbsp;status<br>
-of&nbsp;"APPROVED"&nbsp;until&nbsp;you&nbsp;make&nbsp;the&nbsp;perl&nbsp;changes.&nbsp;&nbsp;&nbsp;Note&nbsp;that&nbsp;this&nbsp;change&nbsp;I<br>
+of&nbsp;"APPROVED"&nbsp;until&nbsp;you&nbsp;make&nbsp;the&nbsp;perl&nbsp;changes.&nbsp;Note&nbsp;that&nbsp;this&nbsp;change&nbsp;I<br>
 mentioned&nbsp;can&nbsp;also&nbsp;be&nbsp;done&nbsp;by&nbsp;editing&nbsp;checksetup.pl,&nbsp;which&nbsp;automates&nbsp;a&nbsp;lot&nbsp;of<br>
-this.&nbsp;&nbsp;But&nbsp;you&nbsp;need&nbsp;to&nbsp;know&nbsp;this&nbsp;stuff&nbsp;anyway,&nbsp;right?<br>
+this.&nbsp;But&nbsp;you&nbsp;need&nbsp;to&nbsp;know&nbsp;this&nbsp;stuff&nbsp;anyway,&nbsp;right?<br>
 	</P
 ></DIV
 ></DIV

webtools/bugzilla/docs/html/disclaimer.html

@@ -87,15 +87,15 @@ NAME="disclaimer"
     </P
 ><P
 >&#13;      All copyrights are held by their respective owners, unless
-      specifically noted otherwise.  Use of a term in this document
+      specifically noted otherwise. Use of a term in this document
       should not be regarded as affecting the validity of any
       trademark or service mark.
     </P
 ><P
 >&#13;      Naming of particular products or brands should not be seen as
-      endorsements, with the exception of the term "GNU/Linux".  We
+      endorsements, with the exception of the term "GNU/Linux". We
       wholeheartedly endorse the use of GNU/Linux in every situation
-      where it is appropriate.  It is an extremely versatile, stable,
+      where it is appropriate. It is an extremely versatile, stable,
       and robust operating system that offers an ideal operating
       environment for Bugzilla.
     </P
@@ -110,10 +110,10 @@ NAME="disclaimer"
       documented or fixed in the code, security holes surely exist.
       Great care should be taken both in the installation and usage of
       this software. Carefully consider the implications of installing
-      other network services with Bugzilla.  The Bugzilla development
+      other network services with Bugzilla. The Bugzilla development
       team members, Netscape Communications, America Online Inc., and
       any affiliated developers or sponsors assume no liability for
-      your use of this product.  You have the source code to this
+      your use of this product. You have the source code to this
       product, and are responsible for auditing it yourself to ensure
       your security needs are met.
     </P

webtools/bugzilla/docs/html/extraconfig.html

@@ -81,7 +81,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN687"
+NAME="AEN786"
 ></A
 >4.2.1. Dependency Charts</H2
 ><P
@@ -145,7 +145,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN702"
+NAME="AEN801"
 ></A
 >4.2.2. Bug Graphs</H2
 ><P
@@ -204,7 +204,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN715"
+NAME="AEN814"
 ></A
 >4.2.3. The Whining Cron</H2
 ><P
@@ -386,13 +386,13 @@ HREF="http://www.openldap.org/"
 TARGET="_top"
 >&#13;      OpenLDAP</A
 > with Bugzilla, using any of a number of administration
-      tools.  You should apply the patch attached this bug:
+      tools.  You should apply the patch attached to 
       <A
 HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=158630"
 TARGET="_top"
->&#13;      http://bugzilla.mozilla.org/show_bug.cgi?id=158630</A
+>bug 158630</A
->, then set
+>
-      the following object classes for your users:
+      , then set the following object classes for your users:
 
       <P
 ></P
@@ -450,7 +450,7 @@ NAME="content-type"
       <A
 HREF="http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3"
 TARGET="_top"
->&#13;      http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3</A
+>http://www.cet.org/tech_tips/malicious_code_mitigation.html/#3</A
 >.
       Executing the following code snippet from a UNIX command shell will
       rectify the problem if your Bugzilla installation is intended for an
@@ -523,13 +523,13 @@ VALIGN="TOP"
 ><P
 >Using &#60;meta&#62; tags to set the charset is not
         recommended, as there's a bug in Netscape 4.x which causes pages
-        marked up in this way to load twice. See 
+        marked up in this way to load twice. See  
         <A
 HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=126266"
 TARGET="_top"
->bug
+>bug 126266</A
-        126266</A
+>
-> for more information including progress toward making
+        for more information including progress toward making
         bugzilla charset aware by default.
         </P
 ></TD
@@ -610,7 +610,7 @@ CLASS="filename"
 HREF="http://www.snert.com/Software/mod_throttle/"
 TARGET="_top"
 >http://www.snert.com/Software/mod_throttle/</A
->
+>.
       Follow the instructions to install into your Apache install. 
       <EM
 >This module only functions with the Apache web

webtools/bugzilla/docs/html/faq.html

@@ -497,7 +497,7 @@ HREF="faq.html#faq-use-changeaddress"
 ><DT
 >A.7.2. <A
 HREF="faq.html#faq-use-query"
->&#13;	    The query page is very confusing.  Isn't there a simpler way to query?
+>&#13;	    The query page is very confusing. Isn't there a simpler way to query?
 	  </A
 ></DT
 ><DT
@@ -511,7 +511,7 @@ HREF="faq.html#faq-use-accept"
 >A.7.4. <A
 HREF="faq.html#faq-use-attachment"
 >&#13;	    I can't upload anything into the database via the "Create Attachment"
-	    link.  What am I doing wrong?
+	    link. What am I doing wrong?
 	  </A
 ></DT
 ><DT
@@ -587,8 +587,8 @@ CLASS="answer"
 	    information at <A
 HREF="http://www.bugzilla.org/"
 TARGET="_top"
->&#13;	    http://www.bugzilla.org/</A
+>http://www.bugzilla.org/</A
->
+>.
 	  </P
 ></DIV
 ></DIV
@@ -616,8 +616,8 @@ CLASS="answer"
 	    See details at <A
 HREF="http://www.mozilla.org/MPL/"
 TARGET="_top"
->&#13;	    http://www.mozilla.org/MPL/</A
+>http://www.mozilla.org/MPL/</A
->
+>.
 	  </P
 ></DIV
 ></DIV
@@ -653,7 +653,7 @@ TARGET="_top"
 >&#13;	    <A
 HREF="http://www.collab.net/"
 TARGET="_top"
->www.collab.net</A
+>http://www.collab.net/</A
 > offers
 	    Bugzilla as part of their standard offering to large projects.
 	    They do have some minimum fees that are pretty hefty, and generally
@@ -691,7 +691,7 @@ CLASS="answer"
 	    There are <EM
 >dozens</EM
 > of major companies with public
-	    Bugzilla sites to track bugs in their products.  A few include:
+	    Bugzilla sites to track bugs in their products. A few include:
 	    <P
 ></P
 ><TABLE
@@ -799,7 +799,7 @@ HREF="http://www.bugzilla.org/who_we_are.html"
 TARGET="_top"
 >core team</A
 >,
-      led by Dave Miller (justdave@netscape.com).      
+      led by Dave Miller (justdave@netscape.com).
 	  </P
 ></DIV
 ></DIV
@@ -863,8 +863,8 @@ CLASS="answer"
 > </B
 >
 	    It may be that the support has not been built yet, or that you
-	    have not yet found it.  Bugzilla is making tremendous strides in
+	    have not yet found it. Bugzilla is making tremendous strides in
-	    usability, customizability, scalability, and user interface.  It
+	    usability, customizability, scalability, and user interface. It
 	    is widely considered the most complete and popular open-source
 	    bug-tracking software in existence.
 	  </P
@@ -907,16 +907,16 @@ CLASS="answer"
 	  </P
 ><P
 >&#13;            There is currently work in progress to make Bugzilla work on
-            PostgreSQL and Sybase in the default distribution.  You can track
+            PostgreSQL and Sybase in the default distribution. You can track
-            the progress of these initiatives in bugs <A
+            the progress of these initiatives in <A
 HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304"
 TARGET="_top"
->98304</A
+>bug 98304</A
 >
             and <A
 HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=173130"
 TARGET="_top"
->173130</A
+>bug 173130</A
 >
             respectively.
           </P
@@ -956,11 +956,11 @@ CLASS="filename"
 > because when
             Terry first started writing the code for mozilla.org he needed a
             version of Perl and other tools that were completely under his
-            control.  This location was abandoned for the 2.18 release in favor
+            control. This location was abandoned for the 2.18 release in favor
             of the more sensible <TT
 CLASS="filename"
 >/usr/bin/perl</TT
->.  If you
+>. If you
             installed an older verion of Bugzilla and created the symlink we
             suggested, you can remove it now (provided that you don't have
             anything else, such as Bonsai, using it and you don't intend to
@@ -993,7 +993,7 @@ CLASS="answer"
 > </B
 >
             Yes, the following bit of perl magic will change all the shebang
-            lines.  Be sure to change <TT
+            lines. Be sure to change <TT
 CLASS="filename"
 >/usr/local/bin/perl</TT
 >
@@ -1100,7 +1100,7 @@ CLASS="answer"
 ><B
 > </B
 >
-	    It is web and e-mail based.  You can edit bugs by sending specially
+	    It is web and e-mail based. You can edit bugs by sending specially
 	    formatted email to a properly configured Bugzilla, or control via the web.
 	  </P
 ></DIV
@@ -1203,7 +1203,7 @@ CLASS="answer"
 > </B
 >
 	    Yes - any sort of attachment is allowed, although administrators can
-      configure a maximum size.  
+      configure a maximum size.
             Bugzilla gives the user the option of either using the MIME-type
             supplied by the browser, choosing from a pre-defined list or
             manually typing any arbitrary MIME-type. 
@@ -1232,17 +1232,17 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Yes.  However, modifying some fields, notably those related to bug
+	    Yes. However, modifying some fields, notably those related to bug
 	    progression states, also require adjusting the program logic to
 	    compensate for the change.
 	  </P
 ><P
 >&#13;	    There is no GUI for adding fields to Bugzilla at this
-	    time.  You can follow development of this feature at
+	    time. You can follow development of this feature in 
 	    <A
 HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=91037"
 TARGET="_top"
->http://bugzilla.mozilla.org/show_bug.cgi?id=91037</A
+>bug 91037</A
 >
 	  </P
 ></DIV
@@ -1268,12 +1268,12 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Yes.  Look at <A
+	    Yes. Look at <A
 HREF="http://bugzilla.mozilla.org/report.cgi"
 TARGET="_top"
->&#13;	    http://bugzilla.mozilla.org/report.cgi</A
+>http://bugzilla.mozilla.org/report.cgi</A
-> for samples of what
+>
-            Bugzilla can do in reporting and graphing.
+            for samples of what Bugzilla can do in reporting and graphing.
 	  </P
 ><P
 >&#13;            If you can not get the reports you want from the included reporting
@@ -1306,7 +1306,7 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Email notification is user-configurable.  By default, the bug id and 
+	    Email notification is user-configurable. By default, the bug id and 
       Summary of the bug report accompany each email notification, along with
 	    a list of the changes made.
 	  </P
@@ -1384,7 +1384,7 @@ VALIGN="TOP"
 >&#13;		If you decide to use the bugzilla_email integration features
 		to allow Bugzilla to record responses to mail with the associated bug,
 		you may need to caution your users to set their mailer to "respond
-		to messages in the format in which they were sent".  For security reasons
+		to messages in the format in which they were sent". For security reasons
 		Bugzilla ignores HTML tags in comments, and if a user sends HTML-based
 		email into Bugzilla the resulting comment looks downright awful.
 	      </P
@@ -1421,7 +1421,7 @@ CLASS="answer"
 >
             Bugzilla can output buglists as HTML (the default), CSV or RDF.
             The link for CSV can be found at the bottom of the buglist in HTML
-            format.  This CSV format can easily be imported into MS Excel or
+            format. This CSV format can easily be imported into MS Excel or
             other spread-sheet applications.
           </P
 ><P
@@ -1429,7 +1429,7 @@ CLASS="answer"
             <TT
 CLASS="computeroutput"
 >&#38;ctype=rdf</TT
-> to the URL.  RDF
+> to the URL. RDF
             is meant to be machine readable and thus it is assumed that the
             URL would be generated progmatically so there is no user visible
             link to this format.
@@ -1479,15 +1479,15 @@ CLASS="answer"
 ><B
 > </B
 >
-            Yes.  For more information including available translated templates,
+            Yes. For more information including available translated templates,
             see <A
 HREF="http://www.bugzilla.org/download.html#localizations"
 TARGET="_top"
 >http://www.bugzilla.org/download.html#localizations</A
 >.
             The admin interfaces are still not included in these translated
-            templates and is therefore still English only.  Also, there may be
+            templates and is therefore still English only. Also, there may be
-            issues with the charset not being declared.  See <A
+            issues with the charset not being declared. See <A
 HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=126266"
 TARGET="_top"
 >bug 126226</A
@@ -1517,7 +1517,7 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Yes.  No.  Yes (using the CSV format).
+	    Yes. No. Yes (using the CSV format).
 	  </P
 ></DIV
 ></DIV
@@ -1542,7 +1542,7 @@ CLASS="answer"
 ><B
 > </B
 >
-	    You have no idea.  Bugzilla's query interface, particularly with the
+	    You have no idea. Bugzilla's query interface, particularly with the
 	    advanced Boolean operators, is incredibly versatile.
 	  </P
 ></DIV
@@ -1569,7 +1569,7 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Bugzilla does not lock records.  It provides mid-air collision detection,
+	    Bugzilla does not lock records. It provides mid-air collision detection,
 	    and offers the offending user a choice of options to deal with the conflict.
 	  </P
 ></DIV
@@ -1599,8 +1599,8 @@ CLASS="answer"
 	    at <A
 HREF="http://www.mysql.com/doc/B/a/Backup.html"
 TARGET="_top"
->&#13;	    http://www.mysql.com/doc/B/a/Backup.html</A
+>http://www.mysql.com/doc/B/a/Backup.html</A
->
+>.
 	  </P
 ></DIV
 ></DIV
@@ -1624,8 +1624,8 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Yes.  However, commits to the database must wait
+	    Yes. However, commits to the database must wait
-	    until the tables are unlocked.  Bugzilla databases are typically
+	    until the tables are unlocked. Bugzilla databases are typically
 	    very small, and backups routinely take less than a minute.
 	  </P
 ></DIV
@@ -1659,7 +1659,7 @@ CLASS="answer"
 	  </P
 ><P
 >&#13;	    Commercial Bug-tracking software typically costs somewhere upwards
-	    of $20,000 or more for 5-10 floating licenses.  Bugzilla consultation
+	    of $20,000 or more for 5-10 floating licenses. Bugzilla consultation
 	    is available from skilled members of the newsgroup. Simple questions
       are answered there and then.
 	  </P
@@ -1689,9 +1689,9 @@ CLASS="answer"
 ><B
 > </B
 >
-	    It all depends on your level of commitment.  Someone with much Bugzilla
+	    It all depends on your level of commitment. Someone with much Bugzilla
 	    experience can get you up and running in less than a day, and
-	    your Bugzilla install can run untended for years.  If your
+	    your Bugzilla install can run untended for years. If your
 	    Bugzilla strategy is critical to your business workflow, hire somebody
 	    with reasonable UNIX or Perl skills to handle your process management and
 	    bug-tracking maintenance &#38; customization.
@@ -1719,7 +1719,7 @@ CLASS="answer"
 ><B
 > </B
 >
-	    No.  MySQL asks, if you find their product valuable, that you purchase
+	    No. MySQL asks, if you find their product valuable, that you purchase
 	    a support contract from them that suits your needs.
 	  </P
 ></DIV
@@ -1753,7 +1753,7 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Run MySQL like this: "mysqld --skip-grant-tables".  Please remember <EM
+	    Run MySQL like this: "mysqld --skip-grant-tables". Please remember <EM
 >this
 	    makes MySQL as secure as taping a $100 to the floor of a football stadium
 	    bathroom for safekeeping.</EM
@@ -1902,11 +1902,11 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Try Klaas Freitag's excellent patch for "whineatassigned" functionality.
+	    Try Klaas Freitag's excellent patch for "whineatassigned"
-	    You can find it at <A
+            functionality. You can find it in <A
 HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=6679"
 TARGET="_top"
->http://bugzilla.mozilla.org/show_bug.cgi?id=6679</A
+>bug 6679</A
 >. This
 	    patch is against an older version of Bugzilla, so you must apply
 	    the diffs manually.
@@ -1938,7 +1938,7 @@ CLASS="answer"
 	    You can call bug_email.pl directly from your aliases file, with
 	    an entry like this:
 	    <A
-NAME="AEN1886"
+NAME="AEN1985"
 ></A
 ><BLOCKQUOTE
 CLASS="BLOCKQUOTE"
@@ -1949,7 +1949,7 @@ CLASS="BLOCKQUOTE"
 >
 	    However, this is fairly nasty and subject to problems; you also
 	    need to set up your smrsh (sendmail restricted shell) to allow
-	    it.  In a pinch, though, it can work.
+	    it. In a pinch, though, it can work.
 	  </P
 ></DIV
 ></DIV
@@ -2066,7 +2066,7 @@ CLASS="answer"
 	  </P
 ><P
 >&#13;	    If you never receive mail from Bugzilla, chances you do not have
-	    sendmail in "/usr/lib/sendmail".  Ensure sendmail lives in, or is symlinked
+	    sendmail in "/usr/lib/sendmail". Ensure sendmail lives in, or is symlinked
 	    to, "/usr/lib/sendmail".
 	  </P
 ></DIV
@@ -2101,7 +2101,7 @@ CLASS="answer"
 >
             Red Hat's old version of Bugzilla (based on 2.8) worked on Oracle.
             Red Hat's newer version (based on 2.17.1 and soon to be merged into
-            the main distribution) runs on PostgreSQL.  At this time we know of
+            the main distribution) runs on PostgreSQL. At this time we know of
             no recent ports of Bugzilla to Oracle but do intend to support it
             in the future (possibly the 2.20 time-frame).
 	  </P
@@ -2140,15 +2140,15 @@ CLASS="filename"
 	    it finishes without errors, you're
 	    <EM
 >probably</EM
-> OK.  If it doesn't come back
+> OK. If it doesn't come back
 	    OK (i.e. any red letters), there are certain things
-	    Bugzilla can recover from and certain things it can't.  If
+	    Bugzilla can recover from and certain things it can't. If
 	    it can't auto-recover, I hope you're familiar with
 	    mysqladmin commands or have installed another way to
-	    manage your database.  Sanity Check, although it is a good
+	    manage your database. Sanity Check, although it is a good
 	    basic check on your database integrity, by no means is a
 	    substitute for competent database administration and
-	    avoiding deletion of data.  It is not exhaustive, and was
+	    avoiding deletion of data. It is not exhaustive, and was
 	    created to do a basic check for the most common problems
 	    in Bugzilla databases.
 	  </P
@@ -2181,7 +2181,7 @@ CLASS="command"
 >mysql</B
 >
             command line utility to manually insert, delete and modify table
-            information.  There are also more intuitive GUI clients available.
+            information. There are also more intuitive GUI clients available.
             Personal favorites of the Bugzilla team are <A
 HREF="http://www.phpmyadmin.net/"
 TARGET="_top"
@@ -2277,7 +2277,7 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Well, you can synchronize or you can move bugs.  Synchronization will
+	    Well, you can synchronize or you can move bugs. Synchronization will
 	    only work one way -- you can create a read-only copy of the database
 	    at one site, and have it regularly updated at intervals from the main
 	    database.
@@ -2347,8 +2347,8 @@ CLASS="answer"
 ><B
 > </B
 >
-	    Not currently.  Bundle::Bugzilla enormously simplifies Bugzilla
+	    Not currently. Bundle::Bugzilla enormously simplifies Bugzilla
-	    installation on UNIX systems.  If someone can volunteer to
+	    installation on UNIX systems. If someone can volunteer to
 	    create a suitable PPM bundle for Win32, it would be appreciated.
 	  </P
 ></DIV
@@ -2382,7 +2382,7 @@ CLASS="answer"
 ><P
 >&#13;	    Microsoft has some advice on this matter, as well:
 	    <A
-NAME="AEN1969"
+NAME="AEN2068"
 ></A
 ><BLOCKQUOTE
 CLASS="BLOCKQUOTE"
@@ -2463,10 +2463,10 @@ CLASS="command"
 	    I reckon TimeDate and Data::Dumper come with the activeperl. You can check
 	    the ActiveState site for packages for installation through PPM.
 	    <A
-HREF=" http://www.activestate.com/Packages/"
+HREF="http://www.activestate.com/Packages/"
 TARGET="_top"
->&#13;	      http://www.activestate.com/Packages/</A
+>http://www.activestate.com/Packages/</A
->
+>.
 	  </P
 ></DIV
 ></DIV
@@ -2514,7 +2514,7 @@ NAME="faq-use-query"
 ><B
 >A.7.2. </B
 >
-	    The query page is very confusing.  Isn't there a simpler way to query?
+	    The query page is very confusing. Isn't there a simpler way to query?
 	  </P
 ></DIV
 ><DIV
@@ -2551,8 +2551,7 @@ CLASS="answer"
 > </B
 >
 	    The current behavior is acceptable to bugzilla.mozilla.org and most
-	    users.  You have your choice of patches
+	    users. You have your choice of patches to change this behavior, however.
-	    to change this behavior, however.
 	    <P
 ></P
 ><TABLE
@@ -2579,8 +2578,8 @@ TARGET="_top"
 ><P
 ></P
 >
-	    Note that these patches are somewhat dated.  You will need to apply
+	    Note that these patches are somewhat dated. You will need to apply
-      them manually.  
+      them manually.
 	  </P
 ></DIV
 ></DIV
@@ -2596,7 +2595,7 @@ NAME="faq-use-attachment"
 >A.7.4. </B
 >
 	    I can't upload anything into the database via the "Create Attachment"
-	    link.  What am I doing wrong?
+	    link. What am I doing wrong?
 	  </P
 ></DIV
 ><DIV
@@ -2606,7 +2605,7 @@ CLASS="answer"
 > </B
 >
 	    The most likely cause is a very old browser or a browser that is
-	    incompatible with file upload via POST.  Download the latest Netscape,
+	    incompatible with file upload via POST. Download the latest Netscape,
 	    Microsoft, or Mozilla browser to handle uploads correctly.
 	  </P
 ></DIV
@@ -2632,8 +2631,8 @@ CLASS="answer"
 > </B
 >
 	    In the Bugzilla administrator UI, edit the keyword and it will let you
-	    replace the old keyword name with a new one.  This will cause a problem
+	    replace the old keyword name with a new one. This will cause a problem
-	    with the keyword cache.  Run sanitycheck.cgi to fix it.
+	    with the keyword cache. Run sanitycheck.cgi to fix it.
 	  </P
 ></DIV
 ></DIV
@@ -2666,7 +2665,7 @@ CLASS="answer"
 > </B
 >
 	    Gerv and Myk suggest a 2-space indent, with embedded code sections on
-	    their own line, in line with outer tags.  Like this:</P
+	    their own line, in line with outer tags. Like this:</P
 ><TABLE
 BORDER="0"
 BGCOLOR="#E0E0E0"
@@ -2701,7 +2700,7 @@ CLASS="programlisting"
 ><P
 >Please note that many have differing opinions on this subject,
 	and the existing templates in Bugzilla espouse both this and a 4-space
-	style.  Either is acceptable; the above is preferred.</P
+	style. Either is acceptable; the above is preferred.</P
 ></DIV
 ></DIV
 ><DIV
@@ -2739,7 +2738,7 @@ TARGET="_top"
 >here</A
 >.
 	    This list includes bugs for the 2.18 release that have already
-	    been fixed and checked into CVS.  Please consult the
+	    been fixed and checked into CVS. Please consult the
 	    <A
 HREF="http://www.bugzilla.org/"
 TARGET="_top"
@@ -2771,14 +2770,13 @@ CLASS="answer"
 ><B
 > </B
 >
-	    This is well-documented here: <A
+	    This is well-documented in <A
 HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=49862"
 TARGET="_top"
->&#13;	    http://bugzilla.mozilla.org/show_bug.cgi?id=49862</A
+>&#13;	    bug 49862</A
->.  Ultimately, it's as easy
+>. Ultimately, it's as easy as adding the "---" priority field to your
-	    as adding the "---" priority field to your localconfig file in the appropriate area,
+            localconfig file in the appropriate area, re-running checksetup.pl, and then changing the
-	    re-running checksetup.pl, and then changing the default priority in your browser using
+            default priority in your browser using "editparams.cgi". 
-	    "editparams.cgi". 
 	  </P
 ></DIV
 ></DIV
@@ -2827,7 +2825,7 @@ TARGET="_top"
 		  or new source file by clicking
 		  "Create a new attachment" link on the bug page you've just created, and
 		  include any descriptions of database changes you may make, into the bug
-		  ID you submitted in step #1.  Be sure and click the "Patch" checkbox
+		  ID you submitted in step #1. Be sure and click the "Patch" checkbox
 		  to indicate the text you are sending is a patch!
 		</P
 ></LI
@@ -2835,7 +2833,7 @@ TARGET="_top"
 ><P
 >&#13;		  Announce your patch and the associated URL
 		  (http://bugzilla.mozilla.org/show_bug.cgi?id=XXXXXX) for discussion in
-		  the newsgroup (netscape.public.mozilla.webtools).  You'll get a really
+		  the newsgroup (netscape.public.mozilla.webtools). You'll get a really
 		  good, fairly immediate reaction to the implications of your patch,
 		  which will also give us an idea how well-received the change would
 		  be.

webtools/bugzilla/docs/html/gfdl-10.html

@@ -84,10 +84,8 @@ NAME="gfdl-10"
     <A
 HREF="http://www.gnu.org/copyleft/"
 TARGET="_top"
->&#13;    http://www.gnu.org/copyleft/</A
+>http://www.gnu.org/copyleft/</A
->
+>.</P
-
-    .</P
 ><P
 >Each version of the License is given a distinguishing version
     number. If the Document specifies that a particular numbered version of

webtools/bugzilla/docs/html/gfdl-howto.html

@@ -81,7 +81,7 @@ NAME="gfdl-howto"
     of the License in the document and put the following copyright and
     license notices just after the title page:</P
 ><A
-NAME="AEN2296"
+NAME="AEN2395"
 ></A
 ><BLOCKQUOTE
 CLASS="BLOCKQUOTE"

webtools/bugzilla/docs/html/gfdl.html

@@ -144,7 +144,7 @@ HREF="gfdl-howto.html"
 ><P
 >Version 1.1, March 2000</P
 ><A
-NAME="AEN2206"
+NAME="AEN2305"
 ></A
 ><BLOCKQUOTE
 CLASS="BLOCKQUOTE"

webtools/bugzilla/docs/html/glossary.html

@@ -70,7 +70,7 @@ CLASS="glossdiv"
 ><H1
 CLASS="glossdiv"
 ><A
-NAME="AEN2301"
+NAME="AEN2400"
 ></A
 >0-9, high ascii</H1
 ><DL
@@ -353,13 +353,9 @@ NAME="gloss-component"
 NAME="gloss-cpan"
 ></A
 ><B
->&#13;        <SPAN
+>Comprehensive Perl Archive Network</B
-CLASS="acronym"
->CPAN</SPAN
->
-      </B
 ></DT
-><DD
+> (CPAN)<DD
 ><P
 >&#13;        <SPAN
 CLASS="acronym"
@@ -600,6 +596,22 @@ NAME="gloss-p"
 >P</H1
 ><DL
 ><DT
+><A
+NAME="gloss-ppm"
+></A
+><B
+>Perl Package Manager</B
+></DT
+> (PPM)<DD
+><P
+><A
+HREF="http://aspn.activestate.com/ASPN/Downloads/ActivePerl/PPM/"
+TARGET="_top"
+>http://aspn.activestate.com/ASPN/Downloads/ActivePerl/PPM/</A
+>
+        </P
+></DD
+><DT
 ><B
 >Product</B
 ></DT
@@ -866,7 +878,7 @@ NAME="gloss-zarro"
         Terry had the following to say:
         </P
 ><A
-NAME="AEN2521"
+NAME="AEN2626"
 ></A
 ><TABLE
 BORDER="0"

webtools/bugzilla/docs/html/hintsandtips.html

@@ -84,7 +84,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN370"
+NAME="AEN371"
 ></A
 >3.2.1. Autolinkification</H2
 ><P
@@ -232,7 +232,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN399"
+NAME="AEN400"
 ></A
 >3.2.5. Filing Bugs</H2
 ><P

webtools/bugzilla/docs/html/how.html

@@ -105,8 +105,8 @@ NAME="myaccount"
       <A
 HREF="http://landfill.bugzilla.org/bugzilla-tip/"
 TARGET="_top"
->&#13;      http://landfill.bugzilla.org/bugzilla-tip/</A
+>http://landfill.bugzilla.org/bugzilla-tip/</A
->
+>.
       </P
 ><P
 ></P
@@ -441,10 +441,8 @@ NAME="query"
       <A
 HREF="http://landfill.bugzilla.org/bugzilla-tip/query.cgi"
 TARGET="_top"
->&#13;      landfill.bugzilla.org/bugzilla-tip/query.cgi</A
+>http://landfill.bugzilla.org/bugzilla-tip/query.cgi</A
->
+>.</P
-
-      .</P
 ><P
 >The Search page has controls for selecting different possible
       values for all of the fields in a bug, as described above. Once you've

webtools/bugzilla/docs/html/http.html

@@ -120,7 +120,7 @@ CLASS="command"
 >./checksetup.pl</B
 > (shown in <A
 HREF="http.html#http-apache-htaccess"
->Example 4-1</A
+>Example 4-2</A
 >
       for the curious) are allowed to override Apache's normal access
       permissions or else important password information may be exposed to the
@@ -241,7 +241,7 @@ NAME="http-apache-htaccess"
 ></A
 ><P
 ><B
->Example 4-1. <TT
+>Example 4-2. <TT
 CLASS="filename"
 >.htaccess</TT
 > files for Apache</B
@@ -420,7 +420,7 @@ CLASS="productname"
       <A
 HREF="http://support.microsoft.com/support/kb/articles/Q245/2/25.asp"
 TARGET="_top"
->Q245225 </A
+>Q245225</A
 >
       for <SPAN
 CLASS="productname"
@@ -552,12 +552,11 @@ VALIGN="TOP"
         <TT
 CLASS="filename"
 >localconfig</TT
->. For more information, see
+>. For more information, see 
         <A
 HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=186383"
 TARGET="_top"
->bug
+>&#13;        bug 186383</A
-        186383</A
 > or <A
 HREF="http://online.securityfocus.com/bid/6501"
 TARGET="_top"

webtools/bugzilla/docs/html/index.html

@@ -451,11 +451,16 @@ CLASS="LOT"
 ></DT
 ><DT
 >4-1. <A
+HREF="stepbystep.html#install-mysql-packets"
+>Set Max Packet Size in MySQL</A
+></DT
+><DT
+>4-2. <A
 HREF="troubleshooting.html#trouble-filetemp-errors"
 >Other File::Temp error messages</A
 ></DT
 ><DT
->4-2. <A
+>4-3. <A
 HREF="troubleshooting.html#trouble-filetemp-patch"
 >Patch for File::Temp in Perl 5.6.0</A
 ></DT
@@ -471,6 +476,11 @@ CLASS="LOT"
 ></DT
 ><DT
 >4-1. <A
+HREF="stepbystep.html#install-perlmodules-cpan"
+>Installing perl modules with CPAN</A
+></DT
+><DT
+>4-2. <A
 HREF="http.html#http-apache-htaccess"
 ><TT
 CLASS="filename"

webtools/bugzilla/docs/html/installation.html

@@ -88,55 +88,45 @@ HREF="stepbystep.html"
 ><DL
 ><DT
 >4.1.1. <A
-HREF="stepbystep.html#intstall-into"
->Introduction</A
-></DT
-><DT
->4.1.2. <A
-HREF="stepbystep.html#install-package-list"
->Package List</A
-></DT
-><DT
->4.1.3. <A
 HREF="stepbystep.html#install-mysql"
 >MySQL</A
 ></DT
 ><DT
->4.1.4. <A
+>4.1.2. <A
 HREF="stepbystep.html#install-perl"
 >Perl</A
 ></DT
 ><DT
->4.1.5. <A
+>4.1.3. <A
-HREF="stepbystep.html#perl-modules"
+HREF="stepbystep.html#install-perlmodules"
 >Perl Modules</A
 ></DT
 ><DT
->4.1.6. <A
+>4.1.4. <A
-HREF="stepbystep.html#sbs-http"
+HREF="stepbystep.html#install-webserver"
 >HTTP Server</A
 ></DT
 ><DT
->4.1.7. <A
+>4.1.5. <A
-HREF="stepbystep.html#AEN600"
+HREF="stepbystep.html#install-bzfiles"
 >Bugzilla</A
 ></DT
 ><DT
->4.1.8. <A
+>4.1.6. <A
-HREF="stepbystep.html#AEN611"
+HREF="stepbystep.html#install-setupdatabase"
 >Setting Up the MySQL Database</A
 ></DT
 ><DT
->4.1.9. <A
+>4.1.7. <A
-HREF="stepbystep.html#AEN649"
+HREF="stepbystep.html#AEN749"
 ><TT
 CLASS="filename"
 >checksetup.pl</TT
 ></A
 ></DT
 ><DT
->4.1.10. <A
+>4.1.8. <A
-HREF="stepbystep.html#AEN681"
+HREF="stepbystep.html#AEN780"
 >Configuring Bugzilla</A
 ></DT
 ></DL
@@ -150,17 +140,17 @@ HREF="extraconfig.html"
 ><DL
 ><DT
 >4.2.1. <A
-HREF="extraconfig.html#AEN687"
+HREF="extraconfig.html#AEN786"
 >Dependency Charts</A
 ></DT
 ><DT
 >4.2.2. <A
-HREF="extraconfig.html#AEN702"
+HREF="extraconfig.html#AEN801"
 >Bug Graphs</A
 ></DT
 ><DT
 >4.2.3. <A
-HREF="extraconfig.html#AEN715"
+HREF="extraconfig.html#AEN814"
 >The Whining Cron</A
 ></DT
 ><DT
@@ -268,12 +258,12 @@ HREF="troubleshooting.html"
 ><DL
 ><DT
 >4.5.1. <A
-HREF="troubleshooting.html#AEN977"
+HREF="troubleshooting.html#AEN1076"
 >Bundle::Bugzilla makes me upgrade to Perl 5.6.1</A
 ></DT
 ><DT
 >4.5.2. <A
-HREF="troubleshooting.html#AEN982"
+HREF="troubleshooting.html#AEN1081"
 >DBD::Sponge::db prepare failed</A
 ></DT
 ><DT

webtools/bugzilla/docs/html/integration.html

@@ -131,11 +131,10 @@ CLASS="filename"
 ><P
 >There is also a CVSZilla project, based upon somewhat dated 
     Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to 
-    email. Check it out at: 
+    email. Check it out at: <A
-    <A
 HREF="http://homepages.kcbbs.gen.nz/~tonyg/"
 TARGET="_top"
->&#13;    http://homepages.kcbbs.gen.nz/~tonyg/</A
+>http://homepages.kcbbs.gen.nz/~tonyg/</A
 >.
     </P
 ></DIV
@@ -153,7 +152,7 @@ NAME="scm"
     <A
 HREF="http://www.ravenbrook.com/project/p4dti/"
 TARGET="_top"
->&#13;    http://www.ravenbrook.com/project/p4dti</A
+>http://www.ravenbrook.com/project/p4dti/</A
 >
 
     . 
@@ -167,7 +166,7 @@ CLASS="QUOTE"
     <A
 HREF="http://public.perforce.com/public/perforce/p4dti/index.html"
 TARGET="_top"
->&#13;    http://public.perforce.com/public/perforce/p4dti/index.html</A
+>http://public.perforce.com/public/perforce/p4dti/index.html</A
 >
 
     .</P

webtools/bugzilla/docs/html/newversions.html

@@ -93,7 +93,7 @@ NAME="newversions"
 >&#13;      The newest version of this guide can always be found at <A
 HREF="http://www.bugzilla.org"
 TARGET="_top"
->bugzilla.org</A
+>http://www.bugzilla.org</A
 >; including
       documentation for past releases and the current development version.
     </P
@@ -108,13 +108,12 @@ TARGET="_top"
     </P
 ><P
 >&#13;      The latest version of this document can always be checked out via CVS.
-	    Please follow the instructions available at 
+      Please follow the <A
-      <A
 HREF="http://www.mozilla.org/cvs.html"
 TARGET="_top"
->the Mozilla CVS page</A
+>Mozilla CVS</A
->,
+>
-      and check out the <TT
+      instructions and check out the <TT
 CLASS="filename"
 >mozilla/webtools/bugzilla/docs/</TT
 >

webtools/bugzilla/docs/html/os-specific.html

@@ -143,19 +143,23 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="win32-perl-modules"
+NAME="win32-perlmodules"
 ></A
 >4.3.1.2. Perl Modules on Win32</H3
 ><P
 >Bugzilla on Windows requires the same perl modules found in
         <A
-HREF="stepbystep.html#install-package-list"
+HREF="stepbystep.html#install-perlmodules"
->Section 4.1.2</A
+>Section 4.1.3</A
 >. The main difference is that
-        windows uses <B
+        windows uses <A
-CLASS="command"
+HREF="glossary.html#gloss-ppm"
->ppm</B
+><I
-> instead of CPAN.
+CLASS="glossterm"
+>PPM</I
+></A
+> instead of
+        CPAN.
         </P
 ><TABLE
 BORDER="0"
@@ -606,7 +610,7 @@ CLASS="prompt"
 > <B
 CLASS="command"
 >urpmi perl-MailTools</B
->    <A
+>             <A
 NAME="test-mailtools"
 ><IMG
 SRC="../images/callouts/1.gif"

webtools/bugzilla/docs/html/security.html

@@ -406,12 +406,11 @@ NAME="security-access"
       not be accessible is rather complicated. A new installation method
       is currently in the works which should solve this by allowing files
       that shouldn't be accessible from the web to be placed in directory
-      outside the webroot. See
+      outside the webroot. See 
       <A
 HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=44659"
 TARGET="_top"
->bug
+>&#13;      bug 44659</A
-      44659</A
 > for more information.
       </P
 ><P

webtools/bugzilla/docs/html/troubleshooting.html

@@ -85,7 +85,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN977"
+NAME="AEN1076"
 ></A
 >4.5.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
 ><P
@@ -110,7 +110,7 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="AEN982"
+NAME="AEN1081"
 ></A
 >4.5.2. DBD::Sponge::db prepare failed</H2
 ><P
@@ -266,7 +266,7 @@ CLASS="productname"
       5.6.0. Many minor variations of this error have been reported. Examples
       can be found in <A
 HREF="troubleshooting.html#trouble-filetemp-errors"
->Figure 4-1</A
+>Figure 4-2</A
 >.
       </P
 ><DIV
@@ -276,7 +276,7 @@ NAME="trouble-filetemp-errors"
 ></A
 ><P
 ><B
->Figure 4-1. Other File::Temp error messages</B
+>Figure 4-2. Other File::Temp error messages</B
 ></P
 ><TABLE
 BORDER="0"
@@ -307,7 +307,7 @@ at /usr/lib/perl5/site_perl/5.6.0/File/Temp.pm line 233.
       or higher solved the problem for them. A less involved fix is to apply
       the patch in <A
 HREF="troubleshooting.html#trouble-filetemp-patch"
->Figure 4-2</A
+>Figure 4-3</A
 >. The patch is also
       available as a <A
 HREF="../xml/filetemp.patch"
@@ -322,7 +322,7 @@ NAME="trouble-filetemp-patch"
 ></A
 ><P
 ><B
->Figure 4-2. Patch for File::Temp in Perl 5.6.0</B
+>Figure 4-3. Patch for File::Temp in Perl 5.6.0</B
 ></P
 ><TABLE
 BORDER="0"

webtools/bugzilla/docs/html/using.html

@@ -122,7 +122,7 @@ HREF="hintsandtips.html"
 ><DL
 ><DT
 >3.2.1. <A
-HREF="hintsandtips.html#AEN370"
+HREF="hintsandtips.html#AEN371"
 >Autolinkification</A
 ></DT
 ><DT
@@ -142,7 +142,7 @@ HREF="hintsandtips.html#attachments"
 ></DT
 ><DT
 >3.2.5. <A
-HREF="hintsandtips.html#AEN399"
+HREF="hintsandtips.html#AEN400"
 >Filing Bugs</A
 ></DT
 ></DL

webtools/bugzilla/docs/html/variant-perforce.html

@@ -84,12 +84,10 @@ CLASS="QUOTE"
 >
     functionality.</P
 ><P
->URL: 
+>URL: <A
-    <A
 HREF="http://www.perforce.com/perforce/technotes/note052.html"
 TARGET="_top"
->&#13;    http://www.perforce.com/perforce/technotes/note052.html
+>http://www.perforce.com/perforce/technotes/note052.html</A
-    </A
 >
     </P
 ><P

webtools/bugzilla/docs/html/variant-redhat.html

@@ -78,26 +78,25 @@ NAME="variant-redhat"
 >D.1. Red Hat Bugzilla</H1
 ><P
 >Red Hat's old fork of Bugzilla which was based on version 2.8 is now
-    obsolete.  The newest version in use is based on version 2.17.1 and is in
+    obsolete. The newest version in use is based on version 2.17.1 and is in
-    the process of being integrated into the main Bugzilla source tree.  The
+    the process of being integrated into the main Bugzilla source tree. The
     back-end is modified to work with PostgreSQL instead of MySQL and they have
     custom templates to get their desired look and feel, but other than that it
-    is Bugzilla 2.17.1.  Dave Lawrence of Red Hat put forth a great deal of
+    is Bugzilla 2.17.1. Dave Lawrence of Red Hat put forth a great deal of
     effort to make sure that the changes he made could be integrated back into
     the main tree. 
     <A
 HREF="http://bugzilla.mozilla.org/show_bug.cgi?id=98304"
 TARGET="_top"
->Bug
+>Bug 98304</A
-    98304</A
+>
-> exists to track this integration.
+    exists to track this integration.
     </P
 ><P
->URL: 
+>URL: <A
-    <A
 HREF="http://bugzilla.redhat.com/bugzilla/"
 TARGET="_top"
->&#13;    http://bugzilla.redhat.com/bugzilla/</A
+>http://bugzilla.redhat.com/bugzilla/</A
 >
     </P
 ><P

webtools/bugzilla/docs/html/variant-scarab.html

@@ -80,11 +80,10 @@ NAME="variant-scarab"
 >Scarab is a new open source bug-tracking system built using Java
     Servlet technology. It is currently at version 1.0 beta 13.</P
 ><P
->URL: 
+>URL: <A
-    <A
 HREF="http://scarab.tigris.org/"
 TARGET="_top"
->http://scarab.tigris.org</A
+>http://scarab.tigris.org/</A
 >
     </P
 ><P

webtools/bugzilla/docs/html/variant-sourceforge.html

@@ -81,11 +81,10 @@ NAME="variant-sourceforge"
     distributed free software and open source projects over the Internet.
     It has a built-in bug tracker, but it's not highly thought of.</P
 ><P
->URL: 
+>URL: <A
-    <A
 HREF="http://www.sourceforge.net"
 TARGET="_top"
->&#13;    http://www.sourceforge.net</A
+>http://www.sourceforge.net</A
 >
     </P
 ><P

webtools/bugzilla/docs/html/variants.html

@@ -119,8 +119,8 @@ HREF="variant-sourceforge.html"
   <A
 HREF="http://linas.org/linux/pm.html"
 TARGET="_top"
->&#13;  http://linas.org/linux/pm.html</A
+>http://linas.org/linux/pm.html</A
->
+>.
   </P
 ></DIV
 ><DIV

webtools/bugzilla/docs/html/voting.html

@@ -106,7 +106,7 @@ TYPE="1"
 ><P
 ><EM
 >Maximum Votes a person can put on a single
-         bug"</EM
+         bug</EM
 >: 
          It should probably be some number lower than the
         "Maximum votes per person". Don't set this field to "0" if