Merge pull request #3969 from ralfhandl/3.1.1/formatting

3.1.1 formatting improvements

Author: miqui

versions/3.1.1.md

@@ -287,8 +287,8 @@ Using a `contentEncoding` of `base64url` ensures that URL encoding (as required
 
 The `contentMediaType` keyword is redundant if the media type is already set:
 
-* as the key for a [`MediaType Object`](#mediaTypeObject)
-* in the `contentType` field of an [`Encoding Object`](#encodingObject)
+* as the key for a [MediaType Object](#mediaTypeObject)
+* in the `contentType` field of an [Encoding Object](#encodingObject)
 
 If the Schema Object will be processed by a non-OAS-aware JSON Schema implementation, it may be useful to include `contentMediaType` even if it is redundant.  However, if `contentMediaType` contradicts a relevant Media Type Object or Encoding Object, then `contentMediaType` SHALL be ignored.
 
@@ -321,7 +321,7 @@ Note that some URI fields are named `url` for historical reasons, but the descri
 
 Unless specified otherwise, all properties that are URIs MAY be relative references as defined by [RFC3986](https://tools.ietf.org/html/rfc3986#section-4.2).
 
-Relative references in [`Schema Objects`](#schemaObject), including any that appear as `$id` values, use the nearest parent `$id` as a Base URI, as described by [JSON Schema Specification Draft 2020-12](https://tools.ietf.org/html/draft-bhutton-json-schema-00#section-8.2).
+Relative references in [Schema Objects](#schemaObject), including any that appear as `$id` values, use the nearest parent `$id` as a Base URI, as described by [JSON Schema Specification Draft 2020-12](https://tools.ietf.org/html/draft-bhutton-json-schema-00#section-8.2).
 
 Relative URI references in other Objects, and in Schema Objects where no parent schema contains an `$id`, MUST be resolved using the referring document's base URI, which is determined in accordance with [RFC3986 §5.1.2 – 5.1.4](https://tools.ietf.org/html/rfc3986#section-5.1.2).
 In practice, this is usually the retrieval URI of the document, which MAY be determined based on either its current actual location or a user-supplied expected location.
@@ -333,15 +333,15 @@ If a URI contains a fragment identifier, then the fragment should be resolved pe
 API endpoints are by definition accessed as locations, and are described by this specification as ***URLs***.
 
 Unless specified otherwise, all properties that are URLs MAY be relative references as defined by [RFC3986](https://tools.ietf.org/html/rfc3986#section-4.2).
-Unless specified otherwise, relative references are resolved using the URLs defined in the [`Server Object`](#serverObject) as a Base URL. Note that these themselves MAY be relative to the referring document.
+Unless specified otherwise, relative references are resolved using the URLs defined in the [Server Object](#serverObject) as a Base URL. Note that these themselves MAY be relative to the referring document.
 
 Relative references in CommonMark hyperlinks are resolved in their rendered context, which might differ from the context of the API description.
 
 ### Schema
 
 This section describes the structure of the OpenAPI Description format.
 This text is the only normative description of the format.
-A JSON Schema is hosted on [spec.openapis.org](https://spec.openapis.org) for informational purposes.
+A JSON Schema is hosted on [`spec.openapis.org`](https://spec.openapis.org) for informational purposes.
 If the JSON Schema differs from this section, then this section MUST be considered authoritative.
 
 In the following description, if a field is not explicitly **REQUIRED** or described with a MUST or SHALL, it can be considered OPTIONAL.
@@ -2709,7 +2709,7 @@ Field Name | Type | Description
 
 This object cannot be extended with additional properties and any properties added SHALL be ignored.
 
-Note that this restriction on additional properties is a difference between Reference Objects and [`Schema Objects`](#schemaObject) that contain a `$ref` keyword.
+Note that this restriction on additional properties is a difference between Reference Objects and [Schema Objects](#schemaObject) that contain a `$ref` keyword.
 
 ##### Reference Object Example