List:Commits« Previous MessageNext Message »
From:jon Date:April 7 2006 8:02am
Subject:svn commit - mysqldoc@docsrva: r1752 - in trunk: refman-4.1 refman-5.0
View as plain text  
Author: jstephens
Date: 2006-04-07 10:02:33 +0200 (Fri, 07 Apr 2006)
New Revision: 1752

Log:

"Share-nothing" -> "Shared-nothing" (forgot to fix in 4.1/5.0 Manuals).



Modified:
   trunk/refman-4.1/ndbcluster.xml
   trunk/refman-5.0/ndbcluster.xml

Modified: trunk/refman-4.1/ndbcluster.xml
===================================================================
--- trunk/refman-4.1/ndbcluster.xml	2006-04-07 02:19:14 UTC (rev 1751)
+++ trunk/refman-4.1/ndbcluster.xml	2006-04-07 08:02:33 UTC (rev 1752)
@@ -96,8 +96,8 @@
 
     <para>
       <firstterm>MySQL Cluster</firstterm> is a technology that enables
-      clustering of in-memory databases in a share-nothing system. The
-      share-nothing architecture allows the system to work with very
+      clustering of in-memory databases in a shared-nothing system. The
+      shared-nothing architecture allows the system to work with very
       inexpensive hardware, and without any specific requirements on
       hardware or software. It also does not have any single point of
       failure because each component has its own memory and disk.
@@ -10741,7 +10741,7 @@
         <para>
           This refers to a group of computers working together using the
           <literal>NDB</literal> storage engine to support a distributed
-          MySQL database in a <emphasis>share-nothing
+          MySQL database in a <emphasis>shared-nothing
           architecture</emphasis> using <emphasis>in-memory
           storage</emphasis>.
         </para>
@@ -11129,12 +11129,12 @@
 
       <listitem>
         <para>
-          <emphasis role="bold">Share-nothing architecture</emphasis>:
+          <emphasis role="bold">shared-nothing architecture</emphasis>:
         </para>
 
         <para>
           The ideal architecture for a MySQL Cluster. In a true
-          share-nothing setup, each node runs on a separate host. The
+          shared-nothing setup, each node runs on a separate host. The
           advantage such an arrangement is that there no single host or
           node can act as single point of failure or as a performance
           bottle neck for the system as a whole.

Modified: trunk/refman-5.0/ndbcluster.xml
===================================================================
--- trunk/refman-5.0/ndbcluster.xml	2006-04-07 02:19:14 UTC (rev 1751)
+++ trunk/refman-5.0/ndbcluster.xml	2006-04-07 08:02:33 UTC (rev 1752)
@@ -96,8 +96,8 @@
 
     <para>
       <firstterm>MySQL Cluster</firstterm> is a technology that enables
-      clustering of in-memory databases in a share-nothing system. The
-      share-nothing architecture allows the system to work with very
+      clustering of in-memory databases in a shared-nothing system. The
+      shared-nothing architecture allows the system to work with very
       inexpensive hardware, and without any specific requirements on
       hardware or software. It also does not have any single point of
       failure because each component has its own memory and disk.
@@ -11035,7 +11035,7 @@
         <para>
           This refers to a group of computers working together using the
           <literal>NDB</literal> storage engine to support a distributed
-          MySQL database in a <emphasis>share-nothing
+          MySQL database in a <emphasis>shared-nothing
           architecture</emphasis> using <emphasis>in-memory
           storage</emphasis>.
         </para>
@@ -11423,12 +11423,12 @@
 
       <listitem>
         <para>
-          <emphasis role="bold">Share-nothing architecture</emphasis>:
+          <emphasis role="bold">shared-nothing architecture</emphasis>:
         </para>
 
         <para>
           The ideal architecture for a MySQL Cluster. In a true
-          share-nothing setup, each node runs on a separate host. The
+          shared-nothing setup, each node runs on a separate host. The
           advantage such an arrangement is that there no single host or
           node can act as single point of failure or as a performance
           bottle neck for the system as a whole.

Thread
svn commit - mysqldoc@docsrva: r1752 - in trunk: refman-4.1 refman-5.0jon7 Apr