1 files changed, 0 insertions, 25 deletions
diff --git a/latest/MSC1711_certificates_FAQ.html b/latest/MSC1711_certificates_FAQ.html
index 630a64d64c..9fa9c6a620 100644
--- a/latest/MSC1711_certificates_FAQ.html
+++ b/latest/MSC1711_certificates_FAQ.html
@@ -218,31 +218,6 @@ timeline and some frequently asked questions are also given below.</p>
 <p>For more details and context on the release of the r0.1 Server/Server API and
 imminent Matrix 1.0 release, you can also see our
 <a href="https://matrix.org/blog/2019/02/04/matrix-at-fosdem-2019/">main talk from FOSDEM 2019</a>.</p>
-<h2 id="contents"><a class="header" href="#contents">Contents</a></h2>
-<ul>
-<li>Timeline</li>
-<li>Configuring certificates for compatibility with Synapse 1.0</li>
-<li>FAQ
-<ul>
-<li>Synapse 0.99.0 has just been released, what do I need to do right now?</li>
-<li>How do I upgrade?</li>
-<li>What will happen if I do not set up a valid federation certificate
-immediately?</li>
-<li>What will happen if I do nothing at all?</li>
-<li>When do I need a SRV record or .well-known URI?</li>
-<li>Can I still use an SRV record?</li>
-<li>I have created a .well-known URI. Do I still need an SRV record?</li>
-<li>It used to work just fine, why are you breaking everything?</li>
-<li>Can I manage my own certificates rather than having Synapse renew
-certificates itself?</li>
-<li>Do you still recommend against using a reverse proxy on the federation port?</li>
-<li>Do I still need to give my TLS certificates to Synapse if I am using a
-reverse proxy?</li>
-<li>Do I need the same certificate for the client and federation port?</li>
-<li>How do I tell Synapse to reload my keys/certificates after I replace them?</li>
-</ul>
-</li>
-</ul>
 <h2 id="timeline"><a class="header" href="#timeline">Timeline</a></h2>
 <p><strong>5th Feb 2019  - Synapse 0.99.0 is released.</strong></p>
 <p>All server admins are encouraged to upgrade.</p>