docs: add :lines: 2-

Author: kenjis

user_guide_src/source/testing/feature.rst

@@ -41,13 +41,15 @@ To do this, you use the ``call()`` method.
       included for consistency.
 
 .. literalinclude:: feature/002.php
+   :lines: 2-
 
 Shorthand Methods
 -----------------
 
 Shorthand methods for each of the HTTP verbs exist to ease typing and make things clearer:
 
 .. literalinclude:: feature/003.php
+   :lines: 2-
 
 Setting Different Routes
 ------------------------
@@ -56,6 +58,7 @@ You can use a custom collection of routes by passing an array of "routes" into t
 override any existing routes in the system:
 
 .. literalinclude:: feature/004.php
+   :lines: 2-
 
 Each of the "routes" is a 3 element array containing the HTTP verb (or "add" for all),
 the URI to match, and the routing destination.
@@ -68,6 +71,7 @@ of key/value pairs that should exist within the ``$_SESSION`` variable when this
 that the current values of ``$_SESSION`` should be used. This is handy for testing authentication and more.
 
 .. literalinclude:: feature/005.php
+   :lines: 2-
 
 Setting Headers
 ---------------
@@ -76,6 +80,7 @@ You can set header values with the ``withHeaders()`` method. This takes an array
 passed as a header into the call:
 
 .. literalinclude:: feature/006.php
+   :lines: 2-
 
 Bypassing Events
 ----------------
@@ -84,6 +89,7 @@ Events are handy to use in your application, but can be problematic during testi
 to send out emails. You can tell the system to skip any event handling with the ``skipEvents()`` method:
 
 .. literalinclude:: feature/007.php
+   :lines: 2-
 
 .. _feature-formatting-the-request:
 
@@ -100,6 +106,7 @@ body of the request in the given format.
 This will also set the `Content-Type` header for your request accordingly.
 
 .. literalinclude:: feature/008.php
+   :lines: 2-
 
 .. _feature-setting-the-body: