Merge pull request #1173 from krishahn/considerations-for-file-uploads-and-support-for-x-www-form-urlencoded-request-bodies

edit 'Considerations for file uploads' and 'Support for x-www-form-ur…

Author: Ron

versions/3.0.md

@@ -1343,9 +1343,9 @@ application/json:
       $ref: "#/components/examples/frog-example"
 ```
 
-##### Considerations for file uploads
+##### 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 may look like the following example:
 
 ```yaml
 requestBody:
@@ -1388,7 +1388,7 @@ requestBody:
         format: binary
 ```
 
-##### Support for x-www-form-urlencoded request bodies
+##### Support for x-www-form-urlencoded Request Bodies
 
 To submit content using form url encoding via [RFC1866](https://tools.ietf.org/html/rfc1866), the following
 definition may be used:
@@ -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 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`.