Documentation patch for bug 296741: 'resticted' spelled wrongly in Bugzilla documentation; patch by me, r=colin.ogilvie.

1 files changed, 11 insertions, 69 deletions

diff --git a/docs/en/xml/administration.xml b/docs/en/xml/administration.xml
index a32a61a59..36dcc14e9 100644
--- a/docs/en/xml/administration.xml
+++ b/docs/en/xml/administration.xml
@@ -82,22 +82,6 @@
 
       <varlistentry>
         <term>
-          maildeliverymethod
-        </term>
-        <listitem>
-          <para>
-            This is used to specify how email is sent, or if it is sent at 
-            all.  There are several options included for different MTAs, 
-            along with two additional options that disable email sending.  
-            "testfile" does not send mail, but instead saves it in 
-            <filename>data/mailer.testfile</filename> for later review.  
-            "none" disables email sending entirely.
-          </para>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry>
-        <term>
           shadowdb
         </term>
         <listitem>
@@ -209,7 +193,7 @@
         <listitem>
           <para>
             This allows you to define an email address for each component, 
-            in addition to that of the default assignee, who will be sent
+            in addition to that of the default owner, who will be sent
             carbon copies of incoming bugs.
           </para>
         </listitem>
@@ -536,46 +520,6 @@
           </listitem>
         </itemizedlist>
       </section>
-      
-      <section id="impersonatingusers">
-        <title>Impersonating Users</title>
-        
-        <para>
-        There may be times when an administrator would like to do something as
-        another user.  The <command>sudo</command> feature may be used to do 
-        this.
-        </para>
-        
-        <note>
-          <para>
-          To use the sudo feature, you must be in the
-          <emphasis>bz_sudoers</emphasis> group.  By default, all
-          administrators are in this group.</para>
-        </note>
-        
-        <para>
-        If you have access to this feature, you may start a session by
-        going to the Edit Users page, Searching for a user and clicking on 
-        their login.  You should see a link below their login name titled 
-        "Impersonate this user".  Click on the link.  This will take you 
-        to a page where you will see a description of the feature and 
-        instructions for using it.  After reading the text, simply 
-        enter the login of the user you would like to impersonate, provide 
-        a short message explaining why you are doing this, and press the 
-        button.</para>
-        
-        <para>
-        As long as you are using this feature, everything you do will be done 
-        as if you were logged in as the user you are impersonating.</para>
-        
-        <warning>
-          <para>
-          The user you are impersonating will not be told about what you are 
-          doing.  If you do anything that results in mail being sent, that 
-          mail will appear to be from the user you are impersonating.  You 
-          should be extremely careful while using this feature.</para>
-        </warning>
-      </section>
     </section>
   </section>
 
@@ -636,12 +580,12 @@
     company.</para>
 
     <para>
-    Each component has a default assignee and (if you turned it on in the parameters),
-    a QA Contact. The default assignee should be the primary person who fixes bugs in
+    Each component has a owner and (if you turned it on in the parameters),
+    a QA Contact. The owner should be the primary person who fixes bugs in
     that component. The QA Contact should be the person who will ensure
-    these bugs are completely fixed. The Assignee, QA Contact, and Reporter
+    these bugs are completely fixed. The Owner, QA Contact, and Reporter
     will get email when new bugs are created in this Component and when
-    these bugs change. Default Assignee and Default QA Contact fields only
+    these bugs change. Default Owner and Default QA Contact fields only
     dictate the 
     <emphasis>default assignments</emphasis>; 
     these can be changed on bug submission, or at any later point in
@@ -661,9 +605,9 @@
 
       <listitem>
         <para>Fill out the "Component" field, a short "Description", 
-        the "Default Assignee" and "Default QA Contact" (if enabled.) 
+        the "Initial Owner" and "Initial QA Contact" (if enabled.) 
         The Component and Description fields may contain HTML; 
-        the "Default Assignee" field must be a login name
+        the "Initial Owner" field must be a login name
         already existing in the database. 
         </para>
       </listitem>
@@ -930,7 +874,7 @@
        </para>
        <para>
          Only users with the ability to edit the bug may 
-         set flags on bugs. This includes the assignee, reporter, and 
+         set flags on bugs. This includes the owner, reporter, and 
          any user with the <computeroutput>editbugs</computeroutput> 
          permission.
        </para>
@@ -958,7 +902,7 @@
        
         <para>
           When you click on the <quote>Create a Flag Type for...</quote>
-          link, you will be presented with a form. Here is what the fields in 
+          link, you will be presented with a form. Here is what the felds in 
           the form mean:
         </para>
 
@@ -975,7 +919,7 @@
           <title>Description</title>
           <para>
             This describes the flag in more detail. At present, this doesn't
-            show up anywhere helpful; ideally, it would be nice to have
+            whos up anywhere helpful; ideally, it would be nice to have
             it show up as a tooltip. This field 
             can be as long as you like, and can contain any character you want.
           </para>
@@ -1311,9 +1255,7 @@
              resulted in a user acquiring permanent membership in a group.
              To remove a user from a group the user was in due to a regular
              expression in version 2.16 or earlier, the user must be explicitly
-             removed from the group. This can easily be done by pressing
-             buttons named 'Remove Memberships' or 'Remove Memberships
-             included in regular expression' under the table.</para>
+             removed from the group.</para>
            </note>
            <warning>
              <para>If specifying a domain in the regexp, make sure you end