diff --git a/xep-0253.xml b/xep-0253.xml
index c100d3ea..c1d1f904 100644
--- a/xep-0253.xml
+++ b/xep-0253.xml
@@ -24,6 +24,12 @@
Specifed protocol flow for the chained subscription. At this point, the service itself will subscribe to the remote node. Now subscribers who are local to the consumer.tld XMPP service can subscribe directly to weatherbot@consumer.tld/Chicagoland instead of the remote pubsub node at notify.weather.tld. We therefore refer to weatherbot@consumer.tld/Chicagoland as a "chaining node" and the remote node as a "chained node". When a chained pubsub node delivers notifications to its subscribers, it SHOULD include an &xep0033; header of "ofrom" (note: this header is not yet defined in XEP-0033).
http://jabber.org/protocol/pubsub#chaining
- XEP-xxxx
+ XEP-0253
Forms used for chaining of pubsub nodes.