From 8405123978f08a089d388c47841c9bea8dec5a51 Mon Sep 17 00:00:00 2001
From: Dave Cridland <dave@forwardhealth.co>
Date: Tue, 21 Jan 2020 13:16:14 +0000
Subject: [PATCH] Fix XEP-0068 reference

---
 inbox/fulltext.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/inbox/fulltext.xml b/inbox/fulltext.xml
index bd984698..6149540d 100644
--- a/inbox/fulltext.xml
+++ b/inbox/fulltext.xml
@@ -51,7 +51,7 @@
 
   <section1 topic="Protocol Elements">
     <section2 topic="Querying">
-      <p>A text input field of <tt>{&ns;}fulltext</tt> is hereby defined for the 'urn:xmpp:mam:2' FORM_TYPE, as conforming to the syntax defined in &xep-0068;</p>
+      <p>A text input field of <tt>{&ns;}fulltext</tt> is hereby defined for the 'urn:xmpp:mam:2' FORM_TYPE, as conforming to the syntax defined in &xep0068;</p>
     </section2>
     <section2 topic="Results">
       <p>The precise matching of the supplied text string is left implementation-defined. Servers MAY use any full-text search engine. While this might mean that certain characters are deemed "special", clients are RECOMMENDED not to attempt any support for these, as they are unlikely to be portable between implementations. A conformant implementation of this protocol could be made, therefore, by accepting any string in the text field and returning nothing (or everything). Any server developer implementing this protocol in such a way MUST buy beers for everyone.</p>