anchor.diff:  }
   ----
   
  -Selenium-Jupiter provides a lot of extra features, such as seamless integration with Docker, test templates (for cross-browser testing), conditional test execution (depending on the availability of browsers), conditional screenshots and recordings (when tests fail), and more. For more details, read the https://bonigarcia.org/selenium-jupiter/[documentation].
  +Selenium-Jupiter provides more different features, such as seamless integration with Docker, test templates (for cross-browser testing), conditional test execution (depending on the availability of browsers), conditional screenshots, and recordings (when tests fail), and more. For further details, read the https://bonigarcia.org/selenium-jupiter/[Selenium-Jupiter documentation].
   
   == Examples
  -To do.
  +The following repositories contain different examples using WebDriverManager:
  +
  +* https://github.com/bonigarcia/webdrivermanager-basic[WebDriverManager Basic]: A simple project using JUnit 5, Selenium WebDriver, and WebDriverManager.
  +* https://github.com/bonigarcia/webdrivermanager-examples[WebDriverManager Examples]: Different examples with JUnit 5, Selenium WebDriver, and WebDriverManager.
  +* https://github.com/bonigarcia/webdrivermanager-spring-boot[WebDriverManager Spring-Boot]: Another simple project using Spring-Boot, JUnit 5, Selenium WebDriver, and WebDriverManager.
  +* https://github.com/bonigarcia/wdm-agent-example[WebDriverManager Agent Example]: Maven project using WebDriverManager as Agent.
  +* https://github.com/bonigarcia/selenium-jupiter-examples[Selenium-Jupiter Examples]: Examples using JUnit 5 and <<selenium-jupiter,Selenium-Jupiter>>.
   
   == Configuration
   To do.
   
   == Known issues
  -To do
  -
   [discrete]
   ==== HTTP response code 403
  -To do.
  +Some of the drivers (e.g., geckodriver or operadriver) are hosted on GitHub. When external clients (like WebDriverManager makes) many consecutive requests to GitHub, eventually, it responds with an HTTP 403 error (_forbidden_). 
  +
  +[source]
  +----
  +io.github.bonigarcia.wdm.config.WebDriverManagerException: Error HTTP 403 executing https://api.github.com/repos/mozilla/geckodriver/releases
  +    at io.github.bonigarcia.wdm.online.HttpClient.execute(HttpClient.java:172)
  +    at io.github.bonigarcia.wdm.WebDriverManager.openGitHubConnection(WebDriverManager.java:1266)
  +    at io.github.bonigarcia.wdm.WebDriverManager.getDriversFromGitHub(WebDriverManager.java:1280)
  +    at io.github.bonigarcia.wdm.managers.FirefoxDriverManager.getDriverUrls(FirefoxDriverManager.java:95)
  +    at io.github.bonigarcia.wdm.WebDriverManager.createUrlHandler(WebDriverManager.java:1111)
  +    at io.github.bonigarcia.wdm.WebDriverManager.download(WebDriverManager.java:959)
  +    at io.githu.bonigarcia.wdm.WebDriverManager.manage(WebDriverManager.java:877)
  +    at io.github.bonigarcia.wdm.WebDriverManager.fallback(WebDriverManager.java:1106)
  +    at io.github.bonigarcia.wdm.WebDriverManager.handleException(WebDriverManager.java:1083)
  +    at io.github.bonigarcia.wdm.WebDriverManager.manage(WebDriverManager.java:883)
  +    at io.github.bonigarcia.wdm.WebDriverManager.setup(WebDriverManager.java:328)
  +----
  +
  +To avoid this problem, WebDriverManager can make authenticated requests using a personal access token. See the <<configuration,configuration>> section to discover how to set up this specify in WebDriverManager.
   
   [discrete]
   ==== Testing localhost
  
positive.code: To configure the WebDriverManager Agent, we need to specify the path of the WebDriverManager https://github.com/bonigarcia/webdrivermanager/releases/download/webdrivermanager-5.0.0/webdrivermanager-5.0.0-fat.jar[fat-JAR] using the JVM flag `-javaagent:/path/to/webdrivermanager-5.0.0-fat.jar`. Alternatively, it can be done using Maven (see a complete project example https://github.com/bonigarcia/wdm-agent-example/[here]).
  
  === Selenium-Jupiter
  WebDriverManager is the heart of the project https://github.com/bonigarcia/selenium-jupiter[Selenium-Jupiter], an open-source JUnit 5 extension for Selenium WebDriver. Selenium-Jupiter uses the programming model provided by JUnit 5 (called _Jupiter_) together with WebDriverManager to create tests with reduced boilerplate code. For instance, thanks to the Jupiter feature for parameter resolution, we can declare a type of the `WebDriver` hierarchy (e.g., `ChromeDriver`) as a test parameter. Selenium-Jupiter resolves its driver and makes it available for the test (and the browser is gracefully closed at the end of the test). For example:
  
  [source,java]
  ----
  
negative.code: ----
  
  === WDM Agent
  WebDriverManager can also be used as _Java Agent_. In this case, and using the JVM instrumentation API, WebDriverManager intercepts calls to applications running on the JVM and modifies their bytecode. In particular, the WebDriverManager Agent uses this technique to check the objects being created in the JVM. Before Selenium WebDriver objects are instantiated (`ChromeDriver`, `FirefoxDriver`, etc.), the required manager is used to resolve its driver (chromedriver, geckodriver, etc.). Thanks to this approach, we can get rid of the WebDriverManager call (e.g. `WebDriverManager.chromedriver.setup();`) from our test, for example:
  
  [source,java]
  ----
  