chore: add toc

Author: achingbrain

ROADMAP.md

@@ -1,13 +1,36 @@
 
-# js-libp2p roadmap Q4’22/Q1’23
+# js-libp2p roadmap Q4’22/Q1’23  <!-- omit in toc -->
+
 ```
 Date: 2022-10-07
 Status: In Progress
 Notes: This document is still in review will may be heavily modified based on stakeholder feedback. Please add any feedback or questions in:
 https://github.com/libp2p/js-libp2p/issues/1438
 ```
 
+## Table of Contents <!-- omit in toc -->
+
+- [About the Roadmap](#about-the-roadmap)
+	- [Sections](#sections)
+	- [Done criteria](#done-criteria)
+- [🛣️ Milestones](#️-milestones)
+	- [2022](#2022)
+		- [Early Q4 (October)](#early-q4-october)
+		- [Mid Q4 (November)](#mid-q4-november)
+		- [End of Q4 (December)](#end-of-q4-december)
+	- [2023](#2023)
+		- [Early/Mid Q1](#earlymid-q1)
+		- [End of Q1 (March)](#end-of-q1-march)
+		- [Early Q2 (April)](#early-q2-april)
+		- [Up Next](#up-next)
+- [Roadmap Appendix](#roadmap-appendix)
+	- [A. 📺 Universal Browser Connectivity](#a--universal-browser-connectivity)
+	- [B. 🥊 Decentralized Hole Punching](#b--decentralized-hole-punching)
+	- [C. 🧪 Future-proof Testing](#c--future-proof-testing)
+	- [Libp2p Project Roadmap](#libp2p-project-roadmap)
+
 ## About the Roadmap
+
 ### Sections
 This document consists of two sections: [Milestones](#Milestones) and the [Roadmap Appendix](#Roadmap-Appendix)
 
@@ -47,7 +70,7 @@ Others supporting projects (like testing or benchmarking) will have different cr
 
 #### Early/Mid Q1
 - C.2 🧪 Future-proof Testing - **Test DHT Server Mode at scale**
-- 
+-
 #### End of Q1 (March)
 - B.3 🥊 Decentralized Hole Punching - **Add QUIC Transport**
 
@@ -58,8 +81,8 @@ Others supporting projects (like testing or benchmarking) will have different cr
 #### Up Next
 - A.3 📺 Universal Browser Connectivity - **WebRTC for Browser to Browser**
 
-# Roadmap Appendix
-## A. 📺 Universal Browser Connectivity
+## Roadmap Appendix
+### A. 📺 Universal Browser Connectivity
 <!--- TODO: Link to GitHub Epic -->
 
 **Why**: A huge part of “the Web” is happening inside the browser. As a universal p2p networking stack, libp2p needs to be able to offer solutions for browser users.
@@ -70,7 +93,7 @@ Others supporting projects (like testing or benchmarking) will have different cr
 2. [WebRTC for Browser to Server](https://github.com/little-bear-labs/js-libp2p-webrtc/pull/4): This will cover the browsers that don't support WebTransport (most notable is iOS Safari). This is getting close to finalized.
 3. WebRTC for Browser to Browser: Even though this use case is made possible by [webrtc-star](https://github.com/libp2p/js-libp2p-webrtc-star) and [webrtc-direct](https://github.com/libp2p/js-libp2p-webrtc-direct) currently, they are a less than ideal solutions. Both libraries have shortcomings, aren't implemented in other languages, and don't employ newer libp2p advancements such as Circuit Relay v2, DCUtR, and authentication via Noise. Therefore, we want to support WebRTC Browser to Browser as a first class transport in js-libp2p and deprecate the previous libraries. This is beginning to be [specified here](https://github.com/libp2p/specs/pull/412).
 
-## B. 🥊 Decentralized Hole Punching
+### B. 🥊 Decentralized Hole Punching
 <!--- TODO: Link to GitHub Epic -->
 **Why**:  P2P networks can have a combination of both public and private nodes. While private nodes can dial nodes on the public Internet, they are unreachable from the outside as they are behind a NAT or a firewall. We need a mechanism to dial them. A [previous DHT crawl found that almost 63%](https://github.com/libp2p/specs/blob/master/ROADMAP.md#-hole-punching-on-tcp-and-quic) of the network was undialable.  This project aims to implement Decentralized Hole Punching in js-libp2p and bring it to parity with the Go and Rust implementations.
 
@@ -81,13 +104,13 @@ Others supporting projects (like testing or benchmarking) will have different cr
 4. Hole Punching - Use [DCUtR](https://github.com/libp2p/specs/blob/master/relay/DCUtR.md) to synchronize hole punching
 
 
-## C. 🧪 Future-proof Testing
+### C. 🧪 Future-proof Testing
 <!--- TODO: Link to GitHub Epic -->
 **Why**:  JS support doesn't exist in Testground yet. In addition to the work to get generic JS test runners, we need support in Testground.
 
 **Goal**:
 1. [Browser Environment Tests](https://github.com/testground/testground/issues/1386): Add support for testing browser features within a browser environment.
 2. Test DHT Server Mode at scale: Requires adding support for js-libp2p in Testground. Server mode is implemented but we need a way to ensure it works and to do that we need a very large network testbed (>20 node at least; ideally 100/1000+.)
 
-## Libp2p Project Roadmap
+### Libp2p Project Roadmap
 Roadmap items in this document were sourced from our the overarching libp2p project roadmap: https://github.com/libp2p/specs/blob/master/ROADMAP.md