* component.
*
* The minimal size of each block is dictated by the underlying finite element
- * (a blocks consists of a single component for scalar elements, but in the
+ * (a block consists of a single component for scalar elements, but in the
* case of the FE_RaviartThomas, for example, a block consists of <tt>dim</tt>
* components). However, several such minimal blocks can be grouped together
* into user defined blocks at will, and in accordance with the
*
* <i>Implementation:</i>
* deal.II has a number of different finite element classes, all of which are
- * derived from the FiniteElement base class (see the @ref feall "module on
- * finite element classes"). With one exception, whether they are scalar or
+ * derived from the FiniteElement base class
+ * (see the @ref feall "module on finite element classes").
+ * With one exception, whether they are scalar or
* vector valued, they all define a single block: all vector components the
* finite element defines through its FiniteElement::n_components() function
* form a single block, i.e. FiniteElement::n_blocks() returns one.
*
* This class is not a fully implemented FiniteElement class. Instead there
* are several pure virtual functions declared in the FiniteElement class
- * which cannot implemented by this class but are left for implementation in
- * derived classes.
+ * which cannot be implemented by this class but are left for implementation
+ * in derived classes.
*
* Furthermore, this class assumes that shape functions of the
* FiniteElement under consideration do <em>not</em> depend on the
* freedom associated with a single base element of an FESystem, where base
* elements with multiplicities count multiple times. These blocks are usually
* addressed using the information in DoFHandler::block_info(). The number of
- * blocks of of a FESystem object is simply the sum of all multiplicities of
+ * blocks of a FESystem object is simply the sum of all multiplicities of
* base elements.
*
* For example, the FESystem for the Taylor-Hood element for the
* subobject (vertex, line, quad, or hex), the degrees of freedom are
* numbered such that we run over all subelements first, before
* turning for the next dof on this subobject or for the next
- * subobject. For example, for a element of three components in one
+ * subobject. For example, for an element of three components in one
* space dimension, the first two components being cubic lagrange
* elements and the third being a quadratic lagrange element, the
* ordering for the system <tt>s=(u,v,p)</tt> is: