commit 477b8873d68bc2a0b02b18b32092e752b0d7700b
Author: Mark Claypool <claypool@cs.wpi.edu>
Date:   Sun Aug 14 19:28:52 2022 -0400

    Updates

diff --git a/methodology.md b/methodology.md
index bd297fe..6a05dec 100644
--- a/methodology.md
+++ b/methodology.md
@@ -1,19 +1,19 @@
 ---
 pagetitle: Writing the Methodology
-version: 1.2
+version: 1.3
 ---
 
 # Writing the Methodology
 
 The Methodology chapter provides details on the approach you used to
-address your problem.
+address the problem you specified in your problem statement.
 
 It is often helpful to think of *verbs* that you used to describe the
 work.  e.g., 
 
-    1. *Design* game that isolates a player action. 
-    2. *Implement* method to gather network traces
-    3. ...
+1. *Design* a game that isolates a player action. 
+2. *Implement* a method to gather network traces
+3. ...
 
 A common structure would briefly (1-2 sentences) restate the problem.
 

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

    Updates

diff --git a/methodology.md b/methodology.md
index 7b22ce5..bd297fe 100644
--- a/methodology.md
+++ b/methodology.md
@@ -1,6 +1,9 @@
-# Methodology Writing Guidelines
+---
+pagetitle: Writing the Methodology
+version: 1.2
+---
 
-v1.1
+# Writing the Methodology
 
 The Methodology chapter provides details on the approach you used to
 address your problem.

commit 5d315f5c8cdbfd2b4715ef1153e2d5cadb0fe093
Author: Mark Claypool <claypool@cs.wpi.edu>
Date:   Mon Mar 8 17:54:42 2021 -0500

    Updates

diff --git a/methodology.md b/methodology.md
index 4eaa408..7b22ce5 100644
--- a/methodology.md
+++ b/methodology.md
@@ -9,8 +9,8 @@ It is often helpful to think of *verbs* that you used to describe the
 work.  e.g., 
 
     1. *Design* game that isolates a player action. 
-	2. *Implement* method to gather network traces
-	3. ...
+    2. *Implement* method to gather network traces
+    3. ...
 
 A common structure would briefly (1-2 sentences) restate the problem.
 

commit 1b6f237249e0a07951642a50d0bb522a10207528
Author: Mark Claypool <claypool@cs.wpi.edu>
Date:   Tue Jan 28 17:14:59 2020 -0500

    Updates

diff --git a/methodology.md b/methodology.md
new file mode 100644
index 0000000..4eaa408
--- /dev/null
+++ b/methodology.md
@@ -0,0 +1,34 @@
+# Methodology Writing Guidelines
+
+v1.1
+
+The Methodology chapter provides details on the approach you used to
+address your problem.
+
+It is often helpful to think of *verbs* that you used to describe the
+work.  e.g., 
+
+    1. *Design* game that isolates a player action. 
+	2. *Implement* method to gather network traces
+	3. ...
+
+A common structure would briefly (1-2 sentences) restate the problem.
+
+Then, have a list of steps up front, like the above.
+
+After that, there would be a sub-section, one for each step in the
+list that provides details.
+
+For the details, what is often needed is *design rationale* that
+provides reasons for the choices made in each step of the methodology.
+For example, why was a particular toolkit or language chosen?  Why was
+the range of parameters for evaluation used?  What alternatives were
+considered but discarded?
+
+Where appropriate, the Methodology chapter can include details on how
+an evaluation was done (e.g., through experiments).  Sometimes, such
+details would be in a different chapter, however.
+
+In most cases, the results from evaluation (typically in the form of
+tables and charts) is a separate chapter and *not* part of the
+Methodology chapter.