[hbase-operator-tools] branch master updated: Fix URLs; had wrong format

[st...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

stack pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hbase-operator-tools.git


The following commit(s) were added to refs/heads/master by this push:
     new 3f76ee3  Fix URLs; had wrong format
3f76ee3 is described below

commit 3f76ee3573215d22df5342c070f0d4911dee2ef3
Author: Michael Stack <st...@apache.org>
AuthorDate: Mon Oct 22 23:31:34 2018 -0700

    Fix URLs; had wrong format
---
 hbase-hbck2/README.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/hbase-hbck2/README.md b/hbase-hbck2/README.md
index 562b260..a3abd77 100644
--- a/hbase-hbck2/README.md
+++ b/hbase-hbck2/README.md
@@ -64,9 +64,10 @@ scenarios in which we use the below tooling to do various fixes.
 The Master runs all assignments, server crash handling, cluster start and
 stop, etc. In hbase-2.x, all that the Master does has been cast as
 Procedures run on a state machine engine. See
-[http://hbase.apache.org/book.html#pv2](Procedure Framework) and
-[http://hbase.apache.org/book.html#amv2](Assignment Manager) for
-detail on how this infrastructure works. Each Procedure has a
+[Procedure Framework](http://hbase.apache.org/book.html#pv2)
+and
+[Assignment Manager](http://hbase.apache.org/book.html#amv2)
+for detail on how this infrastructure works. Each Procedure has a
 Procedure `id`', it's `pid`. You can trace the lifecycle of a
 Procedure as it logs each of its macro steps denoted by its
 `pid`. Procedures start, step through states and finish. Some
@@ -107,7 +108,7 @@ there is a stuck Lock or Procedure or the count of WALs
 doesn't ever come down but only grows, then operator intervention
 is required.
 
-### The [http://hbase.apache.org/book.html#_canary](HBase Canary Tool)
+### The [HBase Canary Tool](http://hbase.apache.org/book.html#_canary)
 
 The Canary tool is useful verifying the state of assign.
 It can be run with a table focus or against the whole cluster.