anchor.diff:    _Medium_ tests represent tests that must be executed before proposing a patch.
     They are designed to run in less than 30 minutes altogether, and are quite stable in their results.
     They are designed to last less than 50 seconds individually.
  -  They can use a cluster, and each of them is executed in a separate JVM. 
  +  They can use a cluster, and each of them is executed in a separate JVM.
   
   Large Tests (((LargeTests)))::
     _Large_ tests are everything else.
     They are typically large-scale tests, regression tests for specific bugs, timeout tests, performance tests.
     They are executed before a commit on the pre-integration machines.
  -  They can be run on the developer machine as well. 
  +  They can be run on the developer machine as well.
   
   Integration Tests (((IntegrationTests)))::
     _Integration_ tests are system level tests.
  -  See <<integration.tests,integration.tests>> for more info. 
  +  See <<integration.tests,integration.tests>> for more info.
   
   [[hbase.unittests.cmds]]
   === Running tests
   
   [[hbase.unittests.cmds.test]]
  -==== Default: small and medium category tests 
  +==== Default: small and medium category tests
   
   Running `mvn test` will execute all small tests in a single JVM (no fork) and then medium tests in a separate JVM for each test instance.
   Medium tests are NOT executed if there is an error in a small test.
   Large tests are NOT executed.
  -There is one report for small tests, and one report for medium tests if they are executed. 
  +There is one report for small tests, and one report for medium tests if they are executed.
   
   [[hbase.unittests.cmds.test.runalltests]]
   ==== Running all tests
  
positive.code: sudo mount -t tmpfs -o size=2048M tmpfs /ram2G
  ----
  
  You can then use it to run all HBase tests on 2.0 with the command: 
  
  ----
  mvn test
  
negative.code: 
  Alternatively, you may limit the shell tests that run using the system variable `shell.test`.
  This value should specify the ruby literal equivalent of a particular test case by name.
  For example, the tests that cover the shell commands for altering tables are contained in the test case `AdminAlterTableTest`        and you can run them with:
  
  [source,bourne]
  ----
  