Skip to content

Commit 5f97fc5

Browse files
committed
DB's changes
1 parent fada30b commit 5f97fc5

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

versions/3.0.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1362,7 +1362,7 @@ schema:
13621362

13631363
These examples apply to either input payloads of file uploads or response payloads.
13641364

1365-
A `requestBody` for submitting a file in a `POST` operation, however, may look like the following example:
1365+
A `requestBody` for submitting a file in a `POST` operation may look like the following example:
13661366

13671367
```yaml
13681368
requestBody:
@@ -1409,7 +1409,7 @@ requestBody:
14091409
properties: {}
14101410
```
14111411
1412-
In this example, the contents in the `requestBody` MUST be stringified per [RFC1866](https://tools.ietf.org/html/rfc1866/) when being passed to the server. In addition, the `address` field complex object will be stringified.
1412+
In this example, the contents in the `requestBody` MUST be stringified per [RFC1866](https://tools.ietf.org/html/rfc1866/) when passed to the server. In addition, the `address` field complex object will be stringified.
14131413

14141414
When passing complex objects in the `x-www-form-urlencoded` content type, the default serialization strategy of such properties is described in the `parameterContent` section as `form`.
14151415

0 commit comments

Comments
 (0)