Browse Source

XEP-0385: Fix typos

s/exiting/existing/
s/contant/content/
s/availablity/availability/
LNJ 11 months ago
parent
commit
16623200cb
1 changed files with 3 additions and 3 deletions
  1. 3
    3
      xep-0385.xml

+ 3
- 3
xep-0385.xml View File

@@ -121,7 +121,7 @@ TODO:
121 121
     <li>Can be improved by server components for taking load of clients</li>
122 122
     <li>Media sharing should work and enable a good UX in multi-user chats like &xep0045; and &xep0369;</li>
123 123
     <li>Media sharing should work great together with conversation synchronization protocols like &xep0280; and &xep0313;</li>
124
-    <li>Reuse exiting protocols for the actual transport of the data, i.e. &xep0096;, &xep0234; or &xep0363;</li>
124
+    <li>Reuse existing protocols for the actual transport of the data, i.e. &xep0096;, &xep0234; or &xep0363;</li>
125 125
     <li>Guarantee file integrity</li>
126 126
     <li>Enable aggresive caching</li>
127 127
     <li>Provide users with metadata, e.g. file size, file type or thumbnail, to help them decide whether or not they want to load the media file</li>
@@ -164,7 +164,7 @@ TODO:
164 164
     <p>A client MAY retrieve the file from other sources than these mentioned in the sources element. This may be via &xep0234; from the senders' other resources or from a
165 165
       media caching service located at the local service. The standardization of such cache is out of scope for this document.</p>
166 166
     <p>Regardless of the transport method used to obtain the file, the received content MUST be verified against one of the hashes.
167
-      If the verification fails, the retrieved contant MUST be discarded and retrieval using a different source can be attempted.</p>
167
+      If the verification fails, the retrieved content MUST be discarded and retrieval using a different source can be attempted.</p>
168 168
   </section2>
169 169
 </section1>
170 170
 <section1 topic='Business Rules' anchor='rules'>
@@ -233,7 +233,7 @@ TODO:
233 233
   </section2>
234 234
   <section2 topic='MUC and MIX related rules'>
235 235
     <p>In cases where media is shared in a &xep0045; or &xep0369; room the sender has to expect that a large number of clients may retrieve the shared media automatically. Ideally multiple sources, including HTTP or other high availability sources, are provided in the &lt;sources&gt; tag of the &lt;media-sharing&gt; tag in case the media is shared in a MUC/MIX room.</p>
236
-    <p class='box'>TODO: Describe protocol for MIX members to advertise media availablilty to peers in a dedicated MIX channel PubSub node. Maybe as a dedicated XEP.</p>
236
+    <p class='box'>TODO: Describe protocol for MIX members to advertise media availabililty to peers in a dedicated MIX channel PubSub node. Maybe as a dedicated XEP.</p>
237 237
   </section2>
238 238
   <section2 topic='MAM and Carbons related rules'>
239 239
     <p>For the media sharing described in this XEP to work, it is REQUIRED for MAM to store the whole stanza instead of only the body content. If the MAM component of the user's server strips away the &lt;media-sharing&gt; tag, any shared media will be missing in archived messages.</p>

Loading…
Cancel
Save