Fix broken links (#4603)

kyma-project · Jun 21, 2019 · eecb659 · eecb659
1 parent b4e9985
commit eecb659
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/docs/tracing/02-01-tracing.md b/docs/tracing/02-01-tracing.md
@@ -2,17 +2,17 @@
 title: Architecture
 ---
 
-The diagram presents the tracing flow including the details of requesting and storing traces. 
+The diagram presents the tracing flow including the details of requesting and storing traces.
 
 ![Tracing architecture](./assets/tracing-architecture.svg)
 
 
 The Jaeger Deployment is the central element of the tracing architecture.
-It serves as a target of all query requests sent from the Jaeger UI. It is also the space for storing and processing the spans and traces created by Envoy, Istio, and Kyma services. 
+It serves as a target of all query requests sent from the Jaeger UI. It is also the space for storing and processing the spans and traces created by Envoy, Istio, and Kyma services.
 
 ## Request traces
 
-The process of requesting traces from Jaeger looks as follows: 
+The process of requesting traces from Jaeger looks as follows:
 
 1. A Kyma user accesses Jaeger UI.
 2. The user uses the UI to request the trace details for a given service by selecting the service from the **Services** drop-down menu and confirming the choice by selecting the **Find Traces** button. Jaeger passes the request to jaeger-query, which is the UI facade.
@@ -24,8 +24,8 @@ The process of requesting traces from Jaeger looks as follows:
 
 Traces are stored in Jaeger in the following way:
 
-1. A Kyma user configures the application to propagate the correct [HTTP headers](https://istio.io/docs/tasks/telemetry/distributed-tracing/overview/#understanding-what-happened) for the outbound calls.
+1. A Kyma user configures the application to propagate the correct [HTTP headers](https://istio.io/docs/tasks/telemetry/distributed-tracing/overview/) for the outbound calls.
 2. Envoy passes the trace details to the Zipkin Kubernetes service. This service acts as a facade receiving the trace and span details.
-3. The Zipkin service forwards the tracing information to Jaeger Deployment, allowing it to process them. 
+3. The Zipkin service forwards the tracing information to Jaeger Deployment, allowing it to process them.
 
 ![Store traces](./assets/store-traces.svg)
diff --git a/docs/tracing/03-03-http-headers.md b/docs/tracing/03-03-http-headers.md
@@ -3,4 +3,4 @@ title: Propagate HTTP headers
 type: Details
 ---
 
-The Envoy proxy controls the inbound and outbound traffic in the application and automatically sends the trace information to Zipkin. To track the flow of the REST API calls or the service injections in Kyma, it requires the application to cooperate with the microservices code. To enable such cooperation, configure the application to propagate the tracing context in HTTP headers when making outbound calls. See the [Istio documentation](https://istio.io/docs/tasks/telemetry/distributed-tracing/overview/#understanding-what-happened) for details on headers required to ensure the correct tracing in Kyma.
+The Envoy proxy controls the inbound and outbound traffic in the application and automatically sends the trace information to Zipkin. To track the flow of the REST API calls or the service injections in Kyma, it requires the application to cooperate with the microservices code. To enable such cooperation, configure the application to propagate the tracing context in HTTP headers when making outbound calls. See the [Istio documentation](https://istio.io/docs/tasks/telemetry/distributed-tracing/overview/) for details on headers required to ensure the correct tracing in Kyma.