summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authortimeless%mac.com <>2002-03-19 13:30:01 +0100
committertimeless%mac.com <>2002-03-19 13:30:01 +0100
commit4accb1955e7d530a322dc64d63807c52bf11c968 (patch)
tree70f2d1537593e3fa45753d05a74c82f816e47649
parent838fdab57fb30cbbbaddaa686d6bd9e6a7fe6021 (diff)
downloadbugzilla-4accb1955e7d530a322dc64d63807c52bf11c968.tar.gz
bugzilla-4accb1955e7d530a322dc64d63807c52bf11c968.tar.xz
Bug 106386 rid source of misspellings
r=db48x sr=blake a=asa
-rw-r--r--docs/html/Bugzilla-Guide.html4
-rw-r--r--docs/html/bzhacking.html2
-rw-r--r--docs/sgml/patches.sgml2
-rw-r--r--docs/txt/Bugzilla-Guide.txt4
-rw-r--r--docs/xml/patches.xml2
-rwxr-xr-xqueryhelp.cgi2
6 files changed, 8 insertions, 8 deletions
diff --git a/docs/html/Bugzilla-Guide.html b/docs/html/Bugzilla-Guide.html
index 60045e438..77f0578ac 100644
--- a/docs/html/Bugzilla-Guide.html
+++ b/docs/html/Bugzilla-Guide.html
@@ -7419,7 +7419,7 @@ CLASS="function"
> when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting <TT
CLASS="function"
>binmode()</TT
-> at the begining of the attachment files, there should be logic to determine if <TT
+> at the beginning of the attachment files, there should be logic to determine if <TT
CLASS="function"
>binmode()</TT
> is needed or not.
@@ -16369,7 +16369,7 @@ CLASS="command"
>&#13; Whitespace
</P
><P
->&#13; Bugzilla's prefered indentation is 4 spaces (no tabs, please).
+>&#13; Bugzilla's preferred indentation is 4 spaces (no tabs, please).
</P
></LI
><LI
diff --git a/docs/html/bzhacking.html b/docs/html/bzhacking.html
index 6727dfa88..5340109bb 100644
--- a/docs/html/bzhacking.html
+++ b/docs/html/bzhacking.html
@@ -217,7 +217,7 @@ CLASS="command"
>&#13; Whitespace
</P
><P
->&#13; Bugzilla's prefered indentation is 4 spaces (no tabs, please).
+>&#13; Bugzilla's preferred indentation is 4 spaces (no tabs, please).
</P
></LI
><LI
diff --git a/docs/sgml/patches.sgml b/docs/sgml/patches.sgml
index b7f54e09b..31d867e86 100644
--- a/docs/sgml/patches.sgml
+++ b/docs/sgml/patches.sgml
@@ -317,7 +317,7 @@ grep (/$value/, @array);
Whitespace
</para>
<para>
- Bugzilla's prefered indentation is 4 spaces (no tabs, please).
+ Bugzilla's preferred indentation is 4 spaces (no tabs, please).
</para>
</listitem>
<listitem>
diff --git a/docs/txt/Bugzilla-Guide.txt b/docs/txt/Bugzilla-Guide.txt
index 10732dd61..a01651b63 100644
--- a/docs/txt/Bugzilla-Guide.txt
+++ b/docs/txt/Bugzilla-Guide.txt
@@ -2171,7 +2171,7 @@ binmode(STDOUT);
According to bug 62000, the perl documentation says that you should
always use binmode() when dealing with binary files, but never when
dealing with text files. That seems to suggest that rather than
- aribtrarily putting binmode() at the begining of the attachment files,
+ aribtrarily putting binmode() at the beginning of the attachment files,
there should be logic to determine if binmode() is needed or not.
Tip
@@ -5921,7 +5921,7 @@ D.5.2. Coding Style for Bugzilla
Bugzilla.
* Whitespace
- Bugzilla's prefered indentation is 4 spaces (no tabs, please).
+ Bugzilla's preferred indentation is 4 spaces (no tabs, please).
* Curly braces.
The opening brace of a block should be on the same line as the
statement that is causing the block and the closing brace should
diff --git a/docs/xml/patches.xml b/docs/xml/patches.xml
index b7f54e09b..31d867e86 100644
--- a/docs/xml/patches.xml
+++ b/docs/xml/patches.xml
@@ -317,7 +317,7 @@ grep (/$value/, @array);
Whitespace
</para>
<para>
- Bugzilla's prefered indentation is 4 spaces (no tabs, please).
+ Bugzilla's preferred indentation is 4 spaces (no tabs, please).
</para>
</listitem>
<listitem>
diff --git a/queryhelp.cgi b/queryhelp.cgi
index 93cbef755..9fd5d9857 100755
--- a/queryhelp.cgi
+++ b/queryhelp.cgi
@@ -575,7 +575,7 @@ find describe. Selecting one or more of the products, versions, components, or m
<h4>Products</h4>
-<p>Although all subprojects within the Mozilla project are similiar, there are several seperate
+<p>Although all subprojects within the Mozilla project are similar, there are several seperate
products being developed. Each product has its own components.
};