Skip to content

Commit 8066c6c

Browse files
authored
Merge pull request #48 from ProgVal/message-format-content
Fix description of encrypted 'content' in the message format
2 parents e1fd9da + c368720 commit 8066c6c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

index.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -815,7 +815,7 @@ <h3 id="message-format">Message format</h3>
815815
</tr>
816816
<tr>
817817
<td>content</td>
818-
<td>If the message is not encrypted, This is a dictionary containing free-form data for applications to interpret, plus a mandatory <em>type</em> field. The <em>type</em> field allows applications to filter out message types they don’t understand and must be a UTF-16 string between 3 and 52 code units long (inclusive). If this is a base64 encoded string, followed by a suffix of <code>.box</code></td>
818+
<td>If the message is not encrypted, This is a dictionary containing free-form data for applications to interpret, plus a mandatory <em>type</em> field. The <em>type</em> field allows applications to filter out message types they don’t understand and must be a UTF-16 string between 3 and 52 code units long (inclusive). If the message is encrypted, then this is a base64 encoded string, followed by a suffix of <code>.box</code>; we will describe private messages later in this document.</td>
819819
</tr>
820820
</table>
821821
<aside style="align-self: start; position: relative; top: 19px;">

0 commit comments

Comments
 (0)