From d0084d7f1b2c41ccf8808d591904d25c7ba838a7 Mon Sep 17 00:00:00 2001 From: Nicole Hayes Date: Tue, 6 Aug 2019 20:34:24 -0400 Subject: [PATCH] Fixed typos and wording in step-20 --- doc/news/changes/minor/20190807NicoleHayes | 3 +++ examples/step-20/step-20.cc | 12 ++++++------ 2 files changed, 9 insertions(+), 6 deletions(-) create mode 100644 doc/news/changes/minor/20190807NicoleHayes diff --git a/doc/news/changes/minor/20190807NicoleHayes b/doc/news/changes/minor/20190807NicoleHayes new file mode 100644 index 0000000000..6d9ce3eb7d --- /dev/null +++ b/doc/news/changes/minor/20190807NicoleHayes @@ -0,0 +1,3 @@ +Changed: Fixed some wording and minor typos in step-20 documentation. +
+(Nicole Hayes, 2019/08/07) \ No newline at end of file diff --git a/examples/step-20/step-20.cc b/examples/step-20/step-20.cc index e304fadb00..c898d57861 100644 --- a/examples/step-20/step-20.cc +++ b/examples/step-20/step-20.cc @@ -116,7 +116,7 @@ namespace Step20 // Our next task is to define the right hand side of our problem (i.e., the // scalar right hand side for the pressure in the original Laplace - // equation), boundary values for the pressure, as well as a function that + // equation), boundary values for the pressure, and a function that // describes both the pressure and the velocity of the exact solution for // later computations of the error. Note that these functions have one, one, // and dim+1 components, respectively, and that we pass the @@ -166,7 +166,7 @@ namespace Step20 // And then we also have to define these respective functions, of // course. Given our discussion in the introduction of how the solution - // should look like, the following computations should be straightforward: + // should look, the following computations should be straightforward: template double RightHandSide::value(const Point & /*p*/, const unsigned int /*component*/) const @@ -220,7 +220,7 @@ namespace Step20 // real-life porous media flow simulations, and we would like to use the // opportunity to demonstrate the technique to use tensor valued functions. // - // Possibly unsurprising, deal.II also has a base class not only for scalar + // Possibly unsurprisingly, deal.II also has a base class not only for scalar // and generally vector-valued functions (the Function base // class) but also for functions that return tensors of fixed dimension and // rank, the TensorFunction template. Here, the function under @@ -257,9 +257,9 @@ namespace Step20 std::vector> & values) const { // The value we are going to store for a given point does not depend on its - // coordinates and we use the `points` object only for checking that the + // coordinates, and we use the `points` object only for checking that the // `values` object has the correct size. In release mode, `AssertDimension` - // is defined empty and the compiler will complain that the `points` object + // is defined empty, and the compiler will complain that the `points` object // is unused. The following line silences this warning. (void)points; AssertDimension(points.size(), values.size()); @@ -334,7 +334,7 @@ namespace Step20 // velocities and pressures are not intermingled: First all velocity // degrees of freedom, then all pressure DoFs. This way, the global matrix // separates nicely into a $2 \times 2$ system. To achieve this, we have to - // renumber degrees of freedom base on their vector component, an + // renumber degrees of freedom based on their vector component, an // operation that conveniently is already implemented: DoFRenumbering::component_wise(dof_handler); -- 2.39.5