s/TestContainers/Testcontainers

Testcontainers is with a lower case c

docs/BROWSER.md

@@ -70,7 +70,7 @@ If this is the case you can specify the address to use using:
     `SELENIUM_PROXY_HOSTNAME=ip.address.of.host mvn install`
 **Important**: this could exposed the proxy wider beyond your machine and expose other internal services, so this should only be used on private or internal networks to prevent any information leak.
 The same issue will also impact any other containers started that the tests that the Browser (rather than Jenkins) needs to access.
-For TestContainers you can additionally set `TESTCONTAINERS_HOST_OVERRIDE=ip.address.of.host`
+For [Testcontainers](https://testcontainers.com/) you can additionally set `TESTCONTAINERS_HOST_OVERRIDE=ip.address.of.host`
 
 ## Avoid focus steal with Xvnc on Linux
 If you select a real GUI browser, such as Firefox,

docs/DOCKER.md

@@ -72,7 +72,7 @@ It's best explained with an example:
 
 If you are using a custom network for the container that executes the testing you may instruct the docker-fixtures to use the same one by setting the env variable `DOCKER_FIXTURES_NETWORK`to specify the network you want your fixtures to connect to. 
 
-# Using TestContainers with a remote webdriver
+# Using Testcontainers with a remote webdriver
 
 If you are using a containerized webdriver (or any other remote webdriver) then any containers launched will not be reachable from the remote web browser.
 This will be an issue for some tests that require the browser interact with the container (e.g. for authentication).