Updated Services (markdown)

Services.md

@@ -156,7 +156,7 @@ folder without a `.txt` or `default.txt`, but with another file, then no Cookies
 >   Profile names are case-sensitive and unique per-service. They have no arbitrary character or length limit, but for
 >   convenience sake we don't recommend using any special characters as your terminal may get confused.
 
-### Cookie file format and Extensions
+## Cookie file format and Extensions
 
 Cookies must be in the standard Netscape cookies file format.  
 Recommended Cookie exporter extensions:
@@ -166,7 +166,7 @@ Recommended Cookie exporter extensions:
 
 Any other extension that exports to the standard Netscape format should theoretically work.
 
-### Sharing Services
+## Sharing Services
 
 Sending and receiving zipped Service folders is quite cumbersome. Let's explore alternative routes to collaborating on
 Service Code.
@@ -175,7 +175,7 @@ Service Code.
 > Please be careful with who you trust and what you run. The users you collaborate with on Service
 > code could update it with malicious code that you would run via unshackle on the next call.
 
-#### Forking
+## Forking
 
 If you are collaborating with a team on multiple services then forking the project is the best way to go.
 
@@ -207,7 +207,7 @@ If you are new to `git` then take a look at [GitHub Desktop](https://desktop.git
 > However, if the core project also has dependency changes your `uv.lock` changes will conflict and you
 > will need to learn how to do conflict resolution/rebasing. It is worth it though!
 
-#### Symlinking
+## Symlinking
 
 This is a great option for those who wish to do something like the forking method, but may not care what changes
 happened or when and just want changes synced across a team.