edit 'Considerations for file uploads' and 'Support for x-www-form-urlencoded request bodies'
MODIFY
versions/3.0.md
versions/3.0.md
@@ -1345,7 +1345,7 @@ application/json:
##### Considerations for file uploads
-In contrast with the 2.0 specification, describing `file` input/output content in OpenAPI is
+In contrast with the 2.0 specification, `file` input/output content in OpenAPI is
described with the same semantics as any other schema type. Specifically:
```yaml
@@ -1360,9 +1360,9 @@ schema:
format: binary
```
-Note that the above examples apply to either input payloads (i.e. file uploads) or response payloads.
+These examples apply to either input payloads of file uploads or response payloads.
-A `requestBody` example for submitting a file in a `POST` operation therefore may look like the following:
+A `requestBody` for submitting a file in a `POST` operation, however, may look like the following example:
```yaml
requestBody:
@@ -1409,7 +1409,7 @@ requestBody:
properties: {}
```
-Note that in the above 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 as well.
+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.
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`.

edit 'Considerations for file uploads' and 'Support for x-www-form-urlencoded request bodies'