Fix some typos.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@24298 91177308-0d34-0410-b5e6-96231b3b80d8

diff --git a/docs/LangRef.html b/docs/LangRef.html
index 59dacf7ef40d626c8d9ee2f84af6e0ff2e464f47..72dfd88c1b6019a1073356da0322b96137768b8d 100644 (file)
--- a/docs/LangRef.html
+++ b/docs/LangRef.html
@@ -2323,7 +2323,7 @@ the "variable argument" area of a function call.  It is used to implement the
 
 <p>This instruction takes a <tt>va_list*</tt> value and the type of
 the argument. It returns a value of the specified argument type and
-increments the <tt>va_list</tt> to poin to the next argument.  Again, the
+increments the <tt>va_list</tt> to point to the next argument.  Again, the
 actual type of <tt>va_list</tt> is target specific.</p>
 
 <h5>Semantics:</h5>
@@ -2790,7 +2790,7 @@ The '<tt>llvm.pcmarker</tt>' intrinsic is a method to export a Program Counter
 (PC) in a region of 
 code to simulators and other tools.  The method is target specific, but it is 
 expected that the marker will use exported symbols to transmit the PC of the marker.
-The marker makes no guaranties that it will remain with any specific instruction 
+The marker makes no guarantees that it will remain with any specific instruction 
 after optimizations.  It is possible that the presense of a marker will inhibit 
 optimizations.  The intended use is to be inserted after optmizations to allow
 correlations of simulation runs.