diff --git a/checkin_notes b/checkin_notes
index 310a869c3f..8f702760fe 100755
--- a/checkin_notes
+++ b/checkin_notes
@@ -1,3 +1,4 @@
+
 Rom    4 Jan 2006
     - Branding update for GridRepublic
     
@@ -8195,3 +8196,10 @@ Charlie 31 July 2006
             macbadgemask.xpm (Added)
             macsnoozebadge.xpm
             macdisconnectbadge.xpm
+
+Bruce 31 July 2006
+    - Documentation on <resend_lost_results>
+
+    doc/
+        project_options.php
+
diff --git a/doc/project_options.php b/doc/project_options.php
index 4198e33b81..7c64576c4e 100644
--- a/doc/project_options.php
+++ b/doc/project_options.php
@@ -258,7 +258,20 @@ list_item("resend_lost_results",
     in scheduler request,
     resend any in-progress results not in the list.
     This is recommended;
-    it should increase the efficiency of your project"
+    it should increase the efficiency of your project.  Note that
+    in an ideal world, it would never be necessary to resend results.
+    The first time that they were sent from the server, the client would
+    receive them and no resending would be needed.  However it is the
+    experience of several projects that, for reasons that are
+    not well understood, a BOINC client sometimes fails to receive the
+    scheduler reply.  This flag addresses that issue: it causes the SAME results to be RESENT
+    by the scheduler, if the client has failed to receive them.
+    It works as follows.  In its scheduler request, the BOINC
+    client includes a list of results that it has already received.  The scheduler
+    checks these against the database to be sure that the client has received
+    ALL results which should be present.  If there are missing results on
+    client, and this flag is set, then those results are RESENT by the
+    scheduler before any new work is sent.""
 );
 list_item("min_passwd_length",
     "Minimum length of user passwords.  Default is 6."