commit 9f0aaf6bfc6557cc30f782a7d97222a44e6b4196
Author: Mark Claypool <claypool@cs.wpi.edu>
Date:   Thu Feb 2 14:04:29 2023 -0500

    Updates

diff --git a/phd-proposal.md b/phd-proposal.md
index a7d178d..ad5ef7c 100644
--- a/phd-proposal.md
+++ b/phd-proposal.md
@@ -1,6 +1,6 @@
 ---
 pagetitle: Writing a PhD Proposal
-version: 0.9
+version: 0.91
 ---
 
 # Writing a PhD Proposal
@@ -10,22 +10,27 @@ should include well-defined boundaries - what is in, what is out - of
 the research space.  Getting this "right" (size and shape) for a PhD
 is key.
 
-Produce aims.  These should be objective in that you
-can check them off.
+The opening should setup the problem statement. Motivate the area,
+describe state of the art, indicate what is *not* done. This leads the
+problem statement.  It doesn't have to be monolithic - there could be
+sub-problems in it.
+
+Then, come up with research aims.  These are objective "chucks" of
+research (think of a research paper, if that helps) that all together,
+will address the problem.
 
 e.g., 
 
-Aim 1: Model target selection time from MMM dataset
+Aim 1: Model target selection time using an existing dataset.
 
-Aim 2: Design and conduct user study measuring performance for
-competitive FPS.
+Aim 2: Assess how user accuracy varies with latency in a shooter game.
 
 Aim 3: ...
 
 The proposal will then have a series of methodologies towards
-addressing each aim.  You might create tasks for each methodology that
-you can work toward and check off.  This makes the work "concrete" and
-allows for planning.
+addressing each aim.  There might be tasks for each methodology that
+can be worked toward and check off.  This makes the work "concrete"
+and allows for planning.
 
 Provide information, preferably visible (e.g., color-coded table,
 maybe with three levels) showing progress towards the tasks and aims.