typo: scheme -> schema
typo: scheme -> schema
MODIFY
versions/3.0.md
versions/3.0.md
@@ -1870,7 +1870,7 @@ As with all links, it at the the clients' discretion to follow them, and permiss
### Example
-The example below shows how relationships in the BitBucket API can be represented with the proposed OAI link scheme. This example uses `operationId` values to link responses to possible operations.
+The example below shows how relationships in the BitBucket API can be represented with the link schema. This example uses `operationId` values to link responses to possible operations.
```yaml
paths:
@@ -2319,7 +2319,7 @@ The following properties are taken from the JSON Schema definition but their def
- format - See [Data Type Formats](#dataTypeFormat) for further details. While relying on JSON Schema's defined formats, the OAS offers a few additional predefined formats.
- default - The default value represents what would be assumed by the consumer of the input as the value of the schema if one is not provided. Unlike JSON Schema, the value MUST conform to the defined type for the Schema Object defined at the same level. For example, of `type` is `string`, then `default` can be `"foo"`` but cannot be `1`.
-Alternatively, any time a Scheme Object can be used, a [Reference Object](#referenceObject) can be used in its place. This allows referencing definitions in place of defining them inline.
+Alternatively, any time a Schema Object can be used, a [Reference Object](#referenceObject) can be used in its place. This allows referencing definitions in place of defining them inline.
Additional properties defined by the JSON Schema specification that are not mentioned here are strictly unsupported.

typo: scheme -> schema

typo: scheme -> schema