summaryrefslogtreecommitdiffstats
path: root/template/en/default
diff options
context:
space:
mode:
authorA. Shimono <shimono@bug-ja.org>2011-01-09 15:24:48 +0100
committerFrédéric Buclin <LpSolit@gmail.com>2011-01-09 15:24:48 +0100
commit6da18342f1be71130dbcb39a0c4fac453ac9f7c5 (patch)
tree360dd249e7f718743c0c28ac07e0d4dd01bf83b2 /template/en/default
parentad089c24e947b5baa99daffbea19514d88806797 (diff)
downloadbugzilla-6da18342f1be71130dbcb39a0c4fac453ac9f7c5.tar.gz
bugzilla-6da18342f1be71130dbcb39a0c4fac453ac9f7c5.tar.xz
Bug 618841: Bare word "bug" in release notes
r=dkl a=LpSolit
Diffstat (limited to 'template/en/default')
-rw-r--r--template/en/default/pages/release-notes.html.tmpl6
1 files changed, 3 insertions, 3 deletions
diff --git a/template/en/default/pages/release-notes.html.tmpl b/template/en/default/pages/release-notes.html.tmpl
index 06ba0eda3..aabe352b9 100644
--- a/template/en/default/pages/release-notes.html.tmpl
+++ b/template/en/default/pages/release-notes.html.tmpl
@@ -251,8 +251,8 @@
if you did two separate searches in separate windows, these links would
only work for the <em>last</em> search you did. Now, [% terms.Bugzilla %]
will "remember" which search result you came from and give you the right
- "last search results" or "next bug" from <em>that</em> list, instead of
- always using your most recent search.</p>
+ "last search results" or "next [% terms.bug %]" from <em>that</em> list,
+ instead of always using your most recent search.</p>
<p>There are still some situations where [% terms.Bugzilla %] will have to
"guess" which search you are trying to navigate through, but it does its
@@ -487,7 +487,7 @@
bugmail_relationships, object_columns, object_update_columns,
and object_validators. The colchange_columns hook has been removed,
as it is no longer necessary (buglist_columns will be used for data
- about which columns can be on the buglist).</li>
+ about which columns can be on the [% terms.bug %] list).</li>
<li>When [% terms.Bugzilla %] throws certain types of errors, it will
now include a "traceback" of where exactly the error occurred in the
code, to help administrators and developers debug problems.</li>