moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-12-03 06:22:16 -05:00
Code Issues Releases Wiki Activity

XEP-0373: Fix typos

Browse Source
This commit is contained in:
Paul Schaub 2018-04-18 12:57:35 +02:00
parent 2b7da0bf24
commit bcc925a8e2
No known key found for this signature in database
GPG Key ID: 62BEE9264BF17311
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
xep-0373.xml
View File

@ -156,7 +156,7 @@
that is, it represents either a &signcrypt;, a &sign; or a &crypt;
extension element qualified by the 'urn:xmpp:openpgp:0'
namespace. Note that OpenPGP's ASCII Armor is not used, instead
the XMPP client MUST encode the raw bytes of OpenPGP message using
the XMPP client MUST encode the raw bytes of the OpenPGP message using
Base64.</p>
<p>In case of a &signcrypt; element, the OpenPGP message embedded
@ -213,21 +213,21 @@
<td>&signcrypt;</td>
<td>MUST have at least one</td>
<td>MUST have exactly one</td>
<td>SHOULD have exaclty one</td>
<td>SHOULD have exactly one</td>
<td>MUST have exactly one</td>
</tr>
<tr>
<td>&sign;</td>
<td>MAY NOT contain one</td>
<td>MUST have exaclty one</td>
<td>MUST have exactly one</td>
<td>NOT REQUIRED</td>
<td>MUST have exactly one</td>
</tr>
<tr>
<td>&crypt;</td>
<td>MUST have at least one</td>
<td>MUST have exaclty one</td>
<td>SHOULD have exaclty one</td>
<td>MUST have exactly one</td>
<td>SHOULD have exactly one</td>
<td>MUST have exactly one</td>
</tr>
</table>
@ -304,7 +304,7 @@
send a PubSub &IQ; request to the entity's bare JID of which it
wants to know the public key.</p>
<example caption='Requesting a OpenPGP public key from an XMPP entity.'><![CDATA[
<example caption='Requesting an OpenPGP public key from an XMPP entity.'><![CDATA[
<iq from='romeo@example.org/orchard'
to='juliet@example.org'
type='get'
@ -333,7 +333,7 @@
</iq>]]></example>
<p>Note that the result may contain multiple pubkey elements. Only
the public keys found in the most recent MUST be used. Requesters
the public keys found in the most recent item MUST be used. Requesters
may want to limit the results to the most recent item using the
'max_items' attribute set to '1'. Clients could alternatively use
&xep0059; as an alternative to 'max_items' but accoding to