From 2a6d11573eded8ba5f5fb367f5f0575a048a068d Mon Sep 17 00:00:00 2001
From: =?utf8?q?Fr=C3=A9d=C3=A9ric=20Buclin?= <LpSolit@gmail.com>
Date: Wed, 14 Jul 2010 01:11:42 +0200
Subject: [PATCH] Bug 536183: Docs claim bug lifecycle is "hard-coded" despite
 that's no longer true r=gerv a=mkanat

---
 docs/en/xml/using.xml | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/docs/en/xml/using.xml b/docs/en/xml/using.xml
index 101a9d131a..e26de42308 100644
--- a/docs/en/xml/using.xml
+++ b/docs/en/xml/using.xml
@@ -365,10 +365,12 @@
     <title>Life Cycle of a Bug</title>
 
     <para>
-      The life cycle, also known as work flow, of a bug is currently hardcoded
-      into Bugzilla. <xref linkend="lifecycle-image"/> contains a graphical
-      representation of this life cycle. If you wish to customize this image for
-      your site, the <ulink url="../images/bzLifecycle.xml">diagram file</ulink>
+      The life cycle of a bug, also known as workflow, is customizable to match
+      the needs of your organization, see <xref linkend="bug_status_workflow"/>.
+      <xref linkend="lifecycle-image"/> contains a graphical representation of
+      the default workflow using the default bug statuses. If you wish to
+      customize this image for your site, the
+      <ulink url="../images/bzLifecycle.xml">diagram file</ulink>
       is available in <ulink url="http://www.gnome.org/projects/dia">Dia's</ulink>
       native XML format.
     </para>
-- 
2.47.2