computations. Instead, this data is now treated as a first-class
citizen in \dealii{}.
-\texttt{CellDataStorage} can work with arbitrary kinds of data defined
-to live on a cell as long as the corresponding data type implements a
-certain interface. As an example,
-the abstract class \texttt{TransferableQuadraturePointData} provides
-a generic interface to facilitate several low-level operations
-that were previously tedious or technically challenging to implement.
-For instance, when a user's custom data type is derived from \texttt{TransferableQuadraturePointData}
--- a data type that stores information at the quadrature points of cells using
-\texttt{CellDataStorage} --,
+\texttt{CellDataStorage} can work with arbitrary kinds of data defined to live on a cell
+as long as the corresponding data type implements a default constructor.
+Additionally, when a user's custom data type is derived from \texttt{TransferableQuadraturePointData}
+and thereby implements certain interface,
then the \texttt{parallel::distributed::ContinuousQuadratureDataTransfer} class
-can transfer this data during
-$h$-adaptive refinement from parent to children and the other way around
+can transfer this data during $h$-adaptive refinement from parent cell to children
(interpreting the data on quadrature points as discrete representations of an
underlying continuous field),
as well as from one processor to another during repartitioning.