From 4ba964bae77d9d32b4bb0167ed5533a0c05dcdf9 Mon Sep 17 00:00:00 2001 From: Tyler Yahn Date: Thu, 28 Oct 2021 12:52:27 -0700 Subject: [PATCH] Correct getting started docs typo (#2333) Resolve #2332 --- 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 d4765a8445e..f7b35a6a370 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 to much 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 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. Start by instrumenting the `Run` method.