From 3e95a48e7bcd25d2cdc64712d74d2aafe3e7f693 Mon Sep 17 00:00:00 2001
From: Jeff Mitchell <jeffrey.mitchell@gmail.com>
Date: Mon, 21 May 2018 16:30:45 -0400
Subject: [PATCH] Remove dupe website text

---
 .../api/system/rekey-recovery-key.html.md     | 35 +------------------
 1 file changed, 1 insertion(+), 34 deletions(-)

diff --git a/website/source/api/system/rekey-recovery-key.html.md b/website/source/api/system/rekey-recovery-key.html.md
index 63f6239461..379fa0ddae 100644
--- a/website/source/api/system/rekey-recovery-key.html.md
+++ b/website/source/api/system/rekey-recovery-key.html.md
@@ -187,7 +187,7 @@ call.
 
 When the operation is complete, this will return a response like the example
 below; otherwise the response will be the same as the `GET` method against
-`sys/rekey-recovery-key/init`, providing status on the operation itself.
+`sys/rekey/init`, providing status on the operation itself.
 
 If verification was requested, successfully completing this flow will
 immediately put the operation into a verification state, and provide the nonce
@@ -274,39 +274,6 @@ threshold required for the new shares to pass verification. `progress` is how
 many of the new unseal keys have been provided for this verification operation.
 The `nonce` for the current rekey operation is also displayed.
 
-## Read Rekey Recovery Key Verification Progress
-
-This endpoint reads the configuration and progress of the current rekey
-verification attempt.
-
-| Method   | Path                                        | Produces               |
-| :------- | :------------------------------------------ | :--------------------- |
-| `GET`    | `/sys/rekey-recovery-key/verify`            | `200 application/json` |
-
-### Sample Request
-
-```
-$ curl \
-    --header "X-Vault-Token: ..." \
-    http://127.0.0.1:8200/v1/sys/rekey-recovery-key/verify
-```
-
-### Sample Response
-
-```json
-{
-  "nonce": "8b112c9e-2738-929d-bcc2-19aff249ff10",
-  "t": 3,
-  "n": 5,
-  "progress": 1
-}
-```
-
-`n` is the total number of new shares that were generated and `t` is the
-threshold required for the new shares to pass verification. `progress` is how
-many of the new unseal keys have been provided for this verification operation.
-The `nonce` for the current rekey operation is also displayed.
-
 ## Cancel Rekey Verification
 
 This endpoint cancels any in-progress rekey verification operation. This clears