From ec0e814de01c5e4bda9ceafc5aa3acb14fb096de Mon Sep 17 00:00:00 2001
From: Vanaryon <vanaryon@vanaryon.eu>
Date: Sun, 24 Apr 2011 16:03:08 +0200
Subject: [PATCH] Changed XEP-0277 0.2.1 version.

---
 xep-0277.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xep-0277.xml b/xep-0277.xml
index 194fd831..a69ca851 100644
--- a/xep-0277.xml
+++ b/xep-0277.xml
@@ -82,7 +82,7 @@ xmpp:romeo@montague.lit?;node=urn%3Axmpp%3Amicroblog%3A0
   </section2>
   <section2 topic='Publishing a Post' anchor='publish'>
     <p>Romeo can publish a post via any interface provided by his service, such as a website, the Atom Publishing Protocol (see &rfc5023;), SMS, an IM bot, or XMPP pubsub. Here we assume that the post is provided via XMPP pubsub.</p>
-    <p>The post content itself can be either text ("content" element "type" attribute with "text" value) or XHTML ("content" element "type" attribute with "xhtml" value). If Romeo publishes XHTML content, the post's "body" element MUST be plain text encoded. For XHTML publishing, see &xep0060;.</p>
+    <p>The post content itself can be either text ("content" element "type" attribute with "text" value) or XHTML ("content" element "type" attribute with "xhtml" value). If Romeo publishes XHTML content, his client MUST publish two "content" elements: a text one, and a XHTML one. For XHTML publishing, see &xep0060;.</p>
     <p>Note: Publishing via HTTP, AtomPub, SMS, or IM bot is simpler for the client (e.g., because the client does not need to generate an Item ID).</p>
     <example caption="Publishing a post"><![CDATA[
 <iq from='romeo@montague.lit/pda'