FAQ: remove 'Why don't you use websockets' todo

... since we already have an answer that answers it

supporting-docs/guides/2015-08-19-faq.md

@@ -520,7 +520,7 @@ Privacy of metadata is not currently protected from server administrators - a ma
 
 Rather than relying on Certificate Authorities (CAs) as in traditional SSL, a [Perspectives](https://perspectives-project.org/)-style system uses a more decentralized model for verifying keys.  Perspectives uses notary servers to verify that the same key is seen across the network, making a man-in-the-middle attack much harder since an attacker must insert itself into multiple places.  For federation in Matrix, each Home Server acts as a notary.  When one Home Server connects to another Home Server that uses a key that it doesn't recognize, it contacts other Home Servers to ensure that they all see the same key from that Home Server.
 
-##### Why HTTP? Doesn't HTTP suck?
+##### Why HTTP? Doesn't HTTP suck? Why don't you use websockets/CoAP/HTTP2/etc?
 
 HTTP is indeed not the most efficient transport, but it is ubiquitous, very well understood and has numerous implementations on almost every platform and language. It also has a simple upgrade path to HTTP/2, which is relatively bandwidth and round-trip efficient.
 
@@ -666,7 +666,6 @@ This FAQ is a constant work in progress - patches and pull requests are *very* w
  * What's on the roadmap?
  * How can I use Matrix to talk on Freenode or other IRC networks?
  * Where can I learn more about Matrix?  (link to PDFs of other presentations etc)
- * Why don't you use websockets?
  * Why is synapse so resource intensive immediately after federating for the first time?
  * \[your question goes here...\]