maybe code blocks are like this...

gof/type.py

@@ -244,7 +244,7 @@ class PureType(object):
 class Type(object2, PureType, CLinkerType):
     """Convenience wrapper combining `PureType` and `CLinkerType`.
 
-    Theano comes with several subclasses of {{{theano.type}}} such as:
+    Theano comes with several subclasses of such as:
 
     - `Generic`: for any python type
 
@@ -255,7 +255,7 @@ class Type(object2, PureType, CLinkerType):
     But you are encouraged to write your own, as described in WRITEME.
 
     In the following code:
-    .. code-block:: python
+    .. python::
        # Note: tensor.fvector is a Type (subtype Tensor) instance
        # Declare a symbolic floating-point vector using __call__
        b = tensor.fvector()
@@ -265,14 +265,13 @@ class Type(object2, PureType, CLinkerType):
 
 
      Whenever you create a symbolic variable in theano (technically, `Result`) it will contain
-     a reference to a Type instance.  
-     That reference is typically constant during the lifetime of the Result.
-     Many variables can refer to a single Type instance, as do b and c above.
-     The Type instance defines the kind of value which might end up in that variable when executing a
-     `Function`.  In this sense, theano is like a strongly-typed language because the types are
-     included in the graph before the values.  In
-     our example above, b is a Result which is guaranteed to corresond to a
-     numpy.ndarray of rank 1 when we try to do some computations with it.
+     a reference to a Type instance.  That reference is typically constant during the lifetime
+     of the Result.  Many variables can refer to a single Type instance, as do b and c above.
+     The Type instance defines the kind of value which might end up in that variable when
+     executing a `Function`.  In this sense, theano is like a strongly-typed language because
+     the types are included in the graph before the values.  In our example above, b is a
+     Result which is guaranteed to corresond to a numpy.ndarray of rank 1 when we try to do
+     some computations with it.
 
      Many `Op` instances will raise an exception if they are applied to inputs with incorrect
      types.  Type references are also useful to do type-checking in pattern-based optimizations.