diff --git a/content/en/docs/concepts/signals/logs.md b/content/en/docs/concepts/signals/logs.md
index 268a744445ac..f8165e1400ad 100644
--- a/content/en/docs/concepts/signals/logs.md
+++ b/content/en/docs/concepts/signals/logs.md
@@ -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.
diff --git a/content/en/docs/concepts/signals/traces.md b/content/en/docs/concepts/signals/traces.md
index 5f5fc10a95f7..ebd6ac9caf04 100644
--- a/content/en/docs/concepts/signals/traces.md
+++ b/content/en/docs/concepts/signals/traces.md
@@ -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.