typos and old references

xep-0283.xml

@@ -127,7 +127,7 @@
     <p>Because the original JID is no longer going to be used, the user SHOULD 
     unsubscribe from all the outbound subscriptions user@example.com had.
     These can be identified as those in the 'to' or 'ask' states as 
-    defined in the 'jabber:iq:roster' protocol in &rfc3921;.</p>
+    defined in the 'jabber:iq:roster' protocol in <cite>RFC 6121</cite>.</p>
 
     <p>To unsubscribe all outbound subscriptions for the original JID send an 
     unsubscribe &PRESENCE; stanza to all the old contacts with a &MOVED; 
@@ -157,7 +157,7 @@
     unsubscribe from all contacts the user@example.com had an inbound 
     subscription from. These can be identified as those in the 'from' 
     subscription state as defined in in the 'jabber:iq:roster' protocol 
-    in &rfc3921;.</p>
+    in <cite>RFC 6121</cite>.</p>
 
     <p>To unsubscribe all inbound subscriptions send an unsubscribed 
     &PRESENCE; stanza to all the old contacts with a &MOVED; element 
@@ -216,7 +216,7 @@
     
   <section2 topic='Contacts Offline at the Time the Rename Occurs' 
    anchor='offline'>
-    <p>&rfc6120; clarifies that an incoming subscribe &PRESENCE; stanza 
+    <p><cite>RFC 6120</cite> clarifies that an incoming subscribe &PRESENCE; stanza 
     MUST be preserved by the server and &PRESENCE; stanzas of type 
     unsubscribe and unsubscribed are not preserved on the server. 
     Therefore, for a contact who is offline, their servers MAY have 
@@ -290,7 +290,7 @@
     the user to subscribe to the new JID listed in the &MOVED; element.</p>
 
   <p>Because of the ability to spoof the &MOVED; element, the client SHOULD
-     NOT automatically subscribe to the &MOVED; element target</p>.
+     NOT automatically subscribe to the &MOVED; element target.</p>
   </section3>
 
   <section3 topic='Roster state and action table' anchor='actions'>