diff --git a/flang/docs/Extensions.md b/flang/docs/Extensions.md
--- a/flang/docs/Extensions.md
+++ b/flang/docs/Extensions.md
@@ -140,7 +140,7 @@
   for the default kind of INTEGER are assumed to have the least larger kind
   that can hold them, if one exists.
 * BOZ literals can be used as INTEGER values in contexts where the type is
-  unambiguous: the right hand sides of assigments and initializations
+  unambiguous: the right hand sides of assignments and initializations
   of INTEGER entities, as actual arguments to a few intrinsic functions
   (ACHAR, BTEST, CHAR), and as actual arguments of references to
   procedures with explicit interfaces whose corresponding dummy
@@ -292,7 +292,7 @@
 * Use of INTEGER data with the intrinsic logical operators `.NOT.`, `.AND.`, `.OR.`,
   and `.XOR.`.
 * IF (integer expression) THEN ... END IF  (PGI/Intel)
-* Comparsion of LOGICAL with ==/.EQ. rather than .EQV. (also .NEQV.) (PGI/Intel)
+* Comparison of LOGICAL with ==/.EQ. rather than .EQV. (also .NEQV.) (PGI/Intel)
 * Procedure pointers in COMMON blocks (PGI/Intel)
 * Underindexing multi-dimensional arrays (e.g., A(1) rather than A(1,1)) (PGI only)
 * Legacy PGI `NCHARACTER` type and `NC` Kanji character literals
diff --git a/flang/docs/FIRArrayOperations.md b/flang/docs/FIRArrayOperations.md
--- a/flang/docs/FIRArrayOperations.md
+++ b/flang/docs/FIRArrayOperations.md
@@ -115,7 +115,7 @@
 This operation taken with `array_load`'s captures Fortran's
 copy-in/copy-out semantics. The first operands of `array_merge_store` is the
 result of the initial `array_load` operation. While this value could be
-retrieved by reference chasiing through the different array operations it is
+retrieved by reference chasing through the different array operations it is
 useful to have it on hand directly for analysis passes since this directly
 defines the "bounds" of the Fortran statement represented by these operations.
 The intention is to allow copy-in/copy-out regions to be easily delineated,
diff --git a/flang/examples/FlangOmpReport/yaml_summarizer.py b/flang/examples/FlangOmpReport/yaml_summarizer.py
--- a/flang/examples/FlangOmpReport/yaml_summarizer.py
+++ b/flang/examples/FlangOmpReport/yaml_summarizer.py
@@ -44,7 +44,7 @@
     $ python3 yaml_summarizer.py file_1.yaml file_2.yaml
     <Unique OMP constructs with there grouped clauses from file_1.yaml and file_2.yaml>
 
-    Construcsts are in the form:
+    Constructs are in the form:
     - construct: someOMPconstruct
     count: 8
     clauses:
diff --git a/flang/lib/Optimizer/CodeGen/TargetRewrite.cpp b/flang/lib/Optimizer/CodeGen/TargetRewrite.cpp
--- a/flang/lib/Optimizer/CodeGen/TargetRewrite.cpp
+++ b/flang/lib/Optimizer/CodeGen/TargetRewrite.cpp
@@ -434,7 +434,7 @@
     return mlir::success();
   }
 
-  /// If the signature does not need any special target-specific converions,
+  /// If the signature does not need any special target-specific conversions,
   /// then it is considered portable for any target, and this function will
   /// return `true`. Otherwise, the signature is not portable and `false` is
   /// returned.
diff --git a/flang/lib/Semantics/check-nullify.cpp b/flang/lib/Semantics/check-nullify.cpp
--- a/flang/lib/Semantics/check-nullify.cpp
+++ b/flang/lib/Semantics/check-nullify.cpp
@@ -60,7 +60,7 @@
   //   A pointer-object shall not depend on the value,
   //   bounds, or association status of another pointer-
   //   object in the same NULLIFY statement.
-  // This restriction is the programmer's responsibilty.
+  // This restriction is the programmer's responsibility.
   // Some dependencies can be found compile time or at
   // runtime, but for now we choose to skip such checks.
 }
diff --git a/flang/test/Driver/default-backend-pipelines.f90 b/flang/test/Driver/default-backend-pipelines.f90
--- a/flang/test/Driver/default-backend-pipelines.f90
+++ b/flang/test/Driver/default-backend-pipelines.f90
@@ -1,4 +1,4 @@
-! Verify that`-O{n}` is indeed taken into account when definining the LLVM backend pass pipeline.
+! Verify that`-O{n}` is indeed taken into account when defining the LLVM backend pass pipeline.
 
 ! REQUIRES: aarch64-registered-target
 
diff --git a/flang/test/Semantics/altreturn06.f90 b/flang/test/Semantics/altreturn06.f90
--- a/flang/test/Semantics/altreturn06.f90
+++ b/flang/test/Semantics/altreturn06.f90
@@ -1,5 +1,5 @@
 ! RUN: %python %S/test_errors.py %s %flang_fc1
-! Test alternat return argument passing for internal and external subprograms
+! Test alternate return argument passing for internal and external subprograms
 ! Both of the following are OK
   call extSubprogram (*100)
   call intSubprogram (*100)
diff --git a/flang/test/Semantics/call27.f90 b/flang/test/Semantics/call27.f90
--- a/flang/test/Semantics/call27.f90
+++ b/flang/test/Semantics/call27.f90
@@ -1,5 +1,5 @@
 ! RUN: %python %S/test_errors.py %s %flang_fc1
-! Catch NULL() actual argement association with allocatable dummy argument
+! Catch NULL() actual argument association with allocatable dummy argument
 program test
   !ERROR: Null actual argument 'NULL()' may not be associated with allocatable dummy argument 'a='
   call foo1(null())