Bug 106386 rid source of misspellings

r=db48x sr=blake a=asa

diff --git a/docs/html/Bugzilla-Guide.html b/docs/html/Bugzilla-Guide.html
index 60045e438cdcd609caf32b209ac3a00870e887bc..77f0578ac34966913295bf48bc8ad8310f916590 100644 (file)
--- 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 6727dfa88d6d9ed5cb28c79aaf77f02bfd9a89d9..5340109bbce9f021ffba4c54b0fefc4fbe832655 100644 (file)
--- a/docs/html/bzhacking.html
+++ b/docs/html/bzhacking.html
@@ -217,7 +217,7 @@ CLASS="command"
 >
            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 b7f54e09bab0862d959a02ac6a268e8c7eba6739..31d867e861ad1bb85329e4ba870f233355330c57 100644 (file)
--- 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 10732dd61b5c3888a619a4e09b3d4070e1886871..a01651b63c2e9edea91485a4565b116495dc0fe9 100644 (file)
--- 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 b7f54e09bab0862d959a02ac6a268e8c7eba6739..31d867e861ad1bb85329e4ba870f233355330c57 100644 (file)
--- 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 93cbef755dbd6eee5674d2212fdb596c7df17d0e..9fd5d9857457958acd6d4f7dcbd8e6b8ebc314c6 100755 (executable)
--- 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.
 
 };