deploy: c7c84b81e3ec3d66f3a57a8d6ba3e58dd4c81ecc

1 files changed, 1 insertions, 1 deletions

diff --git a/develop/usage/configuration/config_documentation.html b/develop/usage/configuration/config_documentation.html

index 6b71c309ed..9f96da087b 100644
--- a/develop/usage/configuration/config_documentation.html
+++ b/develop/usage/configuration/config_documentation.html
@@ -1418,6 +1418,7 @@ limit only, as Synapse presumes ratelimiting by room will be done by the sending
 sender, meaning that a <code>rc_invite.per_user.burst_count</code> of 5 mandates that a single user
 cannot <em>receive</em> more than a burst of 5 invites at a time.</p>
 <p>In contrast, the <code>rc_invites.per_issuer</code> limit applies to the <em>issuer</em> of the invite, meaning that a <code>rc_invite.per_issuer.burst_count</code> of 5 mandates that single user cannot <em>send</em> more than a burst of 5 invites at a time.</p>
+<p><em>Changed in version 1.63:</em> added the <code>per_issuer</code> limit.</p>
 <p>Example configuration:</p>
 <pre><code class="language-yaml">rc_invites:
   per_room:
@@ -1430,7 +1431,6 @@ cannot <em>receive</em> more than a burst of 5 invites at a time.</p>
     per_second: 0.5
     burst_count: 5
 </code></pre>
-<p><em>Changed in version 1.63:</em> added the <code>per_issuer</code> limit.</p>
 <hr />
 <h3 id="rc_third_party_invite"><a class="header" href="#rc_third_party_invite"><code>rc_third_party_invite</code></a></h3>
 <p>This option ratelimits 3PID invites (i.e. invites sent to a third-party ID