2014-11-17: add the requirements to the syntax-examples.

add the requirements to the syntax-examples.

diff --git a/docs/srfi.org b/docs/srfi.org
--- a/docs/srfi.org
+++ b/docs/srfi.org
@@ -151,7 +151,7 @@ The specification is separated into four
 
 ** Overview
 
-The basic rules for wisp-code can be defined in 4 rules, each of which emerges directly from a requirement:
+The basics of wisp syntax can be defined in 4 rules, each of which emerges directly from a requirement:
 
 *** Wisp syntax 1/4: function calls
 
@@ -171,6 +171,8 @@ becomes
 (newline)
 #+END_SRC
 
+/requirement: functions without preceding parenthesis./
+
 *** Wisp syntax 2/4: Continue Argument list
 
 The period:
@@ -191,6 +193,8 @@ becomes
 
 This also works with just one argument after the period. To start a line without a function call, you have to prefix it with a period followed by whitespace.[fn:2]
 
+/requirement: continue the argument list of a function after intermediate call to another function./
+
 *** Wisp syntax 3/4: Double Parens
 
 The colon:[fn:3]
@@ -213,6 +217,8 @@ becomes
   (body))
 #+END_SRC
 
+/requirement: represent code with two adjadent blocks in double-parentheses./
+
 *** Wisp syntax 4/4: Resilient Indentation
 
 The underscore (optional):
@@ -235,6 +241,7 @@ becomes
   (body))
 #+END_SRC
  
+/requirement: share code in environments which do not preserve whitespace./
 
 *** Summary