small fix to the doc.

doc/optimizations.txt

@@ -5,9 +5,9 @@ Optimizations
 ==============
 
 Theano applies many kinds of graph optimizations, with different objectives:
-* simplifying and standardizing the form of the expression graph (e.g.  :term:`merge`, :term:`add canonicalization` ), 
-* reducing the maximum memory footprint (e.g. :term:`inplace_elemwise`),
-* increasing execution speed (e.g. :term:`constant folding`).
+ * simplifying and standardizing the form of the expression graph (e.g.  :term:`merge`, :term:`add canonicalization` ), 
+ * reducing the maximum memory footprint (e.g. :term:`inplace_elemwise`),
+ * increasing execution speed (e.g. :term:`constant folding`).
 
 The optimizations are listed in roughly chronological order.  The table below
 gives a quick summary of the optimizations included in the default modes. 

doc/tutorial/examples.txt

@@ -212,8 +212,7 @@ Using shared variables
 It is also possible to make a function with an internal state. For
 example, let's say we want to make an accumulator: at the beginning,
 the state is initialized to zero. Then, on each function call, the state
-is incremented by the function's argument. We'll also make it so that
-the increment has a default value of 1.
+is incremented by the function's argument.
 
 First let's define the ``accumulator`` function. It adds its argument to the
 internal state, and returns the old state value.
@@ -306,7 +305,7 @@ Using Random Numbers
 Because in Theano you first express everything symbolically and
 afterwards compile this expression to get functions, 
 using pseudo-random numbers is not as straightforward as it is in 
-numpy, though also not to complicated. 
+numpy, though also not too complicated. 
 
 The way to think about putting randomness into Theano's computations is 
 to put random variables in your graph. Theano will allocate a numpy 

doc/tutorial/modes.txt

@@ -50,7 +50,7 @@ expressions or new optimizations) to run your code using the DebugMode
 do several self-checks and assertations that can help to diagnose 
 possible programming errors that can lead to incorect output. Note that 
 ``DEBUG_MODE`` is much slower then ``FAST_RUN`` or ``FAST_COMPILE`` so 
-use it only during development (not when you lunch 1000 process on a 
+use it only during development (not when you launch 1000 process on a 
 cluster!).