From 2d4d7c92bfb4ce18e4413b1e66f30bd62a44e6ff Mon Sep 17 00:00:00 2001
From: "barnboy%trilobyte.net" <>
Date: Wed, 25 Apr 2001 14:11:45 +0000
Subject: Updated Bugzilla Guide and README to fix bug 76156, bug 76841, and
 bug 26242. The README is now gutted, pointers to Guide.  Also some new
 sections added, old ones fixed, and notes appended to deprecated sections
 I've not yet had the heart to remove.

---
 docs/html/why.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'docs/html/why.html')

diff --git a/docs/html/why.html b/docs/html/why.html
index 96363c6c2..b3110f1ec 100644
--- a/docs/html/why.html
+++ b/docs/html/why.html
@@ -4,7 +4,7 @@
 >Why Should We Use Bugzilla?</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.61
+CONTENT="Modular DocBook HTML Stylesheet Version 1.64
 "><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide"
@@ -124,7 +124,7 @@ VALIGN="TOP"
 >      Bugzilla is very adaptable to various situations.  Known uses currently
       include IT support queues, Systems Administration deployment management,
       chip design and development problem tracking (both pre-and-post fabrication),
-      and software bug tracking for luminaries such as Redhat, Loki software,
+      and software and hardware bug tracking for luminaries such as Redhat, Loki software,
       Linux-Mandrake, and VA Systems.  Combined with systems such as CVS, Bonsai,
       or Perforce SCM, Bugzilla provides a powerful, easy-to-use  solution to
       configuration management and replication problems
-- 
cgit v1.2.3-24-g4f1b