diff --git a/.github/ISSUE_TEMPLATE/ISSUE_REPORT.md b/.github/ISSUE_TEMPLATE/ISSUE_REPORT.md
index 5df4ee85b615..d69520f5db17 100644
--- a/.github/ISSUE_TEMPLATE/ISSUE_REPORT.md
+++ b/.github/ISSUE_TEMPLATE/ISSUE_REPORT.md
@@ -8,7 +8,7 @@ assignees: ''
 ---
 
 **What happened?**
-Describe the problem that occured.
+Describe the problem that occurred.
 
 **What did you expect would happen?**
 Describe the expected result/output.
diff --git a/content/en/blog/2022/apisix.md b/content/en/blog/2022/apisix.md
index a98feaf81a17..0a41c186cc0b 100644
--- a/content/en/blog/2022/apisix.md
+++ b/content/en/blog/2022/apisix.md
@@ -364,7 +364,7 @@ provides a lot of value.
 When the request does not reach the demo-server, the output would not include
 the span of demo-server.
 
-![demo-server disconneted](/img/apisix/demo-server-disconnected.png)
+![demo-server disconnected](/img/apisix/demo-server-disconnected.png)
 
 ## Disable the Plugin
 
diff --git a/content/en/docs/collector/trace-receiver.md b/content/en/docs/collector/trace-receiver.md
index a4e9f73c3c38..a10df2eddc90 100644
--- a/content/en/docs/collector/trace-receiver.md
+++ b/content/en/docs/collector/trace-receiver.md
@@ -1840,7 +1840,7 @@ Here is what `appendAtmSystemInstrScopeSpans` looks like after the update:
 ```go
  func appendAtmSystemInstrScopeSpans(resourceSpans *ptrace.ResourceSpans) (ptrace.ScopeSpans){
 	scopeSpans := resourceSpans.ScopeSpans().AppendEmpty()
-	scopeSpans.Scope().SetName("atm-sytem")
+	scopeSpans.Scope().SetName("atm-system")
 	scopeSpans.Scope().SetVersion("v1.0")
 	return scopeSpans
 }
@@ -2137,7 +2137,7 @@ Resource labels:
      -> service.version: STRING(v1.0)
 ScopeSpans #0
 ScopeSpans SchemaURL:
-InstrumentationScope atm-sytem v1.0
+InstrumentationScope atm-system v1.0
 ResourceSpans #1
 Resource SchemaURL:
 Resource labels:
@@ -2149,7 +2149,7 @@ Resource labels:
      -> service.version: STRING(v2.5)
 ScopeSpans #0
 ScopeSpans SchemaURL:
-InstrumentationScope atm-sytem v1.0
+InstrumentationScope atm-system v1.0
 Span #0
     Trace ID       : 5cce8a774d4546c2a5cbdeb607ec74c9
     Parent ID      :
@@ -2173,7 +2173,7 @@ Resource labels:
      -> service.version: STRING(v1.0)
 ScopeSpans #0
 ScopeSpans SchemaURL:
-InstrumentationScope atm-sytem v1.0
+InstrumentationScope atm-system v1.0
 ResourceSpans #1
 Resource SchemaURL:
 Resource labels:
@@ -2185,7 +2185,7 @@ Resource labels:
      -> service.version: STRING(v2.5)
 ScopeSpans #0
 ScopeSpans SchemaURL:
-InstrumentationScope atm-sytem v1.0
+InstrumentationScope atm-system v1.0
 Span #0
     Trace ID       : 8a6ca822db0847f48facfebbb08bbb9e
     Parent ID      :
diff --git a/content/en/docs/instrumentation/java/manual.md b/content/en/docs/instrumentation/java/manual.md
index b002a4d64680..c9710b178e21 100644
--- a/content/en/docs/instrumentation/java/manual.md
+++ b/content/en/docs/instrumentation/java/manual.md
@@ -53,7 +53,7 @@ the most brittle option for library instrumentation.
 ## Acquiring a Tracer
 
 To do [Tracing](/docs/concepts/signals/traces/#tracing-in-opentelemetry) you'll
-need to aquire a [`Tracer`](/docs/concepts/signals/traces/#tracer).
+need to acquire a [`Tracer`](/docs/concepts/signals/traces/#tracer).
 
 **Note:** Methods of the OpenTelemetry SDK should never be called.
 
diff --git a/content/en/docs/instrumentation/js/instrumentation.md b/content/en/docs/instrumentation/js/instrumentation.md
index 8f79f405c817..bd7728d3f6fa 100644
--- a/content/en/docs/instrumentation/js/instrumentation.md
+++ b/content/en/docs/instrumentation/js/instrumentation.md
@@ -132,7 +132,7 @@ In contrast, the `SimpleSpanProcessor` processes spans as they are created. This
 means that if you create 5 spans, each will be processed an exported before the
 next span is created in code. This can be helpful in scenarios where you do not
 want to risk losing a batch, or if you're experimenting with OpenTelemetry in
-development. However, it also comes with potentially signficant overhead,
+development. However, it also comes with potentially significant overhead,
 especially if spans are being exported over a network - each time a call to
 create a span is made, it would be processed and sent over a network before your
 app's execution could continue.
diff --git a/content/en/docs/instrumentation/net/getting-started.md b/content/en/docs/instrumentation/net/getting-started.md
index b956596f9a92..3a120b9be63f 100644
--- a/content/en/docs/instrumentation/net/getting-started.md
+++ b/content/en/docs/instrumentation/net/getting-started.md
@@ -91,7 +91,7 @@ The following sample demonstrates automatic and manual
 [tracing](/docs/concepts/signals/traces/#tracing-in-opentelemetry) with ASP.NET
 Core.
 
-First, install requried packages:
+First, install required packages:
 
 ```shell
 dotnet add package OpenTelemetry.Extensions.Hosting --prerelease
diff --git a/content/en/docs/instrumentation/net/manual.md b/content/en/docs/instrumentation/net/manual.md
index 62d6c2d32e0c..36da5ccc4fe5 100644
--- a/content/en/docs/instrumentation/net/manual.md
+++ b/content/en/docs/instrumentation/net/manual.md
@@ -17,7 +17,7 @@ API, repurposing existing constructs like `ActivitySource` and `Activity` to be
 OpenTelemetry-compliant under the covers.
 
 However, there are parts of the OpenTelemetry API and terminology that .NET
-developers must still know to be able to instrument their applications, wich are
+developers must still know to be able to instrument their applications, which are
 covered here as well as the `System.Diagnostics` API.
 
 If you prefer to use OpenTelemetry APIs instead of `System.Diagnostics` APIs,