Commit d8c3c733 authored by timeless%mozdev.org's avatar timeless%mozdev.org

Bug 364361 The word "Customising" in chapter 6 title is spelled wrong in all documentation

r=colin.ogilvie, kevin.benton
parent fcece8cd
......@@ -2387,7 +2387,7 @@ See also next section.
'letsubmitterchoosepriority' was off.
(bug 63018)
- Most CGIs are now templatised. This helps to make it
- Most CGIs are now templatized. This helps to make it
easier to remember to HTML filter values and easier to spot
when they are not, preventing cross site scripting attacks.
(bug 86168)
......@@ -2398,17 +2398,17 @@ See also next section.
*** IMPORTANT CHANGES ***
- 2.16 introduces "templatisation", a new feature that allows
administrators to easily customise the HTML output (the "look and feel")
- 2.16 introduces "templatization", a new feature that allows
administrators to easily customize the HTML output (the "look and feel")
of Bugzilla without altering Perl code. Bugzilla uses the
"Template Toolkit" for this. Please see the "Template Customisation"
"Template Toolkit" for this. Please see the "Template Customization"
section of the Bugzilla Guide for more details.
Administrators who ran the 2.15 development version and customised
Administrators who ran the 2.15 development version with custom
templates should check the templates are still valid, as file names
and file paths have changed.
Most output is now templatised. This process will be complete next
Most output is now templatized. This process will be complete next
milestone.
For speed, compiled templates are cached on disk. If you modify the
......@@ -2462,7 +2462,7 @@ See also next section.
lengthy delays in future if this problem reoccurs.
(bug 106377)
- In parallel with templatisation, a lot of changes have been made to the HTML
- In parallel with templatization, a lot of changes have been made to the HTML
output of the Bugzilla CGIs. This could break code that attempts to parse
such code. For example, this breaks mozbot.
(no bug number)
......@@ -2739,8 +2739,8 @@ known to us after the Bugzilla 2.14 release.
*** SECURITY ISSUES RESOLVED ***
- Multiple instances of unauthorised access to confidential
bugs has been fixed.
- Multiple instances of unauthorized access to confidential
bugs have been fixed.
(bug 39524, 39526, 39527, 39531, 39533, 70189, 82781)
- Multiple instances of untrusted parameters not being
......@@ -2751,7 +2751,7 @@ known to us after the Bugzilla 2.14 release.
- After logging in passwords no longer appear in the URL.
(bug 15980)
- Procedures to prevent unauthorised access to confidential
- Procedures to prevent unauthorized access to confidential
files are now simpler. In particular the shadow directory
no longer exists and the data/comments file no longer needs
to be directly accessible, so the entire data directory can
......@@ -2762,7 +2762,7 @@ known to us after the Bugzilla 2.14 release.
- If they do not already exist, checksetup.pl will attempt to
write Apache .htaccess files by default, to prevent
unauthorised access to confidential files. You can turn this
unauthorized access to confidential files. You can turn this
off in the localconfig file.
(bug 76154)
......
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!ENTITY conventions SYSTEM "conventions.xml"> ] > -->
<!-- $Id: about.xml,v 1.18 2008/04/04 06:48:10 jake%bugzilla.org Exp $ -->
<!-- $Id: about.xml,v 1.25 2008/04/04 06:48:17 timeless%mozdev.org Exp $ -->
<chapter id="about">
<title>About This Guide</title>
......@@ -65,10 +65,8 @@
<para>
This is the &bz-ver; version of The Bugzilla Guide. It is so named
to match the current version of Bugzilla.
<![%bz-devel;[
This version of the guide, like its associated Bugzilla version, is a
development version.
]]>
<!-- BZ-DEVEL --> This version of the guide, like its associated Bugzilla version, is a
development version.<!-- /BZ-DEVEL -->
</para>
<para>
The latest version of this guide can always be found at <ulink
......@@ -82,18 +80,25 @@
<para>
The Bugzilla Guide, or a section of it, is also available in
the following languages:
<ulink url="http://bugzilla-de.sourceforge.net/docs/html/">German</ulink>.
<ulink url="http://www.traduc.org/docs/guides/lecture/bugzilla/">French</ulink>,
<ulink url="http://bugzilla-de.sourceforge.net/docs/html/">German</ulink>,
<ulink url="http://www.bugzilla.jp/docs/2.18/">Japanese</ulink>.
Note that these may be outdated or not up to date.
</para>
<para>
In addition, there are Bugzilla template localisation projects in
In addition, there are Bugzilla template localization projects in
the following languages. They may have translated documentation
available:
<ulink url="http://sourceforge.net/projects/bugzilla-ar/">Arabic</ulink>,
<ulink url="http://sourceforge.net/projects/bugzilla-be/">Belarusian</ulink>,
<ulink url="http://openfmi.net/projects/mozilla-bg/">Bulgarian</ulink>,
<ulink url="http://sourceforge.net/projects/bugzilla-br/">Brazilian Portuguese</ulink>,
<ulink url="http://sourceforge.net/projects/bugzilla-cn/">Chinese</ulink>,
<ulink url="http://sourceforge.net/projects/bugzilla-fr/">French</ulink>,
<ulink url="http://sourceforge.net/projects/bugzilla-de/">German</ulink>,
<ulink url="http://germzilla.wurblzap.net/">German</ulink>,
<ulink url="http://sourceforge.net/projects/bugzilla-it/">Italian</ulink>,
<ulink url="http://www.bugzilla.jp/about/jp.html">Japanese</ulink>,
<ulink url="http://sourceforge.net/projects/bugzilla-kr/">Korean</ulink>,
<ulink url="http://sourceforge.net/projects/bugzilla-ru/">Russian</ulink> and
<ulink url="http://sourceforge.net/projects/bugzilla-es/">Spanish</ulink>.
......@@ -102,7 +107,7 @@
<para>
If you would like to volunteer to translate the Guide into additional
languages, please contact
<ulink url="mailto:justdave@syndicomm.com">Dave Miller</ulink>.
<ulink url="mailto:justdave@bugzilla.org">Dave Miller</ulink>.
</para>
</section>
......@@ -120,7 +125,7 @@
<varlistentry>
<term>Matthew P. Barnson <email>mbarnson@sisna.com</email></term>
<listitem>
<para>for the Herculaean task of pulling together the Bugzilla Guide
<para>for the Herculean task of pulling together the Bugzilla Guide
and shepherding it to 2.14.
</para>
</listitem>
......@@ -204,9 +209,10 @@
<para>
Also, thanks are due to the members of the
<ulink url="news://news.mozilla.org/netscape.public.mozilla.webtools">
netscape.public.mozilla.webtools</ulink>
newsgroup. Without your discussions, insight, suggestions, and patches,
<ulink url="news://news.mozilla.org/mozilla.support.bugzilla">
mozilla.support.bugzilla</ulink>
newsgroup (and its predecessor, netscape.public.mozilla.webtools).
Without your discussions, insight, suggestions, and patches,
this could never have happened.
</para>
</section>
......
......@@ -68,7 +68,7 @@
</listitem>
<listitem>
<para>Completely customisable and/or localisable web user
<para>Completely customizable and/or localizable web user
interface</para>
</listitem>
......
......@@ -72,7 +72,7 @@
<para>
By default, you have 3 days to confirm your registration. Past this
timeframe, the token is invalidated and the registration is
automatically cancelled. You can also cancel this registration sooner
automatically canceled. You can also cancel this registration sooner
by using the appropriate URL in the email you got.
</para>
</listitem>
......@@ -243,7 +243,7 @@
<listitem>
<para>
<emphasis>Priority:</emphasis>
The bug assignee uses this field to prioritise his or her bugs.
The bug assignee uses this field to prioritize his or her bugs.
It's a good idea not to change this on other people's bugs.</para>
</listitem>
......@@ -402,8 +402,8 @@
have them show up in your personal Bugzilla footer along with your own
Saved Searches.
If somebody is sharing a Search with a group she or he is allowed to
<link linkend="groups">assign users to</link>, it will show up in the
group's direct members' footers by default.
<link linkend="groups">assign users to</link>, the sharer may opt to have
the Search show up in the group's direct members' footers by default.
</para>
<section id="boolean">
......@@ -458,7 +458,7 @@
to whom each bug is assigned). When the operator is either
"equals" or "notequals", the value can be "%reporter%",
"%assignee%", "%qacontact%", or "%user%." The user pronoun
referes to the user who is executing the query or, in the case
refers to the user who is executing the query or, in the case
of whining reports, the user who will be the recipient
of the report. The reporter, assignee, and qacontact
pronouns refer to the corresponding fields in the bug.
......@@ -1064,7 +1064,7 @@
<section id="userpreferences">
<title>User Preferences</title>
<para>Once you have logged in, you can customise various aspects of
<para>Once you have logged in, you can customize various aspects of
Bugzilla via the "Edit prefs" link in the page footer.
The preferences are split into three tabs:</para>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment