Outlining optional modules.

1 files changed, 6 insertions, 5 deletions

diff --git a/TESTING.md b/TESTING.md
index cb06e74..f7ecea5 100644
--- a/TESTING.md
+++ b/TESTING.md
@@ -11,9 +11,12 @@ In general, the process for each `.yml` file is as follows:
   1. Ensure that each element of the 'partials' hash (if it exists) is
      stored in a place where the interpreter will look for it.
 
-  2. If your implementation supports lambdas, ensure that each member of 'data'
-     tagged with '!code' is properly processed into a language-specific
-     lambda reference.
+  2. If your implementation will not support lambdas, feel free to skip over
+     the optional '~lambdas.yml' file.
+
+  2.1. If your implementation will support lambdas, ensure that each member of
+       'data' tagged with '!code' is properly processed into a language-
+       specific lambda reference.
 
       *   e.g. Given this YAML data hash:
 
@@ -27,8 +30,6 @@ In general, the process for each `.yml` file is as follows:
       *   If your implementation language does not currently have lambda
           examples in the spec, feel free to implement them and send a pull
           request.
-      *   If your implementation does not support lambdas, feel free to skip
-          over the `lambdas.yml` file.
 
   3. Render the template (stored in the 'template' key) with the given 'data'
      hash.