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.

commit d364d8db584772c78f8e40ea51c8e2a7572c19ef
Author: Mark Claypool <claypool@cs.wpi.edu>
Date:   Fri Dec 15 19:40:01 2023 -0500

    Updates

diff --git a/conclusion.md b/conclusion.md
index 8b326d9..ebc4bf8 100644
--- a/conclusion.md
+++ b/conclusion.md
@@ -1,6 +1,6 @@
 ---
 pagetitle: Writing the Conclusion
-version: 1.2
+version: 1.3
 ---
 
 # Writing the Conclusion 
@@ -19,6 +19,11 @@ 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
+(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.
+
 The Conclusion chapter does *not* need a post-mortem type of
 discussion (e.g., "what went wrong" or "what we could have done
 better").  If such material is needed for the report, it should be in

commit 0a3a035cc794a63af63c86c0c68decfdb2d808f2
Author: Mark Claypool <claypool@cs.wpi.edu>
Date:   Mon Aug 8 13:58:58 2022 -0400

    Updates

diff --git a/conclusion.md b/conclusion.md
index 7c40ab5..8b326d9 100644
--- a/conclusion.md
+++ b/conclusion.md
@@ -1,6 +1,9 @@
-# Conclusion Writing Guidelines
+---
+pagetitle: Writing the Conclusion
+version: 1.2
+---
 
-v1.1
+# Writing the Conclusion 
 
 The Conclusion chapter typically opens with a brief reminder of the
 domain (about one paragraph) and the problem that was addressed

commit 13647cf9078d66b1182de2b31c5fbd3f4fbedc0c
Author: Mark Claypool <claypool@cs.wpi.edu>
Date:   Fri Sep 18 09:12:35 2020 -0400

    Updates

diff --git a/conclusion.md b/conclusion.md
index 478072f..7c40ab5 100644
--- a/conclusion.md
+++ b/conclusion.md
@@ -1,10 +1,11 @@
 # Conclusion Writing Guidelines
 
-v1.0
+v1.1
 
 The Conclusion chapter typically opens with a brief reminder of the
 domain (about one paragraph) and the problem that was addressed
-(another paragraph).
+(another paragraph).  This may sometimes include a paragraph
+summarizing what was done to address the problem (another paragraph).
 
 Then, the chapter should actually conclude (i.e., not just summarize)
 in light of the original problem that was addressed by the project.

commit e5cfe6bf704f9f36d0c26fae9e94d6228e50907b
Author: Mark Claypool <claypool@cs.wpi.edu>
Date:   Tue Feb 26 12:53:28 2019 -0500

    Updates

diff --git a/conclusion.md b/conclusion.md
new file mode 100644
index 0000000..478072f
--- /dev/null
+++ b/conclusion.md
@@ -0,0 +1,23 @@
+# Conclusion Writing Guidelines
+
+v1.0
+
+The Conclusion chapter typically opens with a brief reminder of the
+domain (about one paragraph) and the problem that was addressed
+(another paragraph).
+
+Then, the chapter should actually conclude (i.e., not just summarize)
+in light of the original problem that was addressed by the project.
+
+Usually, this involves concretely describing the main findings from
+the results and evaluation that addressed the problem.  While the
+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.
+
+The Conclusion chapter does *not* need a post-mortem type of
+discussion (e.g., "what went wrong" or "what we could have done
+better").  If such material is needed for the report, it should be in
+a "Discussion" chapter (although most reports will not have this).
+
+