List:Commits« Previous MessageNext Message »
From:mcbrown Date:July 31 2007 4:00pm
Subject:svn commit - mysqldoc@docsrva: r7286 - trunk/refman-5.0
View as plain text  
Author: mcbrown
Date: 2007-07-31 18:00:23 +0200 (Tue, 31 Jul 2007)
New Revision: 7286

Log:
Some typo corrections



Modified:
   trunk/refman-5.0/ha.xml


Modified: trunk/refman-5.0/ha.xml
===================================================================
--- trunk/refman-5.0/ha.xml	2007-07-31 15:58:41 UTC (rev 7285)
+++ trunk/refman-5.0/ha.xml	2007-07-31 16:00:23 UTC (rev 7286)
Changed blocks: 8, Lines Added: 9, Lines Deleted: 9; 3707 bytes

@@ -14,7 +14,7 @@
     your MySQL installation. Availability refers to the ability to cope with,
     and if necessary recover from, failures on the host, including failures of
     MySQL, the operating system or the hardware. Scalability refers to the
-    abiloity to spread the load of your application queries across multiple
+    ability to spread the load of your application queries across multiple
     MySQL servers. As your application and usage increases, you may need to
     spread the queries for the application across multiple servers to improve
     response times. 

@@ -22,8 +22,8 @@
   <para>
     There are a number of solutions available for
     solving issues of availability and scalability. There are two
-    primary solutions supported bgy MySQL, MySQL Replication and MySQL
-    Cluster. Further options are availabile using third-party solutions
+    primary solutions supported by MySQL, MySQL Replication and MySQL
+    Cluster. Further options are available using third-party solutions
     such as DRBD and Heartbeat, and more complex scenarios can be solved
     through a combination of these technologies. These different tools
     work in different ways:

@@ -38,7 +38,7 @@
         instance. Without using more complex setups, data can only be
         replicated from a single master server to any number of slaves.
         The replication is asynchronous, so the synchronization does not
-        take place in real time, and there is no gurantee that data from
+        take place in real time, and there is no guarantee that data from
         the master will have been replicated to the slaves.
       </para>
 

@@ -72,7 +72,7 @@
             Data can be replicated from one master to any number of
             slaves, making replication suitable in environments with
             heavy reads, but light writes (for example, many web
-            applications) by spreading the laod across multiple slaves.
+            applications) by spreading the load across multiple slaves.
           </para>
         </listitem>
 

@@ -182,7 +182,7 @@
           <para>
             Provides automatic failover between nodes. Only transaction
             information for the active node being used is lost in the
-            event oif a failure.
+            event of a failure.
           </para>
         </listitem>
 

@@ -255,7 +255,7 @@
 
       <para>
         Because the block device, not the data you are storing on it, is
-        being replicated the validty of the information is more reliable
+        being replicated the validity of the information is more reliable
         than with data-only replication solutions. DRBD can also ensure
         data integrity by only returning from a write operation on the
         primary server when the data has been written to the underlying

@@ -323,7 +323,7 @@
       </itemizedlist>
 
       <para>
-        For more information on configuring DRBD and confguring MySQL
+        For more information on configuring DRBD and configuring MySQL
         for use with a DRBD device, see
         <xref linkend="replication-drbd"/>.
       </para>

@@ -334,7 +334,7 @@
         Heartbeat is not a data replication solution, but a solution for
         monitoring servers and switching active MySQL servers
         automatically in the event of failure. Heartbeat needs to be
-        combined with MySQL Replication or DRBD to provide automatica
+        combined with MySQL Replication or DRBD to provide automatic
         failover.
       </para>
     </listitem>


Thread
svn commit - mysqldoc@docsrva: r7286 - trunk/refman-5.0mcbrown31 Jul