0
@@ -1,8 +1,8 @@
0
 module Waves
0
 
0
-  # = Mappings
0
+  # = Mappings are the heart of Waves,
0
   #
0
-  # Mappings are the heart of Waves, the system whereby the madding crowd of slovenly requests are
0
+  # the system whereby the madding crowd of slovenly requests are
0
   # sorted, segregated, cleaned and dressed, put on their best behavior, and shunted through as complex 
0
   # a series of filters as you, the web developer, could wish for.
0
   # 
0
@@ -13,7 +13,7 @@ module Waves
0
   # 
0
   # There are three basic types of mapping:  responses, filters, and exception handlers
0
   #
0
-  # == Responses
0
+  # == Response mappings
0
   # 
0
   # A response mapping provides the primary action in answer to a HTTP request.  That is, the return value of an action
0
   # is written to the HTTP response body.  The default dispatcher runs only the first response mapping it finds 
0
@@ -32,13 +32,23 @@ module Waves
0
   #
0
   # == Exception handlers
0
   # 
0
-  # Handler mappings take an exception class as a constraint, in addition to any of the other possible constraints.
0
+  # A handler mapping takes an exception class as a constraint, in addition to any of the other possible constraints.
0
   # The default dispatcher uses an exception handler, if it can find one, to process exceptions thrown by 
0
   # the before, response, and after actions.
0
   # 
0
-  # = Constraints
0
+  # = Anatomy of a Mapping
0
   #
0
+  #   response :list, :get => [ :resources ] do
0
+  #     action( :all ) and render( :list )
0
+  #   end
0
   # 
0
+  # = Request Matching
0
+  #
0
+  # == Path Patterns
0
+  #
0
+  #   /uno/dos/tres/catorce
0
+  #   
0
+  #   :path => [ 'uno', 'dos', 'tres', 'catorce' ]
0
   
0
   module Mapping
0