summaryrefslogtreecommitdiffstats
path: root/template/en/default/pages
diff options
context:
space:
mode:
authortimeless%mozdev.org <>2004-03-19 01:21:56 +0100
committertimeless%mozdev.org <>2004-03-19 01:21:56 +0100
commit2478a13d479563c23347de222e3da2ed34d71508 (patch)
tree49b21d1dcd314953ca5710fd0d0b0fc052d5f6ab /template/en/default/pages
parentd00f3ac25660d8f535f6ae00c54fc0c08bcae7f3 (diff)
downloadbugzilla-2478a13d479563c23347de222e3da2ed34d71508.tar.gz
bugzilla-2478a13d479563c23347de222e3da2ed34d71508.tar.xz
Bug 237772 instances of "a terms.bug" should be replaced with "terms.abug"
also fix the spelling of decipher r=gerv r=kiko a=justdave
Diffstat (limited to 'template/en/default/pages')
-rw-r--r--template/en/default/pages/bug-writing.html.tmpl10
-rw-r--r--template/en/default/pages/fields.html.tmpl12
-rw-r--r--template/en/default/pages/voting.html.tmpl2
3 files changed, 12 insertions, 12 deletions
diff --git a/template/en/default/pages/bug-writing.html.tmpl b/template/en/default/pages/bug-writing.html.tmpl
index 1a228b0c4..c007b043b 100644
--- a/template/en/default/pages/bug-writing.html.tmpl
+++ b/template/en/default/pages/bug-writing.html.tmpl
@@ -31,7 +31,7 @@
<h3>Why You Should Read This</h3>
<blockquote>
- <p>Simply put, the more effectively you report a [% terms.bug %], the more
+ <p>Simply put, the more effectively you report [% terms.abug %], the more
likely an
engineer will actually fix it.</p>
@@ -57,7 +57,7 @@
<li><b>Specific.</b> The quicker the engineer can isolate the
[% terms.bug %] to a specific area, the more likely she'll expediently
- fix it. (If a programmer or tester has to decypher a [% terms.bug %],
+ fix it. (If a programmer or tester has to decipher [% terms.abug %],
they may spend more time cursing the submitter than solving the
problem.)<br>
<br>
@@ -163,7 +163,7 @@
<p><b>Assigned To: Which engineer should be responsible for fixing
this [% terms.bug %]?</b><br>
[% terms.Bugzilla %] will automatically assign the [% terms.bug %] to a
- default engineer upon submitting a [% terms.bug %] report. If you'd prefer
+ default engineer upon submitting [% terms.abug %] report. If you'd prefer
to directly assign the [% terms.bug %] to someone else, enter their e-mail
address into this field. (To see the list of default engineers for each
component, click on the Component link.)</p>
@@ -181,7 +181,7 @@
<blockquote>
<p><b>Summary:</b> <b>How would you describe the [% terms.bug %], in
approximately 60 or fewer characters?</b><br>
- A good summary should <b>quickly and uniquely identify a [% terms.bug %]
+ A good summary should <b>quickly and uniquely identify [% terms.abug %]
report</b>. Otherwise, an engineer cannot meaningfully identify your
[% terms.bug %] by its summary, and will often fail to pay attention to
your [% terms.bug %] report when skimming through a 10
@@ -323,7 +323,7 @@ PowerPC unmapped memory exception at 0B512BD0 NSGetFactory+055F0
mix a handful of [% terms.bugs %] into a single report, the right people
probably won't discover your [% terms.bugs %] in a timely fashion, or at
all. Certain [% terms.bugs %] are also more important than others. It's
- impossible to prioritize a [% terms.bug %] report when
+ impossible to prioritize [% terms.abug %] report when
it contains four different issues, all of differing importance.</p>
<p><b>No [% terms.bug %] is too trivial to report.</b> Unless you're
diff --git a/template/en/default/pages/fields.html.tmpl b/template/en/default/pages/fields.html.tmpl
index caec210b8..a6c9842e6 100644
--- a/template/en/default/pages/fields.html.tmpl
+++ b/template/en/default/pages/fields.html.tmpl
@@ -25,7 +25,7 @@
<p>
The <b>status</b> and <b>resolution</b> fields define and track the life
-cycle of a [% terms.bug %].
+cycle of [% terms.abug %].
</p>
<a name="status"></a>
@@ -130,17 +130,17 @@ cycle of a [% terms.bug %].
<dt><b>INVALID</b></dt>
- <dd>The problem described is not a [% terms.bug %]</dd>
+ <dd>The problem described is not [% terms.abug %]</dd>
<dt><b>WONTFIX</b></dt>
- <dd>The problem described is a [% terms.bug %] which will never be
+ <dd>The problem described is [% terms.abug %] which will never be
fixed.</dd>
<dt><b>DUPLICATE</b></dt>
<dd>The problem is a duplicate of an existing [% terms.bug %]. Marking
- a [% terms.bug %] duplicate requires the [% terms.bug %]# of the
+ [% terms.abug %] duplicate requires the [% terms.bug %]# of the
duplicating [% terms.bug %] and will at least put that [% terms.bug %]
number in the description field.</dd>
@@ -162,7 +162,7 @@ cycle of a [% terms.bug %].
</table>
<h2><a name="bug_severity">Severity</a></h2>
-This field describes the impact of a [% terms.bug %].
+This field describes the impact of [% terms.abug %].
<table>
<tr>
@@ -204,7 +204,7 @@ This field describes the impact of a [% terms.bug %].
</table>
<h2><a name="priority">Priority</a></h2>
-This field describes the importance and order in which a [% terms.bug %]
+This field describes the importance and order in which [% terms.abug %]
should be fixed. This field is utilized by the
programmers/engineers to prioritize their work to be done. The
available priorities range from <b>P1</b> (most important) to
diff --git a/template/en/default/pages/voting.html.tmpl b/template/en/default/pages/voting.html.tmpl
index 2e555b1ce..f1d768307 100644
--- a/template/en/default/pages/voting.html.tmpl
+++ b/template/en/default/pages/voting.html.tmpl
@@ -42,7 +42,7 @@ a little for many [% terms.bugs %], or vote a lot for a few [% terms.bugs %].
have at least one vote.</li>
</ul>
-<p>To vote for a [% terms.bug %]:</p>
+<p>To vote for [% terms.abug %]:</p>
<ul>
<li>Bring up the [% terms.bug %] in question.</li>