typos in documentation?

[jkorous-apple]

Summary

I have found two possible typos in documentation. Since English is not my first language I would like to ask for verification.

[jroelofs]

LGTM

cfe/trunk/docs/InternalsManual.rst

 expression with ``true`` because it has side effects.
 
 Implementation Approach
 ^^^^^^^^^^^^^^^^^^^^^^^
 
 After trying several different approaches, we've finally converged on a design
 (Note, at the time of this writing, not all of this has been implemented,
 consider this a design goal!).  Our basic approach is to define a single
-recursive method evaluation method (``Expr::Evaluate``), which is implemented
+recursive evaluation method (``Expr::Evaluate``), which is implemented
 in ``AST/ExprConstant.cpp``.  Given an expression with "scalar" type (integer,
 fp, complex, or pointer) this method returns the following information:
 
 * Whether the expression is an integer constant expression, a general constant
   that was folded but has no side effects, a general constant that was folded
   but that does have side effects, or an uncomputable/unfoldable value.
 * If the expression was computable in any way, this method returns the
   ``APValue`` for the result of the expression.
#. Teach code generation to create IR to your AST node.  This step is the first
 
    * Code generation is separated into scalar/aggregate/complex and
      lvalue/rvalue paths, depending on what kind of result your expression
      produces.  On occasion, this requires some careful factoring of code to
      avoid duplication.
    * ``CodeGenFunction`` contains functions ``ConvertType`` and
      ``ConvertTypeForMem`` that convert Clang's types (``clang::Type*`` or
      ``clang::QualType``) to LLVM types.  Use the former for values, and the
-     later for memory locations: test with the C++ "``bool``" type to check
+     latter for memory locations: test with the C++ "``bool``" type to check
      this.  If you find that you are having to use LLVM bitcasts to make the
      subexpressions of your expression have the type that your expression
      expects, STOP!  Go fix semantic analysis and the AST so that you don't
      need these bitcasts.
    * The ``CodeGenFunction`` class has a number of helper functions to make
      certain operations easy, such as generating code to produce an lvalue or
      an rvalue, or to initialize a memory location with a given value.  Prefer
      to use these functions rather than directly writing loads and stores,