We don't actually use Epetra_Map by hand in this program.

git-svn-id: https://svn.dealii.org/trunk@24484 0785d39b-7218-0410-832d-ea1e28bc413d

diff --git a/deal.II/examples/step-32/doc/intro.dox b/deal.II/examples/step-32/doc/intro.dox
index 9e52b89d3ec1d3882206e106ae172ab08f422dc9..b0b2e95195990769e75d21b284e9da62ee482163 100644 (file)
--- a/deal.II/examples/step-32/doc/intro.dox
+++ b/deal.II/examples/step-32/doc/intro.dox
@@ -690,14 +690,12 @@ are part of Trilinos' Epetra library of basic linear algebra and tool classes:
   producing a communicator object that only encompasses this subset of
   machines; there is really no compelling reason to do so here, however.
 
-<li> The Epetra_Map class is used to describe which elements of a vector or which
-  rows of a matrix reside on a given machine that is part of a
+<li> The IndexSet class is used to describe which elements of a vector or which
+  rows of a matrix should reside on the current machine that is part of a
   communicator. To create such an object, you need to know (i) the total
-  number of elements or rows, (ii) the number of elements or rows you want to
-  store on the current machine, and (iii) which communicator enumerates the
-  machines that we want this matrix or vector be stored on. We will set up
-  these maps (which we call <code>partitioners</code> in our code, since we
-  believe this is a better word) in the
+  number of elements or rows, (ii) the indices of the elements you want to
+  store locally. We will set up
+  these <code>partitioners</code> in the
   <code>BoussinesqFlowProblem::setup_dofs</code> function below and then hand
   it to every %parallel object we create.