This commit adds missing text and improves some HTML.
* object.
* @param[in] starting_index The index of the first element of the vector that
* will be part of this view.
- * @param[in] size_of_view
+ * @param[in] size_of_view Number of elements in the new ArrayView.
*
* @pre <code>starting_index + size_of_view <= vector.size()</code>
*
* object.
* @param[in] starting_index The index of the first element of the vector that
* will be part of this view.
- * @param[in] size_of_view
+ * @param[in] size_of_view Number of elements in the new ArrayView.
*
* @pre <code>starting_index + size_of_view <= vector.size()</code>
*
* iterator is invalid anyway, regardless of the state of the triangulation
* pointer and the state of the element pointed to.
*
- * Past-the-end iterators may also be used to compare an iterator with the <i
- * >before-the-start</i> value, when running backwards. There is no
+ * Past-the-end iterators may also be used to compare an iterator with the
+ * <i>before-the-start</i> value, when running backwards. There is no
* distinction between the iterators pointing past the two ends of a vector.
*
* By defining only one value to be past-the-end and making all other values
*
* Range-based for loops are useful in that they require much less code
* than traditional loops (see <a
- * href="http://en.wikipedia.org/wiki/C%2B%2B11#Range-
- * based_for_loop">here</a> for a discussion of how they work). An example
- * is that without range-based for loops, one often writes code such as
- * the following:
+ * href="http://en.wikipedia.org/wiki/C%2B%2B11#Range-based_for_loop">here</a>
+ * for a discussion of how they work). An example is that without
+ * range-based for loops, one often writes code such as the following:
* @code
* DoFHandler<dim> dof_handler;
* ...