Allow booleans in place of any top-level schema field (#2609)

* fix: erroneous reference to v3.0 of the spec as if it was the current version

Signed-off-by: Mike Ralphson <[email protected]>

* Allow boolean values for top level schemaObjects

Signed-off-by: Mike Ralphson <[email protected]>

Author: MikeRalphson

versions/3.1.1.md

@@ -2306,7 +2306,7 @@ $ref: definitions.yaml#/Pet
 #### <a name="schemaObject"></a>Schema Object
 
 The Schema Object allows the definition of input and output data types.
-These types can be objects, but also primitives and arrays. This object is a superset of the [JSON Schema Specification Draft 2020-12](https://tools.ietf.org/html/draft-bhutton-json-schema-00).
+These types can be objects, but also primitives and arrays. This object is a superset of the [JSON Schema Specification Draft 2020-12](https://tools.ietf.org/html/draft-bhutton-json-schema-00). The empty schema (which allows any instance to validate) MAY be represented by the `boolean` value `true` and a schema which allows no instance to validate MAY be represented by the `boolean` value `false`.
 
 For more information about the properties, see [JSON Schema Core](https://tools.ietf.org/html/draft-bhutton-json-schema-00) and [JSON Schema Validation](https://tools.ietf.org/html/draft-bhutton-json-schema-validation-00).
 
@@ -2712,7 +2712,7 @@ This object MAY be extended with [Specification Extensions](#specificationExtens
 
 The discriminator object is legal only when using one of the composite keywords `oneOf`, `anyOf`, `allOf`.
 
-In OAS 3.0, a response payload MAY be described to be exactly one of any number of types:
+In OAS 3.x, a response payload MAY be described to be exactly one of any number of types:
 
 ```yaml
 MyResponseType: