Replace details of multipart/form-data format with referce to RFC 7578

Author: Mike Kistler

versions/3.1.0.md

@@ -1533,7 +1533,7 @@ When passing complex objects in the `application/x-www-form-urlencoded` content
 
 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 supports complex structures as well as supporting mechanisms for multiple file uploads.
 
-In a `multipart/form-data` request body, each property, or each element of an array property, takes a section in the payload with an internal header. For example, for the header `Content-Disposition: form-data; name="submit-name"`, the name of the property is `submit-name`. This type of form property is more commonly used for file transfers. The serialization strategy for each property of a `multipart/form-data` request body can be specified in an associated [`Encoding Object`](#encodingObject).
+In a `multipart/form-data` request body, each property, or each element of an array property, takes a section in the payload with an internal header as defined by [RFC 7578](https://tools.ietf.org/html/rfc7578). The serialization strategy for each property of a `multipart/form-data` request body can be specified in an associated [`Encoding Object`](#encodingObject).
 
 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`: