Fix links and better formatting

docs/sessions/3pid.md

@@ -5,10 +5,14 @@
   - [3PID scope](#3pid-scope)
   - [Session scope](#session-scope)
 - [Notifications](#notifications)
+  - [Email](#email)
 - [Usage](#usage)
   - [Configuration](#configuration)
   - [Scenarios](#scenarios)
-  - [Recommendations](#recommendations)
+    - [Default](#default)
+    - [Local sessions only](#local-sessions-only)
+    - [Remote sessions only](#remote-sessions-only)
+    - [Sessions disabled](#sessions-disabled)
 
 ## Overview
 When adding an email, a phone number or any other kind of 3PID (Third-Party Identifier), 
@@ -91,7 +95,7 @@ mxisd use two components for this:
 
 Built-in generators and connectors for supported 3PID types:
 
-**Email**  
+### Email
 Generators:
 - Template
 
@@ -216,7 +220,7 @@ Nonetheless, because mxisd also aims at offering support for tight control over
 such 3PID bindings available for search and invite queries on the local Homeserver by using the `SQL` backend and
 configuring it to use the synapse database. Support for `SQLite` and `PostgreSQL` is available.
 
-See the *Local only* use case for more information on how to configure.
+See the [Local sessions only](#local-sessions-only) use case for more information on how to configure.
 
 #### Default
 By default, mxisd allows the following:
@@ -226,7 +230,7 @@ By default, mxisd allows the following:
 | **Local 3PID** | Yes | Yes, offered |
 | **Remote 3PID** | No, Remote forced | Yes |
 
-This is usually what people typically expect and will feel natural to users and does not involve further integration.
+This is usually what people expect and will feel natural to users and does not involve further integration.
 
 This allows to stay in control for e-mail addresses which domain matches your Matrix environment, still making them
 discoverable with federation but not recorded in a 3rd party Identity server which is not under your control.