From 4276f7531b9e7e4a6de5cfd11e81118a7cf9dad2 Mon Sep 17 00:00:00 2001 From: David Wells Date: Fri, 17 Apr 2020 11:33:46 -0400 Subject: [PATCH] step-8: make text agree with code. --- examples/step-8/step-8.cc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/examples/step-8/step-8.cc b/examples/step-8/step-8.cc index 86ddbf978f..c3dfd3aeb1 100644 --- a/examples/step-8/step-8.cc +++ b/examples/step-8/step-8.cc @@ -538,9 +538,9 @@ namespace Step8 // The run function does the same things as in step-6, for // example. This time, we use the square [-1,1]^d as domain, and we refine - // it twice globally before starting the first iteration. + // it globally four times before starting the first iteration. // - // The reason for refining twice is a bit accidental: we use the QGauss + // The reason for refining is a bit accidental: we use the QGauss // quadrature formula with two points in each direction for integration of the // right hand side; that means that there are four quadrature points on each // cell (in 2D). If we only refine the initial grid once globally, then there @@ -569,8 +569,8 @@ namespace Step8 // The conclusion needs to be: while of course we will not choose the // initial grid to be well-suited for the accurate solution of the problem, // we must at least choose it such that it has the chance to capture the - // important features of the solution. In this case, it needs to be able - // to see the right hand side. Thus, we refine twice globally. (Any larger + // important features of the solution. In this case, it needs to be able to + // see the right hand side. Thus, we refine globally four times. (Any larger // number of global refinement steps would of course also work.) template void ElasticProblem::run() -- 2.39.5