diff --git a/llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp b/llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp
index e7750ccf3ad8de..f4d74ff7c06fb4 100644
--- a/llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp
+++ b/llvm/lib/CodeGen/TargetLoweringObjectFileImpl.cpp
@@ -1758,7 +1758,7 @@ MCSection *TargetLoweringObjectFileWasm::getExplicitSectionGlobal(
   // Certain data sections we treat as named custom sections rather than
   // segments within the data section.
   // This could be avoided if all data segements (the wasm sense) were
-  // represented as thier own sections (in the llvm sense).
+  // represented as their own sections (in the llvm sense).
   // TODO(sbc): https://github.com/WebAssembly/tool-conventions/issues/138
   if (Name == ".llvmcmd" || Name == ".llvmbc")
     Kind = SectionKind::getMetadata();
diff --git a/polly/www/documentation/gpgpucodegen.html b/polly/www/documentation/gpgpucodegen.html
index bc2949aa178927..917c7cbdc1d3f8 100644
--- a/polly/www/documentation/gpgpucodegen.html
+++ b/polly/www/documentation/gpgpucodegen.html
@@ -80,7 +80,7 @@ <h3>What to do in Polly</h3>
    text.</p>
 <p>In this project, we assume that the device driver library has provided an
    interface to launch kernels in the form of assembly text. Fortunately, most
-   of the mainstream GPU vendors provide such a feature in thier products (see
+   of the mainstream GPU vendors provide such a feature in their products (see
    ptxjit of NVIDIA GPUs and CAL of AMD GPUs). Generally speaking, what we
    are going to do in Polly is:</p>
 <li>Find a way to tile the parallel loops.</li>