chore(spec): fix example used within spec (#288)

* chore(spec): improve runtime expression examples and fix typo

Author: frankkilcommins

versions/1.0.0.md

@@ -868,19 +868,19 @@ The runtime expression is defined by the following [ABNF](https://tools.ietf.org
 
 #### Examples
 
-| Source Location | example expression | notes |
-| ---- | :---- | :---- |
-| HTTP Method | `$method` | The allowable values for the `$method` will be those for the HTTP operation. |
-| Requested media type | `$request.header.accept` | |
-| Request parameter | `$request.path.id` | Request parameters MUST be declared in the `parameters` section of the parent operation or they cannot be evaluated. This includes request headers. |
-| Request body property | `$request.body#/user/uuid` | In operations which accept payloads, references may be made to portions of the `requestBody` or the entire body. |
-| Request URL | `$url` | |
-| Response value | `$response.body#/status` | In operations which return payloads, references may be made to portions of the response body or the entire body. |
-| Response header | `$response.header.Server` | Single header values only are available |
-| workflow input | `$inputs.username` or `$workflows.foo.inputs.username` | Single input values only are available |
-| Step output value | `$steps.someStep.pets` | In situations where the output named property return payloads, references may be made to portions of the response body or the entire body. |
-| Workflow output value | `$outputs.bar` or `$workflows.foo.outputs.bar` | Single input values only are available |
-| Components parameter | `$components.parameters.foo` | Accesses a foo parameter defined within the Components Object. |
+Source Location | example expression  | notes
+---|:---|:---|
+HTTP Method            | `$method`         | The allowable values for the `$method` will be those for the HTTP operation.
+Requested media type | `$request.header.accept`        |
+Request parameter      | `$request.path.id`        | Request parameters MUST be declared in the `parameters` section of the parent operation or they cannot be evaluated. This includes request headers.
+Request body property   | `$request.body#/user/uuid`   | In operations which accept payloads, references may be made to portions of the `requestBody` or the entire body.
+Request URL            | `$url`            |
+Response value         | `$response.body#/status`       |  In operations which return payloads, references may be made to portions of the response body or the entire body.
+Response header        | `$response.header.Server` |  Single header values only are available
+workflow input        | `$inputs.username` or `$workflows.foo.inputs.username` |  Single input values only are available
+Step output value        | `$steps.someStepId.outputs.pets` |  In situations where the output named property return payloads, references may be made to portions of the response body (e.g., `$steps.someStepId.outputs.pets#/0/id`) or the entire body.
+Workflow output value | `$outputs.bar` or `$workflows.foo.outputs.bar` |  In situations where the output named property return payloads, references may be made to portions of the response body (e.g., `$workflows.foo.outputs.mappedResponse#/name`) or the entire body.
+Components parameter | `$components.parameters.foo` | Accesses a foo parameter defined within the Components Object.
 
 Runtime expressions preserve the type of the referenced value.
 Expressions can be embedded into string values by surrounding the expression with `{}` curly braces.