go/opentelemetry-go
1
0
Fork 0
mirror of https://github.com/open-telemetry/opentelemetry-go.git synced 2026-06-03 18:35:08 +02:00
Code Issues Releases Activity

Update getting-started.md (#2984)

Browse Source 
grammar edit for line 175 of readme
This commit is contained in:
Kshitija Murudi
2022-06-28 14:58:51 -07:00
committed by GitHub
parent ef6c0da0de
commit 36b37c4af5
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
website_docs/getting-started.md
+1 -1
View File
@@ -172,7 +172,7 @@ const name = "fib"
Using the full-qualified package name, something that should be unique for Go packages, is the standard way to identify a [`Tracer`]. If your example package name differs, be sure to update the name you use here to match.
Everything should be in place now to start tracing your application. But first, what is a trace? And, how exactly should you build them for you application?
Everything should be in place now to start tracing your application. But first, what is a trace? And, how exactly should you build them for your application?
To back up a bit, a trace is a type of telemetry that represents work being done by a service. A trace is a record of the connection(s) between participants processing a transaction, often through client/server requests processing and other forms of communication.