diff --git a/hbase-server/src/main/javadoc/org/apache/hadoop/hbase/replication/package.html b/hbase-server/src/main/javadoc/org/apache/hadoop/hbase/replication/package.html
index b97a1a6..4e8122b 100644
--- a/hbase-server/src/main/javadoc/org/apache/hadoop/hbase/replication/package.html
+++ b/hbase-server/src/main/javadoc/org/apache/hadoop/hbase/replication/package.html
@@ -71,7 +71,7 @@ Before trying out replication, make sure to review the following requirements:
Zookeeper clusters.
Both clusters should have the same HBase and Hadoop major revision.
For example, having 0.90.1 on the master and 0.90.0 on the slave is
- correct but not 0.90.1 and 0.89.20100725.
+ correct but not 0.90.1 and 0.94.0.
Every table that contains families that are scoped for replication
should exist on every cluster with the exact same name, same for those
replicated families.
@@ -133,14 +133,21 @@ Choosing peer 10.10.1.49:62020
In this case it indicates that 1 region server from the slave cluster
was chosen for replication.
-Should you want to stop the replication while the clusters are running, open
-the shell on the master cluster and issue this command:
-
-hbase(main):001:0> stop_replication
+Kill Switch
+
+A kill switch was built-in in order to stop everything related to replication
+on the local cluster.
-Replication of already queued edits will still happen after you
-issued that command but new entries won't be. To start it back, simply replace
-"false" with "true" in the command.
+
+hbase(main):001:0> help 'stop_replication'
+Stops all the replication features. The state in which each
+stream stops in is undetermined.
+WARNING:
+start/stop replication is only meant to be used in critical load situations.
+Examples:
+
+ hbase> stop_replication
+