wire_protocol.feature in cucumber-0.10.1

- old
+ new

@@ -9,11 +9,11 @@
   # 'programming language' abstraction, and allows step definitions to be
   # implemented and invoked on any platform.
   #
   # Communication is over a TCP socket, which Cucumber connects to when it finds
   # a definition file with the .wire extension in the step_definitions folder
-  # (or other load path).
+  # (or other load path).  Note that these files are rendered with ERB when loaded.
   #
   # Cucumber sends the following request messages out over the wire:
   #
   #   * step_matches   : this is used to find out whether the wire server has a
   #                      definition for a given step
@@ -29,10 +29,10 @@
   #                      raised.
   #
   # Some messages support more responses - see below for details.
   #
   # A WirePacket flowing in either direction is formatted as a JSON-encoded
-  # string, with a newline character signalling the end of a packet. See the
+  # string, with a newline character signaling the end of a packet. See the
   # specs for Cucumber::WireSupport::WirePacket for more details.
   #
   # These messages are described in detail below, with examples.
   #
 