anchor.diff:  
   * `getDockerRecordingPath()`: Get path of the session recording.
   * `getDockerNoVncUrl()`: Ger URL of the remote desktop noVNC session.
  -* `getDockerSeleniumServerUrl()`: Get URL of the underlying Selenium Server (inside the container) that allows controlling the remote (dockerized) browser.
  +* `getDockerSeleniumServerUrl()`: Get the URL of the underlying Selenium Server (inside the container) that allows controlling the remote (dockerized) browser.
   * `getDockerService()`: It allows access to the Docker service and client (based on https://github.com/docker-java/docker-java[docker-java]) to make custom operations with Docker containers (e.g., run commands in the browser container, see example https://github.com/bonigarcia/webdrivermanager/blob/master/src/test/java/io/github/bonigarcia/wdm/test/docker/DockerExecCommandInContainerTest.java[here]).
   * `getDockerBrowserContainerId()`: Get browser container id (required for advance operation using the Docker client)
   * `getWebDriver()`: Get the previously created `WebDriver` object (the same as the returned by the method `create()`.
  
positive.code: image::wdm-vnc.png[scaledwidth=100%]
  
  ==== Recordings
  The following related feature is the recording of the remote session of a dockerized browser. To enable it, we need to invoke the method `enableRecording()` in WebDriverManager. Internally, WebDriverManager starts another Docker container using https://ffmpeg.org/[FFmpeg] to record the browser session. At the end of the test, we can find the recording in MP4 (by default, with a filename composed by the browser name followed by the symbol `_` and the system timestamp, plus another `_` and the session id) located in the project root folder (you can change this behavior using <<advanced-configuration, configuration capabilities>>. The following test shows an example of this feature.
  
  [source,java]
  ----
  
negative.code: 
  [discrete]
  ==== Option 2: Browsers in Docker
  WebDriverManager CLI can execute browsers in Docker containers and interact with them using noVNC. This feature can be interesting for _exploratory testing_ for web applications using different types and versions of web browsers. To use this option, the arguments we need to use are the following (supposing we want to use Chrome):
  
  * Fat-JAR:
  
  