From 0d34527a899eb7c9eba0d7832ac7a3972dd58112 Mon Sep 17 00:00:00 2001 From: Stefano Zampini Date: Sat, 26 Nov 2022 17:25:57 +0300 Subject: [PATCH] Minor changes to examples comments --- examples/step-15/step-15.cc | 2 +- examples/step-17/step-17.cc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/examples/step-15/step-15.cc b/examples/step-15/step-15.cc index 469ff2c321..09e5c42693 100644 --- a/examples/step-15/step-15.cc +++ b/examples/step-15/step-15.cc @@ -551,7 +551,7 @@ namespace Step15 // fixed, they are of course no "real" degrees of freedom and so, strictly // speaking, we shouldn't have assembled entries in the residual vector // for them. However, as we always do, we want to do exactly the same - // thing on every cell and so we didn't not want to deal with the question + // thing on every cell and so we didn't want to deal with the question // of whether a particular degree of freedom sits at the boundary in the // integration above. Rather, we will simply set to zero these entries // after the fact. To this end, we need to determine which degrees diff --git a/examples/step-17/step-17.cc b/examples/step-17/step-17.cc index 144606dde9..a6da2c42e5 100644 --- a/examples/step-17/step-17.cc +++ b/examples/step-17/step-17.cc @@ -561,7 +561,7 @@ namespace Step17 // not want to make the matrix symmetric is because this // would require us to write into column entries that actually // reside on other processes, i.e., it involves communicating - // data. This is always expensive. + // data. // // Experience tells us that CG also works (and works almost as // well) if we don't remove the columns associated with boundary -- 2.39.5