From cc19b8828828bb1416b2d1a2a2e8c3b97ebf4896 Mon Sep 17 00:00:00 2001 From: Jeff Escalante Date: Mon, 13 Apr 2020 19:11:41 -0400 Subject: [PATCH] a couple more anchor link fixes --- website/pages/api-docs/acl/index.mdx | 4 ++-- website/pages/docs/connect/proxies/envoy.mdx | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/website/pages/api-docs/acl/index.mdx b/website/pages/api-docs/acl/index.mdx index d4542091c5..808939c571 100644 --- a/website/pages/api-docs/acl/index.mdx +++ b/website/pages/api-docs/acl/index.mdx @@ -165,7 +165,7 @@ $ curl \ - `ReplicatedTokenIndex` - The last token index that was successfully replicated. This index can be compared with the value of the `X-Consul-Index` header returned - by the [`/v1/acl/tokens`](/api/acl/tokens#list) endpoint to determine + by the [`/v1/acl/tokens`](/api/acl/tokens#list-acls) endpoint to determine if the replication process has gotten all available ACL tokens. Note that ACL replication is rate limited so the indexes may lag behind the primary datacenter. @@ -234,7 +234,7 @@ This endpoint translates the legacy rules embedded within a legacy ACL into the syntax. It is intended to be used by operators managing Consul's ACLs and performing legacy token to new policy migrations. Note that this API requires the auto-generated Accessor ID of the legacy token. This ID can be retrieved using the -[`/v1/acl/token/self`](/api/acl/tokens#self) endpoint. +[`/v1/acl/token/self`](/api/acl/tokens#read-self-token) endpoint. | Method | Path | Produces | | ------ | ----------------------------------- | ------------ | diff --git a/website/pages/docs/connect/proxies/envoy.mdx b/website/pages/docs/connect/proxies/envoy.mdx index 2accdda7c6..ad293d84ae 100644 --- a/website/pages/docs/connect/proxies/envoy.mdx +++ b/website/pages/docs/connect/proxies/envoy.mdx @@ -284,7 +284,7 @@ definition](/docs/connect/registration/service-registration) or These fields may also be overridden explicitly in the [proxy service definition](/docs/connect/registration/service-registration), or defined in the [global `proxy-defaults` configuration -entry](/docs/agent/config_entries/proxy-defaults) to act as +entry](/docs/agent/config-entries/proxy-defaults) to act as defaults that are inherited by all services. Prior to 1.8.0 these settings were specific to Mesh Gateways. The deprecated