[gdm] Fixes for docs. Fixes bug #598338 and some other issues I noticed.

[Brian Cameron <bcameron src gnome org>]

commit faee7a7d8356b7b25be0632dbf40a9ee55683670
Author: Brian Cameron <Brian Cameron sun com>
Date:   Fri Oct 30 21:28:08 2009 -0500

    Fixes for docs.  Fixes bug #598338 and some other issues I noticed.

 docs/C/gdm.xml |   91 ++++++++++---------------------------------------------
 1 files changed, 17 insertions(+), 74 deletions(-)
---
diff --git a/docs/C/gdm.xml b/docs/C/gdm.xml
index 56d1360..3427707 100644
--- a/docs/C/gdm.xml
+++ b/docs/C/gdm.xml
@@ -1139,7 +1139,7 @@ TimedLogin=you
             <listitem>
               <synopsis>MulticastAddr=ff02::1</synopsis>
               <para>
-                This is the Link-local Multicast address.
+                This is the Link-local multicast address.
               </para>
             </listitem>
           </varlistentry>
@@ -1149,20 +1149,6 @@ TimedLogin=you
       <sect3 id="daemonsection">
         <title>[daemon]</title>
         <variablelist>
-
-          <varlistentry>
-            <term>Group</term>
-            <listitem>
-              <synopsis>Group=gdm</synopsis>
-              <para>
-                The group name under which the greeter and other GUI programs
-                are run.  Refer to the <filename>User</filename>
-                configuration key and to the "Security->GDM User And
-                Group" section of this document for more information.
-              </para>
-            </listitem>
-          </varlistentry>
-          
           <varlistentry>
             <term>TimedLoginEnable</term>
             <listitem>
@@ -1265,6 +1251,19 @@ TimedLogin=you
               </para>
             </listitem>
           </varlistentry>
+
+          <varlistentry>
+            <term>Group</term>
+            <listitem>
+              <synopsis>Group=gdm</synopsis>
+              <para>
+                The group name under which the greeter and other GUI programs
+                are run.  Refer to the <filename>User</filename>
+                configuration key and to the "Security->GDM User And
+                Group" section of this document for more information.
+              </para>
+            </listitem>
+          </varlistentry>
         </variablelist>
       </sect3>
 
@@ -1563,62 +1562,6 @@ gdm:.my.domain
           </varlistentry>
 
           <varlistentry>
-            <term>/apps/gdm/simple-greeter/include</term>
-            <listitem>
-              <synopsis>[] (string list)</synopsis>
-              <para>
-               Set to a list of users to always include in the Face Browser.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
-            <term>/apps/gdm/simple-greeter/include_all</term>
-            <listitem>
-              <synopsis>true (boolean)</synopsis>
-              <para>
-                If true, then the face browser will show all users on the
-                local machine.  If false, the face browser will only show
-                users who have recently logged in.
-              </para>
-              <para>
-               To provide more detail on how this option works. When this key
-               is true, GDM will call fgetpwent() to get a list of local users
-               on the system.  The Face Browser also will display any users
-               that have previously logged in on the system (for example
-               NIS/LDAP users).  It gets this list via calling the ck-history
-               ConsoleKit interface.  It will also filter out any users which
-               do not have a valid shell (valid shells are any shell that
-               getusershell() returns.  <filename>/sbin/nologin</filename> or
-               <filename>/bin/false</filename> are considered invalid shells
-               even if getusershell() returns them).
-              </para>
-
-              <para>
-               If false, then GDM more simply only displays users that have 
-               previously logged in on the system (local or NIS/LDAP users) by
-               calling the ck-history ConsoleKit interface.
-              </para>
-
-              <para>
-               In both cases, GDM filters out any users with a UID less than
-               500 (or 100 if running on Solaris).  Such users are considered
-               system users.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
-            <term>/apps/gdm/simple-greeter/exclude</term>
-            <listitem>
-              <synopsis>[] (string list)</synopsis>
-              <para>
-                Set to a list of users to always exclude in the Face Browser.
-              </para>
-            </listitem>
-          </varlistentry>
-
-          <varlistentry>
             <term>/apps/gdm/simple-greeter/logo_icon_name</term>
             <listitem>
               <synopsis>computer (string)</synopsis>
@@ -1694,7 +1637,7 @@ gdm:.my.domain
       </para>
 
       <sect3 id="accessibilitydialog">
-        <title>GDM Accessibility Dialog And Gconf Keys</title>
+        <title>GDM Accessibility Dialog And GConf Keys</title>
 
         <para>
          The GDM greeter panel at the login screen displays an accessibility
@@ -1721,7 +1664,7 @@ gdm:.my.domain
          The other checkboxes in the GDM Accessibility Dialog do not have
          corresponding GConf keys because no additional program is launched to
          provide the accessibility features that they offer.  These other
-         options coorespond to accessibility features that are provided by the
+         options correspond to accessibility features that are provided by the
          Xserver, which is always running during the GDM session.
         </para>
       </sect3>
@@ -1806,7 +1749,7 @@ AutostartCondition=GNOME /desktop/gnome/applications/at/screen_reader_enabled
 </screen>
 
         <para>
-         When an accesibility key is true, then any program which is linked to
+         When an accessibility key is true, then any program which is linked to
          that key in a GDM autostart desktop file will be launched (unless the
          Hidden key is set to true in that desktop file).  A single GConf key
          can even start multiple assistive tools if there are multiple desktop