List:Commits« Previous MessageNext Message »
From:paul Date:January 28 2006 5:53am
Subject:svn commit - mysqldoc@docsrva: r1076 - in trunk: . refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: paul
Date: 2006-01-28 06:53:29 +0100 (Sat, 28 Jan 2006)
New Revision: 1076

Log:
 r6800@frost:  paul | 2006-01-27 22:31:43 -0600
 General revisions.


Modified:
   trunk/
   trunk/refman-4.1/installing.xml
   trunk/refman-5.0/installing.xml
   trunk/refman-5.1/installing.xml


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6799
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2588
   + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:6800
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:2588

Modified: trunk/refman-4.1/installing.xml
===================================================================
--- trunk/refman-4.1/installing.xml	2006-01-28 05:53:13 UTC (rev 1075)
+++ trunk/refman-4.1/installing.xml	2006-01-28 05:53:29 UTC (rev 1076)
@@ -13,15 +13,15 @@
 
   <title>&title-installing;</title>
 
-  <remark role="todo">
-    each major section needs intro about what's in section.
-  </remark>
-
   <indexterm>
     <primary>installing</primary>
     <secondary>overview</secondary>
   </indexterm>
 
+  <remark role="todo">
+    each major section needs intro about what's in section.
+  </remark>
+
   <para>
     This chapter describes how to obtain and install MySQL. A summary of
     the procedure follows and later sections provide the details. If you
@@ -37,8 +37,8 @@
       <para>
         <emphasis role="bold">Determine whether your platform is
         supported.</emphasis> Please note that not all supported systems
-        are equally good for running MySQL on them. On some it is much
-        more robust and efficient than others. See
+        are equally suitable for running MySQL. On some platforms it is
+        much more robust and efficient than others. See
         <xref linkend="which-os"/>, for details.
       </para>
     </listitem>
@@ -446,15 +446,15 @@
 
       <para>
         Based on the preceding criteria, the best platforms for running
-        MySQL at this point are x86 with SuSE Linux using a 2.4 kernel,
-        and ReiserFS (or any similar Linux distribution) and SPARC with
-        Solaris (2.7-9). FreeBSD comes third, but we really hope it
-        joins the top club once the thread library is improved. We also
-        hope that at some point we is able to include into the top
-        category all other platforms on which MySQL currently compiles
-        and runs okay, but not quite with the same level of stability
-        and performance. This requires some effort on our part in
-        cooperation with the developers of the operating system and
+        MySQL at this point are x86 with SuSE Linux using a 2.4 or 2.6
+        kernel, and ReiserFS (or any similar Linux distribution) and
+        SPARC with Solaris (2.7-9). FreeBSD comes third, but we really
+        hope it joins the top club once the thread library is improved.
+        We also hope that at some point we are able to include into the
+        top category all other platforms on which MySQL currently
+        compiles and runs, but not quite with the same level of
+        stability and performance. This requires some effort on our part
+        in cooperation with the developers of the operating systems and
         library components that MySQL depends on. If you are interested
         in improving one of those components, are in a position to
         influence its development, and need more detailed instructions
@@ -484,18 +484,18 @@
 
       <remark role="todo">
         We need to define what a "release" is, i.e., when we assign a
-        new version number a produce distributions that users can grab
+        new version number and produce distributions that users can grab
         and install. Also, define "release series", and "distribution"
         (an installable package).
       </remark>
 
       <remark role="todo">
-        This needs to describe the Standard/Max/Pro/Classic breakdown
+        This needs to describe the Standard/Max/etc breakdown.
       </remark>
 
       <remark role="todo">
-        This needs to describe distribution formats as well (.tar.gz,
-        RPM, PKG, .msi)
+        This needs to describe distribution formats as well. (.tar.gz,
+        RPM, PKG, .msi, etc.)
       </remark>
 
       <para>
@@ -604,12 +604,13 @@
         </para>
 
         <para>
-          If you are running an old system and want to upgrade, but do
+          If you are running an older system and want to upgrade, but do
           not want to take the chance of having a non-seamless upgrade,
           you should upgrade to the latest version in the same release
           series you are using (where only the last part of the version
           number is newer than yours). We have tried to fix only fatal
-          bugs and make small, relatively safe changes to that version.
+          bugs and make only small, relatively <quote>safe</quote>
+          changes to that version.
         </para>
 
         <para>
