Skip to content

Commit 7065b9e

Browse files
committed
edit Tag Object Examples
1 parent e6ec613 commit 7065b9e

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

versions/3.0.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2340,15 +2340,15 @@ description: Pets operations
23402340

23412341
#### <a name="examplesObject"></a>Examples Object
23422342

2343-
Anywhere an `example` may be given, a JSON Reference MAY be used, with the
2343+
In an `example`, a JSON Reference MAY be used, with the
23442344
explicit restriction that examples having a JSON format with object named
2345-
`$ref` are not allowed. This does mean that `example`, structurally, can be
2345+
`$ref` are not allowed. Therefore, that `example`, structurally, can be
23462346
either a string primitive or an object, similar to `additionalProperties`.
23472347

23482348
In all cases, the payload is expected to be compatible with the type schema
2349-
for the value that it is accompanying. Tooling implementations MAY choose to
2349+
for the associated value. Tooling implementations MAY choose to
23502350
validate compatibility automatically, and reject the example value(s) if they
2351-
are not compatible.
2351+
are incompatible.
23522352

23532353
```yaml
23542354
# in a model

0 commit comments

Comments
 (0)