From c52469aad9bffd41ecb32641fa2dc4e67b085ea1 Mon Sep 17 00:00:00 2001
From: Doug Meil <dmeil@apache.org>
Date: Tue, 11 Oct 2011 23:16:10 +0000
Subject: [PATCH] HBASE-4576 book.xml,ops_mgt.xml - moved cluster repl into
 OpsMgt chapter.

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1182139 13f79535-47bb-0310-9956-ffa450edef68
---
 src/docbkx/book.xml    | 10 ++--------
 src/docbkx/ops_mgt.xml |  7 +++++++
 2 files changed, 9 insertions(+), 8 deletions(-)

diff --git a/src/docbkx/book.xml b/src/docbkx/book.xml
index 0368718fb31..afa2c047deb 100644
--- a/src/docbkx/book.xml
+++ b/src/docbkx/book.xml
@@ -602,14 +602,14 @@ admin.enableTable(table);
       "a lot" of versions of a row to be retained (e.g., where it is significantly above the HBase default of 3 max versions).  The 
       rows-approach would require storing a timstamp in some portion of the rowkey so that they would not overwite with each successive update.
       </para>
-      <para>Winner:  Rows (generally speaking).
+      <para>Preference:  Rows (generally speaking).
       </para>
     </section>
     <section xml:id="schema.smackdown.rowscols"><title>Rows vs. Columns</title>
       <para>Another common question is whether one should prefer rows or columns.  The context is typically in extreme cases of wide
       tables, such as having 1 row with 1 million attributes, or 1 million rows with 1 columns apiece.  
       </para>
-      <para>Winner:  Rows (generally speaking).  To be clear, this guideline is in the context is in extremely wide cases, not in the 
+      <para>Preference:  Rows (generally speaking).  To be clear, this guideline is in the context is in extremely wide cases, not in the 
       standard use-case where one needs to store a few dozen or hundred columns.
       </para>
     </section>
@@ -681,12 +681,6 @@ admin.enableTable(table);
    </section>
   </chapter>
 
-  <chapter xml:id="cluster_replication">
-  <title>Cluster Replication</title>
-  <para>See <link xlink:href="http://hbase.apache.org/replication.html">Cluster Replication</link>.
-  </para>
-  </chapter>
-
   <chapter xml:id="datamodel">
     <title>Data Model</title>
     <para>In short, applications store data into an HBase table.
diff --git a/src/docbkx/ops_mgt.xml b/src/docbkx/ops_mgt.xml
index 1101ed88f35..ce445d67778 100644
--- a/src/docbkx/ops_mgt.xml
+++ b/src/docbkx/ops_mgt.xml
@@ -251,6 +251,13 @@ false
     <para>TODO
     </para>
   </section>
+  
+  <section xml:id="cluster_replication">
+    <title>Cluster Replication</title>
+    <para>See <link xlink:href="http://hbase.apache.org/replication.html">Cluster Replication</link>.
+    </para>
+  </section>
+  
   <section xml:id="ops.backup">
     <title >HBase Backup</title>
     <para>There are two broad strategies for performing HBase backups: backing up with a full cluster shutdown, and backing up on a live cluster.