diff --git a/versions/3.1.1.md b/versions/3.1.1.md
index b76582a24a..d32588efb7 100644
--- a/versions/3.1.1.md
+++ b/versions/3.1.1.md
@@ -267,8 +267,8 @@ The following table shows how to migrate from OAS 3.0 binary data descriptions,
| OAS < 3.1 | OAS 3.1 | Comments |
| ------------------------------------ | -------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
-| `type: string`
`format: binary` | `contentMediaType: image/png` | if redundant, can be omitted, often resulting in an empty [Schema Object](#schema-object) |
-| `type: string`
`format: byte` | `type: string`
`contentMediaType: image/png`
`contentEncoding: base64` | note that `base64url` can be used to avoid re-encoding the base64 string to be URL-safe |
+| type: string
format: binary
| contentMediaType: image/png
| if redundant, can be omitted, often resulting in an empty [Schema Object](#schema-object) |
+| type: string
format: byte
| type: string
contentMediaType: image/png
contentEncoding: base64
| note that `base64url` can be used to avoid re-encoding the base64 string to be URL-safe |
### Rich Text Formatting
@@ -1591,6 +1591,12 @@ content:
application/octet-stream: {}
```
+```yaml
+# arbitrary JSON without constraints beyond being syntactically valid:
+content:
+ application/json: {}
+```
+
These examples apply to either input payloads of file uploads or response payloads.
A `requestBody` for submitting a file in a `POST` operation may look like the following example: