From 977e2646eb97dc40d8133d9a617030980dc72155 Mon Sep 17 00:00:00 2001 From: Wolfgang Bangerth Date: Wed, 27 Jul 2016 11:21:40 -0600 Subject: [PATCH] Clarify that update_once/each is not part of a public interface. --- doc/doxygen/headers/update_flags.h | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/doxygen/headers/update_flags.h b/doc/doxygen/headers/update_flags.h index 1c13573330..9f54646b91 100644 --- a/doc/doxygen/headers/update_flags.h +++ b/doc/doxygen/headers/update_flags.h @@ -173,7 +173,8 @@ * * To accommodate this structure, both mappings and finite element classes * may internally split the update flags into two sets commonly referenced as - * update_once and update_each. The former contains + * update_once and update_each (though these names + * do not appear in any public interfaces). The former contains * all those pieces of information that can be pre-computed once at the * time the FEValues object starts to interact with a mapping or * finite element, whereas the latter contains those flags corresponding to @@ -236,7 +237,7 @@ * * Once initialization is over and we call FEValues::reinit, FEFaceValues::reinit * or FESubfaceValues::reinit to move to a concrete cell or face, we need - * to calculate the update_each kinds of data. This done in the following + * to calculate the "update_each" kinds of data. This is done in the following * functions: * * - * This is, where the actual data fields for FEValues, stored in + * This is where the actual data fields for FEValues, stored in * internal::FEValues::MappingRelatedData and * internal::FEValues::FiniteElementRelatedData objects, are * computed. These functions call the function in Mapping first, such -- 2.39.5