Skip to content
This repository was archived by the owner on Jul 1, 2021. It is now read-only.

Commit 2cda83a

Browse files
authored
Change only occurrence of -- to —
1 parent 150d27e commit 2cda83a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

versions/3.0.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1466,7 +1466,7 @@ When passing complex objects in the `x-www-form-urlencoded` content type, the de
14661466

14671467
It is common to use `multipart/form-data` as a `Content-Type` when transferring request bodies to operations. In contrast to 2.0, a `schema` is required to define the input parameters to the operation when using `multipart` content. This allows complex structures as well as supports mechanisms for multiple file uploads.
14681468

1469-
When passing in `multipart` types, boundaries MAY be used to separate sections of the content being transferred--thus, the following default `Content-Type`s are defined for `multipart/*`:
1469+
When passing in `multipart` types, boundaries MAY be used to separate sections of the content being transferredthus, the following default `Content-Type`s are defined for `multipart/*`:
14701470

14711471
* If the property is a primitive, or an array of primitive values, the default Content-Type is `text/plain`
14721472
* If the property is complex, or an array of complex values, the default Content-Type is `application/json`

0 commit comments

Comments
 (0)