</p>
<p>
- If enabled, each of the features above will usually add one ore
+ If enabled, each of the features above will usually add one or
more dependencies to external or 'bundled' (i.e. bundled with
<acronym>deal.II</acronym> and residing under <code>bundled/</code>)
libraries.
* fairly general tensorial types @p T.
*
* The purpose of this reordering facility is to be able to contract over
- * an arbitrary index of two (ore more) tensors:
+ * an arbitrary index of two (or more) tensors:
* - reorder the indices in mind to the end of the tensors
* - use the contract function below that contracts the _last_ elements of
* tensors.
* Implementation of matrix generation for MGTransferBlock.
*
* This is the base class for MGTransfer objects for systems of equations
- * where multigrid is applied only to one ore some blocks, where a
+ * where multigrid is applied only to one or some blocks, where a
* @ref GlossBlock
* comprises all degrees of freedom generated by one base element.
*
// This requires usage of find_least_face_dominating_fe()
// with fe_indices of sub-faces and the mother face.
// Note that the last solution covers the first two scenarios,
- // thus we stick with it assuming that we won't loose much time/efficiency.
+ // thus we stick with it assuming that we won't lose much time/efficiency.
const unsigned int dominating_fe_index = fe_collection.find_least_face_dominating_fe(fe_ind_face_subface);
AssertThrow(dominating_fe_index != numbers::invalid_unsigned_int,
ExcMessage("Could not find a least face dominating FE."));
// natural to use the union. however, intersection is
// the less aggressive tactic and favours a smaller
// number of refined cells over an intensive
- // smoothing. this way we try not to loose too much of
+ // smoothing. this way we try not to lose too much of
// the effort we put in anisotropic refinement
// indicators due to overly aggressive smoothing...
directional_cell_refinement_case