further initialise()->initialize() and alike

diff --git a/doc/news/changes.h b/doc/news/changes.h
index ee06971fe1eb8fcfb0977f03d32cb99d4dd83a0b..d77a7b8ac800dab356bf4baa5b7e4609065aacf3 100644 (file)
--- a/doc/news/changes.h
+++ b/doc/news/changes.h
@@ -40,7 +40,7 @@ inconvenience this causes.
 <ol>
   <li> Rework: SLEPcWrappers were reworked to allow usage of PETSc solvers
   and preconditioners inside SLEPc's eigensolvers. To that end extra methods
-  were introduced to PETSc wrappers. Moreover, initialisation of the
+  were introduced to PETSc wrappers. Moreover, initialization of the
   underlying SLEPc objects is now done inside constructors of the wrapper
   classes. As a result, one has to provide an MPI communicator to the constructors of
   spectral transformation classes.

diff --git a/include/deal.II/lac/slepc_solver.h b/include/deal.II/lac/slepc_solver.h
index cc4887d439965263a3f5ec75afad17b69735d5d6..96da5c012457dcbb500ace99b8b9cb6455757410 100644 (file)
--- a/include/deal.II/lac/slepc_solver.h
+++ b/include/deal.II/lac/slepc_solver.h
@@ -79,7 +79,7 @@ DEAL_II_NAMESPACE_OPEN
  *   PETScWrappers::PreconditionBoomerAMG preconditioner(mpi_communicator, data);
  *   SolverControl linear_solver_control (dof_handler.n_dofs(), 1e-12,false,false);
  *   PETScWrappers::SolverCG  linear_solver(linear_solver_control,mpi_communicator);
- *   linear_solver.initialise(preconditioner);
+ *   linear_solver.initialize(preconditioner);
  *   SolverControl solver_control (100, 1e-9,false,false);
  *   SLEPcWrappers::SolverKrylovSchur eigensolver(solver_control,mpi_communicator);
  *   SLEPcWrappers::TransformationShift spectral_transformation(mpi_communicator);
@@ -90,7 +90,7 @@ DEAL_II_NAMESPACE_OPEN
  *
  * In order to support this usage case, different from PETSc wrappers, the classes
  * in this namespace are written in such a way that the underlying SLEPc objects
- * are initialised in constructors. By doing so one also avoid caching of different
+ * are initialized in constructors. By doing so one also avoid caching of different
  * settings (such as target eigenvalue or type of the problem); instead those are
  * applied straight away when the corresponding functions of the wrapper classes
  * are called.