* need a <code>.pvtu</code> file that describes which VTU files form
* a group. The DataOutInterface::write_pvtu_record() function can
* generate such a master record. Likewise,
- * DataOutInterface::write_visit_record() does the same for VisIt.
+ * DataOutInterface::write_visit_record() does the same for older versions of VisIt (before 2.5.1).
* Finally, for time dependent problems, you may also want to look
* at DataOutInterface::write_pvd_record()
*
* function can generate such a
* master record. Likewise,
* DataOutInterface::write_visit_record()
- * does the same for VisIt. Finally,
+ * does the same for older versions of VisIt (before 2.5.1). Finally,
* DataOutInterface::write_pvd_record()
* can be used to group together
* the files that jointly make up
* DataOutInterface::write_pvd_record()
* function.
*
- * @note At the time of writing,
- * the other big VTK-based
- * visualization program, VisIt,
+ * @note Older versions of VisIt (before 2.5.1),
* can not read <code>pvtu</code>
* records. However, it can read
* visit records as written by
/**
* This function is the exact equivalent of the write_pvtu_record()
- * function but for the VisIt visualization program and for one visualization graph
+ * function but for older versions of the VisIt visualization program and for one visualization graph
* (or one time step only). See there for the purpose of this function.
*
* This function is documented in the "Creating a master file for