diff --git a/docs/docs/reference/changed/pattern-matching.md b/docs/docs/reference/changed/pattern-matching.md
index 82b1645d759d..40f5e94201a3 100644
--- a/docs/docs/reference/changed/pattern-matching.md
+++ b/docs/docs/reference/changed/pattern-matching.md
@@ -114,4 +114,4 @@ object Nat {
 // 5 is a natural number
 ```
 
-In case of ambiguities, *Product Pattern* is preferred over *Name Based Pattern*. This document reflects the state of pattern matching as currently implemented in Dotty. They are plans for further simplification, in particular to factor out *Product Pattern* and *Name Based Pattern* into a single type of extractor.
+In case of ambiguities, *Product Pattern* is preferred over *Name Based Pattern*. This document reflects the state of pattern matching as currently implemented in Dotty. There are plans for further simplification, in particular to factor out *Product Pattern* and *Name Based Pattern* into a single type of extractor.
diff --git a/docs/docs/reference/changed/structural-types.md b/docs/docs/reference/changed/structural-types.md
index d51f73c20ed0..b0425475851a 100644
--- a/docs/docs/reference/changed/structural-types.md
+++ b/docs/docs/reference/changed/structural-types.md
@@ -6,7 +6,7 @@ title: "Programmatic Structural Types"
 Previously, Scala supported structural types by means of
 reflection. This is problematic on other platforms, because Scala's
 reflection is JVM-based. Consequently, Scala.js and Scala.native don't
-support structural types fully. The reflction based implementation is
+support structural types fully. The reflection based implementation is
 also needlessly restrictive, since it rules out other implementation
 schemes. This makes structural types unsuitable for e.g. modelling
 rows in a database, for which they would otherwise seem to be an ideal
diff --git a/docs/docs/reference/dropped/auto-apply.md b/docs/docs/reference/dropped/auto-apply.md
index b7096d747abd..1bb82fb9f576 100644
--- a/docs/docs/reference/dropped/auto-apply.md
+++ b/docs/docs/reference/dropped/auto-apply.md
@@ -76,7 +76,7 @@ requirement.
 
 Existing Scala code with inconsistent parameters can still be compiled
 in Dotty under `-language:Scala2`. When paired with the `-rewrite`
-option, the code will be automatcally rewritten to conform to Dotty's
+option, the code will be automatically rewritten to conform to Dotty's
 stricter checking.
 
 ### Reference
diff --git a/docs/docs/reference/dropped/class-shadowing.md b/docs/docs/reference/dropped/class-shadowing.md
index a0be5985626f..b850f5fab846 100644
--- a/docs/docs/reference/dropped/class-shadowing.md
+++ b/docs/docs/reference/dropped/class-shadowing.md
@@ -21,7 +21,7 @@ Dotty rejects this with the error message:
 
 The issue is that the two `Ops` classes _look_ like one overrides the
 other, but classes in Scala cannot be overridden. To keep things clean
-(and its internal operations conistent) the Dotty compiler forces you
+(and its internal operations consistent) the Dotty compiler forces you
 to rename the inner classes so that their names are different.