Typo fixes

versions/1.0.0.md

@@ -622,12 +622,12 @@ This object cannot be extended with additional properties and any properties add
 
 #### Criterion Object
 
-An object used to specify the context, conditions, and condition types that can be used to prove or satisfy criteria specified in Step Object `successCriteria`, Success Action Object `criteria`, and Failure Action Object `criteria`.
+An object used to specify the context, conditions, and condition types that can be used to prove or satisfy assertions specified in Step Object `successCriteria`, Success Action Object `criteria`, and Failure Action Object `criteria`.
 
 There are three flavors of conditions supported:
-- simple - where use of basic literals, operators, and loose comparisons are used in combination with [Runtime Expressions](#runtime-expressions)
-- regex - where a regex pattern is applied on the supplied context (defined by a [Runtime Expression](#runtime-expressions))
-- JSONPath - where a JSONPath expression is applied. The root node context is defined by a [Runtime Expression](#runtime-expressions)
+- simple - where basic literals, operators, and loose comparisons are used in combination with [Runtime Expressions](#runtime-expressions)
+- regex - where a regex pattern is applied on the supplied context. The context is defined by a [Runtime Expression](#runtime-expressions).
+- JSONPath - where a JSONPath expression is applied. The root node context is defined by a [Runtime Expression](#runtime-expressions).
 
 ##### Literals
 As part of a condition expression, you can use `boolean`, `null`, `number`, or `string` data types.
@@ -660,8 +660,8 @@ String comparisons `SHOULD` be case insensitive.
 Field Name | Type | Description
 ---|:---:|---
 <a name="criterionContext"></a>context | `{expression}` | A [runtime expression](#runtime-expressions) used to set the context for the condition to be applied on. If `type` is specified, then the `context` MUST be provided (e.g. `$response.body` would set the context that a JSONPath query could be applied to).
-<a name="criterionCondition"></a>condition | `string` | **REQUIRED**. The condition to apply. Conditions can be simple (e.g. `$statusCode == 200` which applies a operator on a value obtained from a runtime expression), or a regex, or a JSONPath expression. For regex and [JSONPath](https://datatracker.ietf.org/doc/draft-ietf-jsonpath-base/21/), the `type` and `context` must be specified.
-<a name="criterionType"></a>type | `string` | The type of condition to be applied. If specified, the options allowed are `regex` or `JSONPath`. If omitted, then the condition is assumed to be a simple condition which at most combines literals, operators and [Runtime Expressions](#runtime-expressions).
+<a name="criterionCondition"></a>condition | `string` | **REQUIRED**. The condition to apply. Conditions can be simple (e.g. `$statusCode == 200` which applies a operator on a value obtained from a runtime expression), or a regex, or a JSONPath expression. For regex and [JSONPath](https://datatracker.ietf.org/doc/draft-ietf-jsonpath-base/21/), the `type` and `context` MUST be specified.
+<a name="criterionType"></a>type | `string` | The type of condition to be applied. If specified, the options allowed are `regex` or `JSONPath`. If omitted, then the condition is assumed to be simple, which at most combines literals, operators and [Runtime Expressions](#runtime-expressions).
 
 
 This object _MAY_ be extended with [Specification Extensions](#specificationExtensions).