diff --git a/llvm/docs/LangRef.html b/llvm/docs/LangRef.html
index adc5d9a143fe..e3e710be6b9a 100644
--- a/llvm/docs/LangRef.html
+++ b/llvm/docs/LangRef.html
@@ -1251,38 +1251,42 @@ target datalayout = "layout specification"
-
Any memory access must be done though a pointer value associated
+
Any memory access must be done through a pointer value associated
with an address range of the memory access, otherwise the behavior
is undefined. Pointer values are associated with address ranges
according to the following rules:
- - A pointer value formed from a getelementptr instruction is
- associated with the addresses associated with the first operand of
- the getelementptr.
- - An addresses of a global variable is associated with the address
+
- A pointer value formed from a
+ getelementptr instruction
+ is associated with the addresses associated with the first operand
+ of the getelementptr.
+ - An address of a global variable is associated with the address
range of the variable's storage.
- The result value of an allocation instruction is associated with
the address range of the allocated storage.
- A null pointer in the default address-space is associated with
- no addresses.
- - A pointer value formed by an inttoptr is associated with
- all address ranges of all pointer values that contribute (directly
- or indirectly) to the computation of the pointer's value.
- - The result value of a bitcast is associated with all
+ no address.
+ - A pointer value formed by an
+ inttoptr is associated with all
+ address ranges of all pointer values that contribute (directly or
+ indirectly) to the computation of the pointer's value.
+ - The result value of a
+ bitcast is associated with all
addresses associated with the operand of the bitcast.
- An integer constant other than zero or a pointer value returned
from a function not defined within LLVM may be associated with address
ranges allocated through mechanisms other than those provided by
- LLVM. Such ranges shall not overlap with any ranges of address
+ LLVM. Such ranges shall not overlap with any ranges of addresses
allocated by mechanisms provided by LLVM.
LLVM IR does not associate types with memory. The result type of a
-load merely indicates the size and alignment of the memory from
-which to load, as well as the interpretation of the value. The first
-operand of a store similarly only indicates the size and
-alignment of the store.
+
load merely indicates the size and
+alignment of the memory from which to load, as well as the
+interpretation of the value. The first operand of a
+
store similarly only indicates the size
+and alignment of the store.
Consequently, type-based alias analysis, aka TBAA, aka
-fstrict-aliasing, is not applicable to general unadorned