From 5d4dec4ecb9cea341f6b9b425b1a90f454f3e17c Mon Sep 17 00:00:00 2001
From: Wolfgang Bangerth <bangerth@colostate.edu>
Date: Mon, 13 May 2019 02:50:57 -0600
Subject: [PATCH] Provide a much nicer way to format a table in step-56.

---
 examples/step-56/doc/results.dox | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/examples/step-56/doc/results.dox b/examples/step-56/doc/results.dox
index bace019770..1f83e66bde 100644
--- a/examples/step-56/doc/results.dox
+++ b/examples/step-56/doc/results.dox
@@ -17,7 +17,7 @@ see for example Ern/Guermond "Theory and Practice of Finite Elements", Section
 element as an example (this is what is done in the code, but is easily
 changed in <code>main()</code>):
 
-<table align="center" border="1">
+<table align="center" class="doxtable">
   <tr>
     <th>&nbsp;</th>
     <th>L2 Velocity</th>
@@ -66,7 +66,7 @@ CG. The preconditioner for CG is then either ILU or GMG.
 The following table summarizes solver iterations, timings, and virtual
 memory (VM) peak usage:
 
-<table align="center" border="1">
+<table align="center" class="doxtable">
 <tr>
   <th></th>
   <th colspan="3">General</th>
@@ -173,7 +173,7 @@ memory (VM) peak usage:
 </tr>
 </table>
 
-As can be seen from the table,
+As can be seen from the table:
 
 1. UMFPACK uses large amounts of memory, especially in 3d. Also, UMFPACK
 timings do not scale favorably with problem size.
-- 
2.39.5