[skywalking] 01/01: Fix dead links

[ke...@apache.org]

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

kezhenxu94 pushed a commit to branch doc/dead-links
in repository https://gitbox.apache.org/repos/asf/skywalking.git

commit e7d6d85ce8fcd22217213a64b10585fba4021639
Author: kezhenxu94 <ke...@apache.org>
AuthorDate: Thu May 13 08:10:23 2021 +0800

    Fix dead links
---
 docs/en/setup/envoy/metrics_service_setting.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/en/setup/envoy/metrics_service_setting.md b/docs/en/setup/envoy/metrics_service_setting.md
index 8750de9..163d10d 100644
--- a/docs/en/setup/envoy/metrics_service_setting.md
+++ b/docs/en/setup/envoy/metrics_service_setting.md
@@ -50,7 +50,7 @@ static_resources:
 
 A more complete static configuration, can be observed [here](config.yaml).
 
-Note that Envoy can also be configured dynamically through [xDS Protocol](https://github.com/envoyproxy/data-plane-api/blob/main/xds_protocol.rst).
+Note that Envoy can also be configured dynamically through [xDS Protocol](https://github.com/envoyproxy/envoy/blob/v1.18.2/api/xds_protocol.rst).
 
 As mentioned above, SkyWalking also builds the topology of services from the metrics, this is because Envoy also carries the service metadata along with the metrics, to feed the Envoy such metadata, another configuration part is as follows:
 
@@ -65,7 +65,7 @@ node:
 
 ## Configure Envoy to send metrics to SkyWalking with Istio
 
-Typically, Envoy can be also used under Istio's control, where the configurations are much more simple because Istio composes the configurations for you and sends them to Envoy via [xDS Protocol](https://github.com/envoyproxy/data-plane-api/blob/master/xds_protocol.rst).
+Typically, Envoy can be also used under Istio's control, where the configurations are much more simple because Istio composes the configurations for you and sends them to Envoy via [xDS Protocol](https://github.com/envoyproxy/envoy/blob/v1.18.2/api/xds_protocol.rst).
 Istio also automatically injects the metadata such as service name and instance name into the bootstrap configurations.
 
 Under this circumstance, emitting the metrics to SyWalking is as simple as adding the option `--set meshConfig.defaultConfig.envoyMetricsService.address=<skywalking.address.port.11800>` to Istio install command, for example:
@@ -75,7 +75,7 @@ istioctl install -y \
   --set profile=demo `# replace the profile as per your need` \
   --set meshConfig.defaultConfig.envoyMetricsService.address=<skywalking.address.port.11800> # replace <skywalking.address.port.11800> with your actual SkyWalking OAP address
 ```
-
+F
 If you already have Istio installed, you can use the following command to apply the config without re-installing Istio:
 
 ```shell