Split Implementations into Servers and Clients

Signed-off-by: Andreas Brönnimann <foss@exul.org>

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

@@ -19,7 +19,9 @@ Categories
 
 [Standard](#standard)
 
-[Implementations](#implementations)
+[Servers](#servers)
+
+[Clients](#clients)
 
 |
 
@@ -502,7 +504,7 @@ HTTP is indeed not the most efficient transport, but it is ubiquitous, very well
 
 It has thus been chosen as the mandatory baseline of the exchange, but it is still entirely possible to use more fancy protocols for communication between clients and server (see for example this [websocket transport draft](https://github.com/matrix-org/matrix-doc/blob/master/drafts/websockets.rst)), and it's also possible in the future that negotiation of more efficient protocols will be added for the federation between servers, with HTTP+JSON remaining as the compability baseline.
 
-### Implementations
+### Servers
 
 ##### What is Synapse?
 
@@ -553,6 +555,8 @@ This is because both provide a mature and well known event-driven async IO frame
 
 Synapse is *very* database dependent (as of Oct 2015; this is improving in the near future however), and we like having the flexibility to sculpt our own queries.
 
+### Clients
+
 ##### Where can I find a mobile app?
 
 The "Matrix Console" reference apps (ugly, geeky and powerful - intended for early adopter powerusers) can be downloaded from the [Google Play store](https://play.google.com/store/apps/details?id=org.matrix.androidsdk.alpha)