commit 787961fae13143d13649bfc83f59fa1a9a3c1519
Author: Mark Claypool <claypool@cs.wpi.edu>
Date:   Wed Feb 28 16:27:46 2024 -0500

    Updates

diff --git a/conclusion.md b/conclusion.md
index ebc4bf8..c2504b3 100644
--- a/conclusion.md
+++ b/conclusion.md
@@ -1,6 +1,6 @@
 ---
 pagetitle: Writing the Conclusion
-version: 1.3
+version: 1.4
 ---
 
 # Writing the Conclusion 
@@ -19,7 +19,7 @@ Results chapter usually has low-level details, here they are coalesced
 and brought to a summation at a higher-level.  Typically, there are
 2-4 paragraphs with such conclusions.
 
-**Tip:* avoid unmeasureable outcomes (opinions) and superlatives
+**Tip:** avoid unmeasureable outcomes (opinions) and superlatives
 (e.g., "our work was the best" or "our system was super necessary").
 Instead, speak to the facts of what the project designed, built and
 evaluated.