Jeff Zaroyko : wineusr: Minor improvements to the introduction.

[Alexandre Julliard]

Module: docs
Branch: master
Commit: 5a02bc4930b31513b614cc52d2087c182df9cc2f
URL:    http://source.winehq.org/git/docs.git/?a=commit;h=5a02bc4930b31513b614cc52d2...

Author: Jeff Zaroyko 
Date:   Fri Jul 16 13:09:58 2010 +1000

wineusr: Minor improvements to the introduction.

---

en/wineusr-introduction.sgml |   51 +++++++++++++++++++++++++----------------
 1 files changed, 31 insertions(+), 20 deletions(-)

diff --git a/en/wineusr-introduction.sgml b/en/wineusr-introduction.sgml
index 4b326dd..ea087cd 100644
--- a/en/wineusr-introduction.sgml
+++ b/en/wineusr-introduction.sgml
@@ -19,17 +19,18 @@
       <sect2>
         <title>Further questions and comments</title>
         <para>
-          If, after examining this guide, the FAQ, and other relevant
-          documentation there is still something you cannot figure out,
-          we would love to hear from you.  The <ulink
-          url="http://www.winehq.org/site/forums%22%3Emailing lists</ulink>
-          section contains several mailing lists and an IRC channel, all
-          of which are great places to seek help and offer suggestions.
-          If you are particularly savvy, and believe that something can be
-          explained better, you can file a <ulink
-          url="http://bugs.winehq.org/%22%3Ebug report</ulink> or <ulink
-          url="http://wiki.winehq.org/SubmittingPatches%22%3Epost a
-          patch</ulink> on Wine's documentation itself.
+          If, after examining this guide,
+          the <ulink url="http://wiki.winehq.org/FAQ">FAQ</ulink>, and
+          other relevant documentation there is still something you
+          cannot figure out, we would love to hear from you.
+          The <ulink url="http://www.winehq.org/site/forums">mailing
+          lists</ulink> section contains several mailing lists and an
+          IRC channel, all of which are great places to seek help and
+          offer suggestions.  If you are particularly savvy, and
+          believe that something can be explained better, you can file
+          a <ulink url="http://bugs.winehq.org/">bug report</ulink>
+          or <ulink url="http://wiki.winehq.org/SubmittingPatches">post
+          a patch</ulink> on Wine's documentation itself.
         </para>
       </sect2>

@@ -64,20 +65,28 @@
                 linkend="getting-wine">Getting Wine</link> and see 
                 the <ulink url="http://www.winehq.org/site/download">Wine 
                 Downloads</> page. For the casual or new user the simplest 
-                is to get an rpm distribution.    
+                is to get a packaged version for your distribution.
               </para>
             </listitem>
             <listitem>
               <para>
-                Configure wine using the <link 
+                Optionally configure wine using the <link 
                 linkend="config-wine-main"><emphasis><filename>winecfg</></>
-                </link> command. For most people wine should now be usable.         
+                </link> command. Wine should work without any
+                additional configuration options.
               </para>
             </listitem>
             <listitem>
               <para>
-                To test your installation run wine's Windows 3.1 like file 
-                manager using the <filename>wine winefile</> command.
+                To test your installation run wine's notepad clone
+                using the <filename>wine notepad</> command.
+              </para>
+            </listitem>
+            <listitem>
+              <para>
+              Check the Wine <ulink url="http://appdb.winehq.org">AppDB</ulink>
+              for specific instructions or steps required to install or run
+              your application.
               </para>
             </listitem>
             <listitem>
@@ -87,9 +96,10 @@
                 <filename>filespec/appname.exe</></></link> command.
               </para>
               <para>
-                The first command you will run will be to install a package. 
+                The first command you will run will be to install an application.
                 Typically something like <filename>wine 
-                /media/cdrom/setup.exe</> or the equivalent.
+                /media/cdrom/setup.exe</> or the equivalent path might be used
+                to install an application from CD.
               </para>
             </listitem>
           </itemizedlist>
@@ -202,7 +212,7 @@
             </listitem>
             <listitem>
               <para>
-                Support for alternative input devices 
+                Support for alternative input devices such as graphics tablets.
               </para>
             </listitem>
             <listitem>
@@ -326,7 +336,8 @@
           and filesharing programs have very good open source equivalents.
           Furthermore, a sizable number of Windows programs have been
           ported to Linux directly, eliminating the need for Wine (or
-          Windows) entirely.
+          Windows) entirely.  These alternatives should be found through
+          your system's package management facilities.
         </para>
       </sect2>
       <sect2>