@@ -624,7 +625,7 @@
           current patches and bugfixes, you can use one of our BitKeeper
           repositories. These are not <quote>releases</quote> as such,
           but are available as previews of the code on which future
-          releases are based.
+          releases are to be based.
         </para>
 
         <indexterm>
@@ -716,8 +717,8 @@
             </para>
 
             <para>
-              All API's, extern visible structures and columns for SQL
-              commands will not change during future beta, release
+              All APIs, externally visible structures, and columns for
+              SQL statements will not change during future beta, release
               candidate, or production releases.
             </para>
           </listitem>
@@ -737,8 +738,8 @@
               run for a while at many different sites with no reports of
               critical repeatable bugs other than platform-specific
               bugs. Only critical bugfixes are applied to the release.
-              This is what we call a production (stable) or `General
-              Availability' (GA) release.
+              This is what we call a production (stable) or
+              <quote>General Availability</quote> (GA) release.
             </para>
           </listitem>
 
@@ -746,9 +747,9 @@
 
         <para>
           MySQL uses a naming scheme that is slightly different from
-          most other products. In general, it is relatively safe to use
-          any version that has been out for a couple of weeks without
-          being replaced with a new version within the release series.
+          most other products. In general, it is usually safe to use any
+          version that has been out for a couple of weeks without being
+          replaced by a new version within the same release series.
         </para>
 
         <para>
@@ -855,22 +856,15 @@
               Binary distributions generally are easier to install than
               source distributions.
             </para>
+          </listitem>
 
+          <listitem>
             <remark role="todo">
               This makes a false characterization of max vs. non-max as
-            </remark>
-
-            <remark>
               transactional vs. non-transactional. Replace this with
-              descriptions
+              descriptions of Standard/Max/Pro/Classic?
             </remark>
 
-            <remark>
-              of Standard/Max/Pro/Classic?
-            </remark>
-          </listitem>
-
-          <listitem>
             <para>
               To satisfy different user requirements, we provide two
               different binary versions: one compiled with the
@@ -884,7 +878,7 @@
 
             <para>
               The extended MySQL binary distribution is marked with the
-              <option>-max</option> suffix and is configured with the
+              <literal>-max</literal> suffix and is configured with the
               same options as <command>mysqld-max</command>. See
               <xref linkend="mysqld-max"/>.
             </para>
@@ -908,9 +902,9 @@
           <listitem>
             <para>
               You want to install MySQL at some explicit location. The
-              standard binary distributions are <quote>ready to
-              run</quote> at any place, but you may want to have even
-              more flexibility to place MySQL components where you want.
+              standard binary distributions are ready to run at any
+              place, but you may want to have even more flexibility to
+              place MySQL components where you want.
             </para>
           </listitem>
 
@@ -959,7 +953,7 @@
 
               <listitem>
                 <para>
-                  <option>--with-debug[=<replaceable>full</replaceable>]</option>
+                  <option>--with-debug[=full]</option>
                 </para>
               </listitem>
 
@@ -1034,23 +1028,23 @@
         </indexterm>
 
         <para>
-          MySQL is evolving quite rapidly here at MySQL AB and we want
-          to share new developments with other MySQL users. We try to
-          make a release when we have very useful features that others
-          seem to have a need for.
+          MySQL is evolving quite rapidly and we want to share new
+          developments with other MySQL users. We try to produce a new
+          release whenever we have new and useful features that others
+          also seem to have a need for.
         </para>
 
         <para>
-          We also try to help out users who request features that are
-          easy to implement. We take note of what our licensed users
-          want to have, and we especially take note of what our support
-          customers want and try to help them out.
+          We also try to help users who request features that are easy
+          to implement. We take note of what our licensed users want,
+          and we especially take note of what our support customers want
+          and try to help them in this regard.
         </para>
 
         <para>
-          No one has to download a new release. The News section tells
-          you if the new release has something you really want. See
-          <xref linkend="news"/>.
+          No one is <emphasis>required</emphasis> to download a new
+          release. The News section tells you if the new release has
+          something you really want. See <xref linkend="news"/>.
         </para>
 
         <para>
@@ -1101,9 +1095,9 @@
 
           <listitem>
             <para>
-              If by any chance a fatal bug is found in a release, we
-              make a new release as soon as possible. (We would like
-              other companies to do this, too!)
+              If by any chance a fatal bug is found in a release, our
+              policy is to fixt it in a new release as soon as possible.
+              (We would like other companies to do this, too!)
             </para>
           </listitem>
 
@@ -1118,10 +1112,10 @@
         <para>
           We put a lot of time and effort into making our releases
           bug-free. We haven't released a single MySQL version with any
-          <emphasis>known</emphasis> <quote>fatal</quote> repeatable
-          bugs. (A <quote>fatal</quote> bug is something that crashes
-          MySQL under normal usage, produces incorrect answers for
-          normal queries, or has a security problem.)
+          <emphasis>known</emphasis> fatal repeatable bugs. (A
+          <quote>fatal</quote> bug is something that crashes MySQL under
+          normal usage, produces incorrect answers for normal queries,
+          or has a security problem.)
         </para>
 
         <para>
@@ -1130,11 +1124,11 @@
         </para>
 
         <para>
-          Our aim is to fix everything that is fixable without risk of
-          making a stable MySQL version less stable. In certain cases,
-          this means we can fix an issue in the development versions,
-          but not in the stable (production) version. Naturally, we
-          document such issues so that users are aware of them.
+          Our aim is to fix everything that is fixable without making a
+          stable MySQL version less stable. In certain cases, this means
+          we can fix an issue in the development versions, but not in
+          the stable (production) version. Naturally, we document such
+          issues so that users are aware of them.
         </para>
 
         <para>
@@ -1163,7 +1157,7 @@
               When we fix a bug, we always try to make a test case for
               it and include it into our test system to ensure that the
               bug can never recur without being detected. (About 90% of
-              all fixed bugs have a test case.)
+              all fixed bugs have test cases.)
             </para>
           </listitem>
 
@@ -1176,7 +1170,7 @@
           <listitem>
             <para>
               Before we start to build a new MySQL release, we ensure
-              that all reported repeatable bugs for the MySQL version
+              that all reported repeatable bugs for that MySQL version
               (3.23.x, 4.0.x, and so forth) are fixed. If something is
               impossible to fix (due to some internal design decision in
               MySQL), we document this in the manual. See
@@ -1218,16 +1212,17 @@
               <literal>announce</literal> mailing lists. See
               <xref linkend="mailing-lists"/>. The announcement message
               contains a list of all changes to the release and any
-              known problems with the release. The Known Problems
-              section in the release notes has been needed for only a
-              handful of releases.
+              known problems with the release. The
+              <emphasis role="bold">Known Problems</emphasis> section in
+              the release notes has been needed for only a handful of
+              releases.
             </para>
           </listitem>
 
           <listitem>
             <para>
               To quickly give our users access to the latest MySQL
-              features, we do a new MySQL release every 4-8 weeks.
+              features, we produce a new MySQL release every 4-8 weeks.
               Source code snapshots are built daily and are available at
               <ulink url="http://downloads.mysql.com/snapshots.php"/>.
             </para>
@@ -1235,12 +1230,12 @@
 
           <listitem>
             <para>
-              If, despite our best efforts, we get any bug reports after
-              the release is done that there was something critically
-              wrong with the build on a specific platform, we fix it at
-              once and build a new <literal>'a'</literal> release for
-              that platform. Thanks to our large user base, problems are
-              found quickly.
+              If, despite our best efforts, we recieve any bug reports
+              after the release is made that there is a critical problem
+              with the build on a specific platform, we fix it at once
+              and build a new <literal>'a'</literal> release for that
+              platform. Thanks to our large user base, problems are
+              found and resolved very quickly.
             </para>
           </listitem>
 
@@ -1248,7 +1243,7 @@
             <para>
               Our track record for making stable releases is quite good.
               In the last 150 releases, we had to do a new build for
-              fewer than 10 releases. In three of these cases, the bug
+              fewer than 10 of them. In three of these cases, the bug
               was a faulty <literal>glibc</literal> library on one of
               our build machines that took us a long time to track down.
             </para>
@@ -2143,24 +2138,24 @@
           checksum of the <emphasis role="bold">archive file</emphasis>
           (for example, the <literal>.zip</literal> or
           <literal>.tar.gz</literal> file) and not of the files that are
-          contained inside of the archive!
+          contained inside of the archive.
         </para>
 
         <para>
           Note that not all operating systems support the
-          <literal>md5sum</literal> command. On some, it is simply
-          called <literal>md5</literal> and others do not ship it at
-          all. On Linux, it is part of the <literal>GNU Text
-          Utilities</literal> package, which is available for a wide
-          range of platforms. You can download the source code from
+          <command>md5sum</command> command. On some, it is simply
+          called <command>md5</command> and others do not ship it at
+          all. On Linux, it is part of the <emphasis role="bold">GNU
+          Text Utilities</emphasis> package, which is available for a
+          wide range of platforms. You can download the source code from
           <ulink url="http://www.gnu.org/software/textutils/"/> as well.
-          If you have <literal>OpenSSL</literal> installed, you can also
-          use the command <literal>openssl md5 package_name</literal>
-          instead. A DOS/Windows implementation of the
-          <literal>md5</literal> command line utility is available from
-          <ulink url="http://www.fourmilab.ch/md5/"/>. A graphical MD5
-          checking tool is <literal>winMd5Sum</literal>, which can be
-          obtained from
+          If you have OpenSSL installed, you can also use the command
+          <command>openssl md5 package_name</command> instead. A
+          DOS/Windows implementation of the <command>md5</command>
+          command line utility is available from
+          <ulink url="http://www.fourmilab.ch/md5/"/>.
+          <literal>winMd5Sum</literal> is a graphical MD5 checking tool
+          which can be obtained from
           <ulink url="http://www.nullriver.com/index/products/winmd5sum"/>.
         </para>
 
@@ -2191,6 +2186,12 @@
           <ulink url="http://www.openpgp.org/"/>.
         </para>
 
+        <remark>
+          Do not use @email with the key name, that comes out as
+          &amp;lt;...&amp;gt; in some output formats, which are not part
+          of the key name.
+        </remark>
+
         <para>
           To verify the signature for a specific package, you first need
           to obtain a copy of MySQL AB's public GPG build key. You can
@@ -2247,7 +2248,7 @@
 
         <para>
           You can import the build key into your personal public GPG
-          keyring by using <literal>gpg --import</literal>. For example,
+          keyring by using <command>gpg --import</command>. For example,
           if you save the key in a file named
           <filename>mysql_pubkey.asc</filename>, the import command
           looks like this:
@@ -2312,8 +2313,8 @@
 
         <para>
           The <literal>Good signature</literal> message indicates that
-          everything is all right. You can ignore the <literal>insecure
-          memory</literal> warning.
+          everything is all right. You can ignore any <literal>insecure
+          memory</literal> warning you might obtain.
         </para>
 
       </section>
@@ -2454,8 +2455,8 @@
       </informaltable>
 
       <para>
-        Installations created from Linux RPM distributions result in
-        files under the following system directories:
+        Installations created from MySQL AB's Linux RPM distributions
+        result in files under the following system directories:
       </para>
 
       <informaltable>
@@ -2608,7 +2609,7 @@
       </informaltable>
 
       <para>
-        Within an installation directory, the layout of a source
+        Within its installation directory, the layout of a source
         installation differs from that of a binary installation in the
         following ways:
       </para>
@@ -2688,13 +2689,10 @@
     <title>&title-windows-installation;</title>
 
     <remark role="todo">
-      The prompt is inconsistent in the Windows sections. Sometimes
+      The prompt is inconsistent in the Windows sections. Sometimes it
+      begins with C:, sometimes it's shell&amp;gt;.
     </remark>
 
-    <remark>
-      begins with C:, sometimes it is shell&amp;gt;.
-    </remark>
-
     <para>
       A native Windows version of MySQL has been available from MySQL AB
       since version 3.21 and represents a sizable percentage of the
@@ -2711,8 +2709,8 @@
     </para>
 
     <para>
-      If you have installed a version of MySQL prior to version 4.1.5,
-      you must perform the following steps:
+      If you are upgrading an existing installation of MySQL prior to
+      version 4.1.5, you must perform the following steps:
     </para>
 
     <orderedlist>
@@ -2785,8 +2783,8 @@
 
     <para>
       Generally speaking, you should use the binary distribution. It is
-      simpler, and you need no additional tools to get MySQL up and
-      running.
+      simpler to use than the others, and you need no additional tools
+      to get MySQL up and running.
     </para>
 
     <para>
@@ -2881,7 +2879,7 @@
         <listitem>
           <para>
             If you need tables with a size larger than 4GB, install
-            MySQL on an NTFS or newer filesystem. Do not forget to use
+            MySQL on an NTFS or newer filesystem. Don't forget to use
             <literal>MAX_ROWS</literal> and
             <literal>AVG_ROW_LENGTH</literal> when you create tables.
             See <xref linkend="create-table"/>.
@@ -3001,12 +2999,12 @@
         <title>&title-mysql-install-wizard-introduction;</title>
 
         <para>
-          MySQL Installation Wizard is a new installer for the MySQL
-          server that uses the latest installer technologies for
-          Microsoft Windows. The MySQL Installation Wizard, in
-          combination with the MySQL Configuration Wizard, allows a user
-          to install and configure a MySQL server that is ready for use
-          immediately after installation.
+          MySQL Installation Wizard is an installer for the MySQL server
+          that uses the latest installer technologies for Microsoft
+          Windows. The MySQL Installation Wizard, in combination with
+          the MySQL Configuration Wizard, allows a user to install and
+          configure a MySQL server that is ready for use immediately
+          after installation.
         </para>
 
         <para>
@@ -3021,12 +3019,11 @@
 
         <para>
           Microsoft has included an improved version of their Microsoft
-          Windows Installer (MSI) in the recent versions of Windows.
-          Using the MSI has become the de-facto standard for application
-          installations on Windows 2000, Windows XP, and Windows Server
-          2003. The MySQL Installation Wizard makes use of this
-          technology to provide a smoother and more flexible
-          installation progress.
+          Windows Installer (MSI) in the recent versions of Windows. MSI
+          has become the de-facto standard for application installations
+          on Windows 2000, Windows XP, and Windows Server 2003. The
+          MySQL Installation Wizard makes use of this technology to
+          provide a smoother and more flexible installation process.
         </para>
 
         <para>
@@ -3040,12 +3037,12 @@
         </para>
 
         <para>
-          Further, Microsoft has introduced the WiX (Windows Installer
-          XML) tool set recently. It is the first highly acknowledged
-          Open Source project from Microsoft. We switched to WiX because
-          it is an Open Source project and it allows us to handle the
-          complete Windows installation process in a flexible way with
-          scripts.
+          In addition, Microsoft has introduced the WiX (Windows
+          Installer XML) toolkit recently. This is the first highly
+          acknowledged Open Source project from Microsoft. We have
+          switched to WiX because it is an Open Source project and it
+          allows us to handle the complete Windows installation process
+          in a flexible manner using scripts.
         </para>
 
         <para>
@@ -9406,7 +9403,7 @@
           <listitem>
             <para>
               Unpack the source distribution in the aforementioned
-              directory using <literal>WinZip</literal> or other Windows
+              directory using <command>WinZip</command> or other Windows
               tool that can read <filename>.zip</filename> files.
             </para>
           </listitem>
@@ -9433,9 +9430,8 @@
 
           <listitem>
             <para>
-              From the <guimenu/><literal>Build</literal> menu, select
-              the <guisubmenu>Set Active Configuration</guisubmenu>
-              menu.
+              From the <guimenu>Build</guimenu> menu, select the
+              <guisubmenu>Set Active Configuration</guisubmenu> menu.
             </para>
           </listitem>
 
@@ -9574,14 +9570,15 @@
 </programlisting>
 
             <para>
-              Benchmarking requires Perl support.
+              Benchmarking requires Perl support. See
+              <xref linkend="perl-support"/>.
             </para>
           </listitem>
 
           <listitem>
             <para>
               From the <filename>workdir</filename> directory, copy into
-              the <literal>C:\mysql</literal> directory the following
+              the <filename>C:\mysql</filename> directory the following
               directories:
             </para>
 
@@ -10393,7 +10390,7 @@
           <para>
             At this point, you should have the server running. However,
             none of the initial MySQL accounts have a password, so you
-            should assign passwords using the instructions in
+            should assign passwords using the instructions found in
             <xref linkend="default-privileges"/>.
           </para>
         </listitem>

Modified: trunk/refman-5.0/installing.xml
===================================================================
--- trunk/refman-5.0/installing.xml	2006-01-28 05:53:13 UTC (rev 1075)
+++ trunk/refman-5.0/installing.xml	2006-01-28 05:53:29 UTC (rev 1076)
@@ -717,8 +717,8 @@
             </para>
 
             <para>
-              All API's, externally visible structures and columns for
-              SQL commands will not change during future beta, release
+              All APIs, externally visible structures, and columns for
+              SQL statements will not change during future beta, release
               candidate, or production releases.
             </para>
           </listitem>
@@ -1225,12 +1225,12 @@
 
           <listitem>
             <para>
-              If, despite our best efforts, we receive any bug reports
-              after the release is made a critical problem with that
-              build on a specific platform, we fix it at once and build
-              a new <literal>'a'</literal> release for that platform.
-              Thanks to our large user base, any such problems are found
-              and resolved very quickly.
+              If, despite our best efforts, we recieve any bug reports
+              after the release is made that there is a critical problem
+              with the build on a specific platform, we fix it at once
+              and build a new <literal>'a'</literal> release for that
+              platform. Thanks to our large user base, problems are
+              found and resolved very quickly.
             </para>
           </listitem>
 
@@ -2685,10 +2685,7 @@
     <title>&title-windows-installation;</title>
 
     <remark role="todo">
-      The prompt is inconsistent in the Windows sections. Sometimes
-    </remark>
-
-    <remark>
+      The prompt is inconsistent in the Windows sections. Sometimes it
       begins with C:, sometimes it's shell&amp;gt;.
     </remark>
 
@@ -9796,7 +9793,7 @@
       <para>
         Before setting up passwords, you might want to try running some
         client programs to make sure that you can connect to the server
-        and that it is operating properly. Make sure the server is
+        and that it is operating properly. Make sure that the server is
         running (see <xref linkend="windows-server-first-start"/>), and
         then issue the following commands to verify that you can
         retrieve information from the server. The output should be
@@ -9854,10 +9851,10 @@
       <para>
         After installing MySQL on Unix, you need to initialize the grant
         tables, start the server, and make sure that the server works
-        okay. You may also wish to arrange for the server to be started
-        and stopped automatically when your system starts and stops. You
-        should also assign passwords to the accounts in the grant
-        tables.
+        satisfactorily. You may also wish to arrange for the server to
+        be started and stopped automatically when your system starts and
+        stops. You should also assign passwords to the accounts in the
+        grant tables.
       </para>
 
       <para>

Modified: trunk/refman-5.1/installing.xml
===================================================================
--- trunk/refman-5.1/installing.xml	2006-01-28 05:53:13 UTC (rev 1075)
+++ trunk/refman-5.1/installing.xml	2006-01-28 05:53:29 UTC (rev 1076)
@@ -717,8 +717,8 @@
             </para>
 
             <para>
-              All API's, externally visible structures and columns for
-              SQL commands will not change during future beta, release
+              All APIs, externally visible structures, and columns for
+              SQL statements will not change during future beta, release
               candidate, or production releases.
             </para>
           </listitem>
@@ -1225,12 +1225,12 @@
 
           <listitem>
             <para>
-              If, despite our best efforts, we receive any bug reports
-              after the release is made a critical problem with that
-              build on a specific platform, we fix it at once and build
-              a new <literal>'a'</literal> release for that platform.
-              Thanks to our large user base, any such problems are found
-              and resolved very quickly.
+              If, despite our best efforts, we recieve any bug reports
+              after the release is made that there is a critical problem
+              with the build on a specific platform, we fix it at once
+              and build a new <literal>'a'</literal> release for that
+              platform. Thanks to our large user base, problems are
+              found and resolved very quickly.
             </para>
           </listitem>
 
@@ -9798,7 +9798,7 @@
       <para>
         Before setting up passwords, you might want to try running some
         client programs to make sure that you can connect to the server
-        and that it is operating properly. Make sure the server is
+        and that it is operating properly. Make sure that the server is
         running (see <xref linkend="windows-server-first-start"/>), and
         then issue the following commands to verify that you can
         retrieve information from the server. The output should be
@@ -9856,10 +9856,10 @@
       <para>
         After installing MySQL on Unix, you need to initialize the grant
         tables, start the server, and make sure that the server works
-        okay. You may also wish to arrange for the server to be started
-        and stopped automatically when your system starts and stops. You
-        should also assign passwords to the accounts in the grant
-        tables.
+        satisfactorily. You may also wish to arrange for the server to
+        be started and stopped automatically when your system starts and
+        stops. You should also assign passwords to the accounts in the
+        grant tables.
       </para>
 
       <para>
@@ -11395,7 +11395,11 @@
               <para>
                 On Windows, one <literal>root</literal> account is
                 created; this account allows connecting from the local
-                host only.
+                host only. The Windows installer will optionally create
+                an account allowing for connections from any host only
+                if the user selects the <guilabel>Enable root access
+                from remote machines</guilabel> option during
+                installation.
               </para>
             </listitem>
 

Thread
svn commit - mysqldoc@docsrva: r1076 - in trunk: . refman-4.1 refman-5.0 refman-5.1paul28 Jan