diff --git a/xep-0165.xml b/xep-0165.xml
index f9b61ff2..5cabaef7 100644
--- a/xep-0165.xml
+++ b/xep-0165.xml
@@ -137,11 +137,11 @@
   <section2 topic='Subscription Requests' anchor='rec-subscriptions'>
     <p>We have seen that, at a minimum, three names or address types are needed to provide a petname system for XMPP: a JID, a nickname, and a handle (preferably strengthened by inclusion of a fingerprint derived from a key). However, at present a subscription request contains only the JID of the sender:</p>
     <example caption='A Basic Subscription Request'><![CDATA[
-<presence from='stpeter@jabber.org to='MaineBoy@jabber.org' type='subscribe'/>
+<presence from='stpeter@jabber.org' to='MaineBoy@jabber.org' type='subscribe'/>
     ]]></example>
     <p>Naturally, based on the JID, it is possible to pull information about the sender from a persistent data store such as an LDAP database, &xep0054; node, or future profile system (see &xep0154;). However, to speed interactions, this document recommends that when a client sends a subscription request, it SHOULD include the preferred nickname of the sender (encapsulated via the format specified in <cite>XEP-0172</cite>) and the sender's key or keys.</p>
     <example caption='Subscription Request With Nickname and Key'><![CDATA[
-<presence from='stpeter@jabber.org to='MaineBoy@jabber.org' type='subscribe'>
+<presence from='stpeter@jabber.org' to='MaineBoy@jabber.org' type='subscribe'>
   <nick xmlns='http://jabber.org/protocol/nick'>psa</nick>
   <KeyInfo xmlns='http://www.w3.org/2000/09/xmldsig#'>
     <KeyName>stpeterRSAkey1</KeyName>