Updated Fetching pages with WebDriver (markdown)

Fetching-pages-with-WebDriver.md

@@ -2,7 +2,7 @@ Javascript support / Fetching via WebDriver
 
 The backend can be configured to fetch pages via Chrome using the built in [WebDriver](https://www.selenium.dev/documentation/webdriver/) network interface, this is mainly used where the pages you are watching are using Javascript to render the page content (the basic fetcher does not execute any JS!), The easiest way is to enable it is to uncomment the following in your local [docker-compose.yml](https://github.com/dgtlmoon/changedetection.io/blob/master/docker-compose.yml) and restart your docker-compose. 
 
-## Linux / RaspberryPi / Ubuntu / etc
+# Linux / RaspberryPi / Ubuntu / etc
 
 **Note:** RaspberryPi needs a different selenium/webdriver runner, please edit your `docker-compose.yml` and use the recommended RaspberryPi image [more information here](https://github.com/dgtlmoon/changedetection.io/blob/271181968f4a303041164b719d3affbe2d1a5181/docker-compose.yml#L47)
 
@@ -48,7 +48,7 @@ Known to work with RaspberryPi-4 Use the `seleniarm/standalone-chromium:4.0.0-20
 
 - It's good to set the ENV var `FETCH_WORKERS` to a low value like 2 or 3, because maybe having 10 sessions of chrome open might be a bit too heavy on your rPi
 
-## Microsoft Windows - Running ChromeDriver natively (without Docker)
+# Microsoft Windows - Running ChromeDriver natively (without Docker)
 
 You need to install WebDriver/ChromeDriver for Chrome, this will "listen" for instructions from your changedetection.py and drive the browser to fetch the results.
 
@@ -69,7 +69,7 @@ Tested with Chrome version 99.0
 
 
 
-## There's a few things left todo
+# There's a few things left todo
 
 * Make tests use the full docker stack with the chromedriver + relevant settings
 * Lower the number of workers (make it configurable per backend?) 10 is too many (is it?), but this is totally fine for requests/plaintext