* to the solution values for all degrees of freedom that are <i>locally
* relevant</i>. On the other hand, both of the packages we can use for
* parallel linear algebra (PETSc and Trilinos) as well as
- * parallel::distributed::Vector subdivide vectors into chunks
+ * LinearAlgebra::distributed::Vector subdivide vectors into chunks
* each processor owns and chunks stored on other processors. To postprocess
* stuff therefore means that we have to tell PETSc or Trilinos that it should
* also import <i>ghost elements</i>, i.e. additional vector elements of the
* that the current processor stores but does not own (i.e., the
* "ghost elements") are simply mirror images of a primary value somewhere
* else -- thus, the name "ghost". This is also the case for the
- * parallel::distributed::Vector class.
+ * LinearAlgebra::distributed::Vector class.
*
* On the other hand, in Trilinos (and consequently in
* TrilinosWrappers::MPI::Vector), a ghosted vector is simply a view
* across MPI processes.
*
* This function does not imply a model of keeping data on different processes
- * in sync, as parallel::distributed::Vector and other vector classes do where
- * there exists a notion of certain elements of the vector owned by each
+ * in sync, as LinearAlgebra::distributed::Vector and other vector classes do
+ * where there exists a notion of certain elements of the vector owned by each
* process and possibly ghost elements that are mirrored from its owning
* process to other processes. Rather, the elements of the current object are
* simply copied to the other processes, and it is useful to think of this
* space.
*
* This function does not imply a model of keeping data on different processes
- * in sync, as parallel::distributed::Vector and other vector classes do where
- * there exists a notion of certain elements of the vector owned by each
+ * in sync, as LinearAlgebra::distributed::Vector and other vector classes do
+ * where there exists a notion of certain elements of the vector owned by each
* process and possibly ghost elements that are mirrored from its owning
* process to other processes. Rather, the elements of the current object are
* simply copied to the other processes, and it is useful to think of this
* TrilinosWrappers::PreconditionBase that this payload wraps is passed by
* reference to the <tt>vmult</tt> and <tt>Tvmult</tt> functions. This
* object is not thread-safe when the transpose flag is set on it or the
- * Trilinos object to which it refers. See the docuemtation for the
+ * Trilinos object to which it refers. See the documentation for the
* TrilinosWrappers::internal::LinearOperatorImplementation::TrilinosPayload::SetUseTranspose()
* function for further details.
*