[muji/master] capitalisation/whitespace

[Dafydd Harries]

---
 xep/mingle.xml |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/xep/mingle.xml b/xep/mingle.xml
index 2767dc0..590451f 100644
--- a/xep/mingle.xml
+++ b/xep/mingle.xml
@@ -61,8 +61,8 @@ streams.
 
 <section1 topic='Starting a conference' anchor='starting'>
   <!-- TODO better conflict handling -->
-  Assuming there is no existing mingle conference in the <cite>XEP-0045</cite> 
-  room a new conference can be started by a user putting a mingle stanza with
+  Assuming there is no existing Mingle conference in the <cite>XEP-0045</cite>
+  room a new conference can be started by a user putting a Mingle stanza with
   the proposed contents in its presence. As shown in the example below:
 
   <code><![CDATA[
@@ -102,18 +102,18 @@ streams.
 
   Afterwords a normal jingle session MUST initiated to all participants
   previously in the conference. The name of a content in the jingle session
-  refers to the content with the same name in the mingle stanza presence. The
-  jingle content MUST have exactly the same description as the mingle content
+  refers to the content with the same name in the Mingle stanza presence. The
+  jingle content MUST have exactly the same description as the Mingle content
   it refers to.
 
-  To leave a conference first the mingle stanza presence MUST be removed from
+  To leave a conference first the Mingle stanza presence MUST be removed from
   the participants presence and afterwards it SHOULD terminate all jingle
   sessions.
 </section1>
 
 <section1 topic='TODO' anchor='TODO'>
 <ul>
- <li> There is a slight race when two participants try to start a new mingle
+ <li> There is a slight race when two participants try to start a new Mingle
       conference at the same time. This can be solves by making the initial
       conference announceemnt two stage and relying on the fact that messages
       are ordered to be the arbiter. (Note actually find out if presence is
-- 
1.5.6.5