Bug 759413 - Use "cannot" instead of "can not".

r=Wurblzap, a=LpSolit

4 files changed, 7 insertions, 7 deletions

diff --git a/docs/en/xml/administration.xml b/docs/en/xml/administration.xml
index f3c640a5b..d0525d917 100644
--- a/docs/en/xml/administration.xml
+++ b/docs/en/xml/administration.xml
@@ -2362,7 +2362,7 @@ ReadOnly: ENTRY, NA/NA, CANEDIT
     <para>
     Keywords are global, rather than per-product. If the administrator changes
     a keyword currently applied to any bugs, the keyword cache must be rebuilt
-    using the <xref linkend="sanitycheck"/> script. Currently keywords can not
+    using the <xref linkend="sanitycheck"/> script. Currently keywords cannot
     be marked obsolete to prevent future usage.
     </para>
     <para>
@@ -2386,7 +2386,7 @@ ReadOnly: ENTRY, NA/NA, CANEDIT
     </para>
     <tip>
       <para>
-        Before adding a Custom Field, make sure that Bugzilla can not already
+        Before adding a Custom Field, make sure that Bugzilla cannot already
         do the desired behavior. Many Bugzilla options are not enabled by 
         default, and many times Administrators find that simply enabling
         certain options that already exist is sufficient. 
@@ -3160,7 +3160,7 @@ ReadOnly: ENTRY, NA/NA, CANEDIT
     To run the "Sanity Check" script, log in as an Administrator and click the
     "Sanity Check" link in the admin page. Any problems that are found will be
     displayed in red letters. If the script is capable of fixing a problem,
-    it will present a link to initiate the fix. If the script can not
+    it will present a link to initiate the fix. If the script cannot
     fix the problem it will require manual database administration or recovery.
     </para>
     <para>
diff --git a/docs/en/xml/customization.xml b/docs/en/xml/customization.xml
index 1bc3f10d8..ce549b8ea 100644
--- a/docs/en/xml/customization.xml
+++ b/docs/en/xml/customization.xml
@@ -488,7 +488,7 @@
      except group restrictions (unless they are members of the groups they 
      are trying to change). Bug reporters also have the ability to edit some 
      fields, but in a more restrictive manner. Other users, without 
-     <emphasis>editbugs</emphasis> privileges, can not edit 
+     <emphasis>editbugs</emphasis> privileges, cannot edit 
      bugs, except to comment and add themselves to the CC list.
     </para> 
     
diff --git a/docs/en/xml/installation.xml b/docs/en/xml/installation.xml
index bf9c5a1cc..8c5c29b8e 100644
--- a/docs/en/xml/installation.xml
+++ b/docs/en/xml/installation.xml
@@ -2394,7 +2394,7 @@ bash$ <command>./checksetup.pl</command>
           <warning>
             <para>
               The period at the beginning of the command
-              <command>./checksetup.pl</command> is important and can not
+              <command>./checksetup.pl</command> is important and cannot
               be omitted.
             </para>
           </warning>
diff --git a/docs/en/xml/using.xml b/docs/en/xml/using.xml
index da389c43b..e625cca16 100644
--- a/docs/en/xml/using.xml
+++ b/docs/en/xml/using.xml
@@ -1531,7 +1531,7 @@
           </term>
           <listitem>
             <para> 
-             Indicates user can not be impersonated by other users.
+             Indicates user cannot be impersonated by other users.
             </para>
           </listitem>
         </varlistentry>
@@ -2014,7 +2014,7 @@
         <para>
           When running queries, the whining system acts as if you are the user
           executing the query.  This means that the whining system will ignore
-          bugs that match your query, but that you can not access.
+          bugs that match your query, but that you cannot access.
         </para>
       </note>