chore: tidy up prompts

Author: mefellows

products.yml

@@ -27,9 +27,6 @@ paths:
                       # name: "pizza"
                       # version: "1.0.0"
                       # see https://github.com/apiaryio/dredd/issues/1430 for why
-        "400":
-          description: Invalid ID supplied
-          content: {}
   /product/{id}:
     get:
       summary: Find product by ID

src/test.instructions.txt

@@ -6,7 +6,5 @@
 * Use the native Jest expect (https://jestjs.io/docs/expect) matchers such as `toEqual` and `toBeTruthy`
 * Prefer the use of the async/await pattern when using Promises
 * Use the PactV4 interface
-* Use a 3 level hierarchy for tests
-  1. Level 1 should be the API under test as a `describe` block e.g. "🧱 Product API"
-  2. Level 2 should be the endpoint as a `describe` block e.g. "🔌 GET /products/:id", "POST /products"
-  3. Level 3 should be the scenario as a `test` block e.g. "🧪 Given a valid user, returns a 200", "Given an invalid user, returns a 400"
+* Omit the comments in the template given, as these are designed to help you understand the template's structure and intent
+* Remember, test all scenarios - 200, 400, 401 and 404