From f1a628c6b0e0d47d14ca9a84037f7a0fa621389f Mon Sep 17 00:00:00 2001
From: Guus der Kinderen <guus.der.kinderen@gmail.com>
Date: Wed, 20 Dec 2023 19:51:55 +0100
Subject: [PATCH] PubSub Server Info: fixed typo

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

diff --git a/inbox/pubsub-server-info.xml b/inbox/pubsub-server-info.xml
index c3500a8d..f90eedd7 100644
--- a/inbox/pubsub-server-info.xml
+++ b/inbox/pubsub-server-info.xml
@@ -106,7 +106,7 @@
   <domain name='shakespeare.lit'/>
 </serverinfo>]]></example>
   <p>The optional 'federation' child element is used to denote remote XMPP domains with which the local domain is federating. Each of them are represented by an element named 'remote-domain'. The domain name of the peer in an optional attribute named 'name'. Optionally, each actual (e.g. TCP) connection from the local server to the peer is added as a 'connection' child-element to the 'remote-domain' element, that has an optional 'type' attribute, defining the directionality of the connection (one of 'incoming', 'outgoing' and 'bidi').</p>
-  <p>The name of a remote domain MUST only be included if the remote server advertises supporting for this XEP. This acts as an opt-in mechanism, to address the privacy concern defined in the <link url="#privacy">Privacy Considerations section</link> of this document.</p>
+  <p>The name of a remote domain MUST only be included if the remote server advertises support for this XEP. This acts as an opt-in mechanism, to address the privacy concern defined in the <link url="#privacy">Privacy Considerations section</link> of this document.</p>
   <example caption="Data Format with Federated Domains"><![CDATA[
 <serverinfo xmlns="urn:xmpp:serverinfo:0">
   <domain name="shakespeare.lit">