From 43c55c3e5c64da924a1dbbef4900fda8c1c1b149 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Robert=20Paj=C4=85k?= Date: Wed, 10 Nov 2021 23:15:16 +0100 Subject: [PATCH] Rephrase a sentence with typo in getting-started.md (#2355) Co-authored-by: Tyler Yahn --- website_docs/getting-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website_docs/getting-started.md b/website_docs/getting-started.md index f7b35a6a370..6e0d37a9c0e 100644 --- a/website_docs/getting-started.md +++ b/website_docs/getting-started.md @@ -176,7 +176,7 @@ To back up a bit, a trace is a type of telemetry that represents work being done Each part of the work that a service performs is represented in the trace by a span. Those spans are not just an unordered collection. Like the call stack of our application, those spans are defined with relationships to one another. The "root" span is the only span without a parent, it represents how a service request is started. All other spans have a parent relationship to another span in the same trace. -If this last part about span relationships doesn't make complete sense now, don't worry. The important thing to take away is each part of your code that does work should to be represented as a span. You will have a better understanding of these span relationships after you instrument your code, so let's get started. +If this last part about span relationships doesn't make complete sense now, don't worry. The most important takeaway is that each part of your code, which does some work, should be represented as a span. You will have a better understanding of these span relationships after you instrument your code, so let's get started. Start by instrumenting the `Run` method.