Skip to content
This repository was archived by the owner on May 30, 2022. It is now read-only.

Commit 2a4cc4a

Browse files
committed
Fixed section names
1 parent 8d3dc3f commit 2a4cc4a

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

versions/3.0.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -674,7 +674,7 @@ This object can be extended with [Specification Extensions](#specificationExtens
674674
"200": {
675675
"description": "pet response",
676676
"content": {
677-
"*": {
677+
"*/*": {
678678
"schema": {
679679
"type": "array",
680680
"items": {
@@ -721,7 +721,7 @@ get:
721721
'200':
722722
description: pet response
723723
content:
724-
*:
724+
'*/*' :
725725
schema:
726726
type: array
727727
items:
@@ -1831,7 +1831,7 @@ X-Rate-Limit-Reset:
18311831

18321832
Allows sharing examples for operation requests and responses. This literal value can either be any JSON or YAML object, array or primitive value. To represent examples of media types that cannot naturally represented in the OpenAPI definition, a string value can be used to contain the example with escaping where necessary.
18331833

1834-
##### Example Example
1834+
##### Example Object Example
18351835

18361836
Example representation for application/json media type of a Pet data type:
18371837

@@ -1863,7 +1863,7 @@ Field Name | Type | Description
18631863
<a name="describedExampleSummary"></a>summary | `string` | Short description for the example.
18641864
<a name="describedExampleDescription"></a>description | `string` | Long description for the example.
18651865
<a name="describedExampleValue"></a>value | [Example Object](#exampleObject) | Embedded literal example. The `value` field and `valueUrl` field are mutually exclusive.
1866-
<a name="describedExampleValueUrl"></a>valueUrl | `string` | A Url that points to the literal example. This provides the ability to reference examples that cannot easily be included in JSON or YAML documents. The `value` field and `valueUrl` field are mutually exclusive.
1866+
<a name="describedExampleValueUrl"></a>valueUrl | `string` | A URL that points to the literal example. This provides the ability to reference examples that cannot easily be included in JSON or YAML documents. The `value` field and `valueUrl` field are mutually exclusive.
18671867

18681868
This object can be extended with [Specification Extensions](#specificationExtensions).
18691869

@@ -1872,7 +1872,7 @@ for the value that it is accompanying. Tooling implementations MAY choose to
18721872
validate compatibility automatically, and reject the example value(s) if they
18731873
are not compatible.
18741874

1875-
##### Example Described Example
1875+
##### Described Example Object Example
18761876

18771877
```yaml
18781878
# in a model
@@ -1906,7 +1906,8 @@ schemas:
19061906
textExample:
19071907
summary: This is a text example
19081908
valueUrl: 'http://foo.bar/examples/address-example.txt'
1909-
1909+
1910+
19101911
# in a parameter
19111912
parameters:
19121913
- name: 'zipCode'
@@ -2436,7 +2437,6 @@ name: pet
24362437
description: Pets operations
24372438
```
24382439

2439-
24402440
#### <a name="referenceObject"></a>Reference Object
24412441

24422442
A simple object to allow referencing other components in the specification, internally and externally.

0 commit comments

Comments
 (0)