diff --git a/Summit2Day1.md b/Summit2Day1.md
index 7eb08b5..97b6c94 100644
--- a/Summit2Day1.md
+++ b/Summit2Day1.md
@@ -51,7 +51,8 @@ expected vs required vs known, k-of-N, H, points, understandability
     - challenge of identifying reliability of nodes
     - Brian says client/gateway should expect user to teach it what sort of
       grid they expect, so it can bail when expectations aren't met
-    - Shawn would prefer scheme where client measures reliability itself,
+    - Shawn would prefer scheme where client measures node reliability itself
+      (though in the near term allows the user to specify node reliabilities),
       sets N to the number of servers currently accepting shares, sets H
       slightly below N (to improve upload availability) and computes and
       uses a k that maximizes performance (or minimizes cost) while achieving