diff --git a/Fetching-pages-with-WebDriver.md b/Fetching-pages-with-WebDriver.md
index 31075b1..5750e94 100644
--- a/Fetching-pages-with-WebDriver.md
+++ b/Fetching-pages-with-WebDriver.md
@@ -1,3 +1,5 @@
+Many modern web pages use javascript to fill-in the content, they are more dynamic and sometimes need a real chrome browser for fetching the content, although many may work with our built in 'fetcher'
+
 The backend can be configured to fetch pages via Chrome (ChromeDriver) 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. 
 
 **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) - Use `seleniarm/standalone-chromium:4.0.0-20211213` instead of `selenium/standalone-chrome-debug:3.141.59`