open-telemetry
/
opentelemetry.io
mirror of https://github.com/open-telemetry/opentelemetry.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix typos in "Signals" documentation section (#3825) 

Co-authored-by: Phillip Carter <pcarter@fastmail.com>
This commit is contained in:
Fabrizio De Cicco 2024-01-20 21:16:11 +01:00 committed by GitHub
parent 3b41cea31f
commit 6e3bf58397
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/docs/concepts/signals/logs.md
View File

@ -33,7 +33,7 @@ components that will play a part in instrumenting our code.
As an application developer, the **Logs Bridge API** should not be called by you
directly, as it is provided for logging library authors to build log appenders /
bridges. Instead, you just use your preferred logging library and configure it
to use an log appender (or log bridge) that is able to emit logs into an
to use a log appender (or log bridge) that is able to emit logs into an
OpenTelemetry LogRecordExporter.
OpenTelemetry language SDKs offer this functionality.

2
content/en/docs/concepts/signals/traces.md
View File

@ -298,7 +298,7 @@ Each span has a status. The three possible values are:
The default value is `Unset`. A span status that is `Unset` means that the
operation it tracked successfully completed without an error.
When a span status is `Error`, then that means some error ocurred in the
When a span status is `Error`, then that means some error occurred in the
operation it tracks. For example, this could be due to an HTTP 500 error on a
server handling a request.