[docs] Fix a couple spelling errors.

llvm-svn: 352439

2 files changed, 2 insertions, 2 deletions

diff --git a/llvm/docs/LangRef.rst b/llvm/docs/LangRef.rst
index 16cc068ce4f..27f5e0cbec7 100644
--- a/llvm/docs/LangRef.rst
+++ b/llvm/docs/LangRef.rst
@@ -2184,7 +2184,7 @@ operations relative to non-volatile operations. This is not Java's
 A volatile load or store may have additional target-specific semantics.
 Any volatile operation can have side effects, and any volatile operation
 can read and/or modify state which is not accessible via a regular load
-or store in this module. Volatile operations may use adresses which do
+or store in this module. Volatile operations may use addresses which do
 not point to memory (like MMIO registers). This means the compiler may
 not use a volatile operation to prove a non-volatile access to that
 address has defined behavior.
diff --git a/llvm/docs/SpeculativeLoadHardening.md b/llvm/docs/SpeculativeLoadHardening.md
index 0911b7c6ae2..de6dc015c57 100644
--- a/llvm/docs/SpeculativeLoadHardening.md
+++ b/llvm/docs/SpeculativeLoadHardening.md
@@ -255,7 +255,7 @@ if (untrusted_size_from_caller < sizeof(local_buffer)) {
   memcpy(local_buffer, untrusted_data_from_caller,
          untrusted_size_from_caller);
   // The stack has now been smashed, writing an attacker-controlled
-  // address over the return adress.
+  // address over the return address.
   minor_processing(local_buffer);
   return;
   // Control will speculate to the attacker-written address.