Documentation update

website/source/docs/auth/token.html.md

@@ -459,40 +459,6 @@ of the header should be "X-Vault-Token" and the value should be the token.
   </dd>
 </dl>
 
-### /auth/token/revoke-prefix[/prefix]
-#### POST
-
-<dl class="api">
-  <dt>Description</dt>
-  <dd>
-    Revokes all tokens generated at a given prefix, along with child tokens,
-    and all secrets generated using those tokens. Uses include revoking all
-    tokens generated by a credential backend during a suspected compromise.
-    This is a root-protected endpoint.
-  </dd>
-
-  <dt>Method</dt>
-  <dd>POST</dd>
-
-  <dt>URL</dt>
-  <dd>`/auth/token/revoke-prefix</prefix>`</dd>
-
-  <dt>Parameters</dt>
-  <dd>
-    <ul>
-      <li>
-        <span class="param">token</span>
-        <span class="param-flags">required</span>
-            Token source prefix to revoke. This can be part of the URL or the body.
-      </li>
-    </ul>
-  </dd>
-
-  <dt>Returns</dt>
-  <dd>`204` response code.
-  </dd>
-</dl>
-
 ### /auth/token/roles/[role_name]
 
 #### DELETE 
@@ -599,7 +565,7 @@ of the header should be "X-Vault-Token" and the value should be the token.
     available or would require `sudo`/root privileges to access. Role
     parameters, when set, override any provided options to the `create`
     endpoints. The role name is also included in the token path, allowing all
-    tokens created against a role to be revoked using the `revoke-prefix`
+    tokens created against a role to be revoked using the `sys/revoke-prefix`
     endpoint.
   </dd>
 
@@ -645,7 +611,7 @@ of the header should be "X-Vault-Token" and the value should be the token.
         revoking all tokens created against it before some point in time. The
         suffix can be changed, allowing new callers to have the new suffix as
         part of their path, and then tokens with the old suffix can be revoked
-        via `revoke-prefix`.
+        via `sys/revoke-prefix`.
       </li>
     </ul>
   </dd>