fix broken links

Author: titusfortner

website_and_docs/content/blog/2010/selenium-1-0-3-released.md

@@ -10,7 +10,7 @@ description: >
 ---
 
 
-Hot off the heals of [1.0.2](/blog/2010/selenium-1.0.2-released-firefox-3.6-and-snow-leopard-support/), 
+Hot off the heals of [1.0.2](../selenium-1.0.2-released-firefox-3.6-and-snow-leopard-support/), 
 we’re releasing Selenium Remote Control 1.0.3. You can download it now (`http://selenium.googlecode.com/files/selenium-remote-control-1.0.3.zip`).
 
 There is no functional difference between this version and 1.0.2, other than it is packaged up a little nicer and we’ve clarified the relationship between selenium-server and the client drivers. That is: we are **not** releasing new client drivers with future 1.x releases. The reason is that we locked down the API in version 1.0.1 and so there is no need to push out the same code each time. As such, when you download 1.0.3, you’ll see all the client drivers are labeled version 1.0.1, which is expected.

website_and_docs/content/blog/2013/selenium-hangout-2-recap.md

@@ -10,7 +10,7 @@ description: >
 ---
 
 
-This is a recap from the most recent Selenium Hangout (a.k.a. [The World’s Best Selenium Meetup](seleniumhq.wordpress.com/2013/08/09/the-worlds-best-selenium-meetup/)). For info on future meetups, [follow them on Twitter](https://twitter.com/SeleniumHangout).
+This is a recap from the most recent Selenium Hangout (a.k.a. [The World’s Best Selenium Meetup](../the-worlds-best-selenium-meetup/)). For info on future meetups, [follow them on Twitter](https://twitter.com/SeleniumHangout).
 
 Thanks to all who attended and tuned into the last Selenium Hangout where we talked about Selenium 3! Below is a write-up of the meetup, the video, and relevant links we mentioned. And to access all meetup videos you can go [here](http://bit.ly/sehovideos).
 

website_and_docs/content/blog/2021/announcing-selenium-4.md

@@ -98,16 +98,16 @@ our users.
 **We hope you enjoy Selenium 4, and we can’t wait to see what you do
 with it!**
 
-[auth]: /documentation/webdriver/bidirectional/bidi_api/#register-basic-auth
+[auth]: /documentation/webdriver/bidirectional/chrome_devtools/bidi_api/#basic-authentication
 [browserstack]: https://www.browserstack.com/
 [chromium]: https://www.chromium.org/Home
 [docker]: https://hub.docker.com/u/selenium
 [docs]: /documentation/getting_started/how_to_upgrade_to_selenium_4/
 [firefox]: https://www.mozilla.org/en-GB/firefox/new/
 [github]: https://github.com/SeleniumHQ/selenium/releases/tag/selenium-4.0.0
 [grid]: /documentation/grid/
-[js errors]: /documentation/webdriver/bidirectional/bidi_api/#listen-to-js-exceptions
-[mutation]: /documentation/webdriver/bidirectional/bidi_api/#mutation-observation
+[js errors]: /documentation/webdriver/bidirectional/chrome_devtools/bidi_api/#javascript-exceptions
+[mutation]: /documentation/webdriver/bidirectional/chrome_devtools/bidi_api/#mutation-observation
 [otel]: https://opentelemetry.io
 [pr]: https://github.com/SeleniumHQ/selenium/pulls
 [relative locators]: /documentation/webdriver/locating_elements/#relative-locators

website_and_docs/content/blog/2021/selenium-4-beta-1.md

@@ -72,4 +72,4 @@ directly from the [Selenium site][download].
 [graphql]: https://github.com/SeleniumHQ/selenium/blob/selenium-4.0.0-beta-1/java/server/src/org/openqa/selenium/grid/graphql/selenium-grid-schema.graphqls
 [OpenTelemetry]: https://opentelemetry.io
 [se4]: /blog/2020/what-is-coming-in-selenium-4-new-tricks/
-[tlc]: /structure/#tlc
+[tlc]: /project/structure/#tlc

website_and_docs/content/documentation/selenium_manager.en.md

@@ -169,7 +169,7 @@ Selenium Manager follows the same versioning schema as Selenium. Nevertheless, w
 For most users, direct interaction with Selenium Manager is not required since the Selenium bindings use it internally. Nevertheless, if you want to *play* with Selenium Manager or use it for your use case involving driver or browser management, you can get the Selenium Manager binaries in different ways:
 
 - From the Selenium repository. The Selenium Manager source code is stored in the main Selenium repo under the folder [rust](https://github.com/SeleniumHQ/selenium/tree/trunk/rust). Moreover, you can find the compiled versions for Windows, Linux, and macOS in the [Selenium Manager Artifacts](https://github.com/SeleniumHQ/selenium_manager_artifacts) repo. The stable Selenium Manager binaries (i.e., those distributed in the latest stable Selenium version) are linked in this [file](https://github.com/SeleniumHQ/selenium/blob/trunk/common/selenium_manager.bzl).
-- From the build workflow. Selenium Manager is compiled using a [GitHub Actions workflow]((https://github.com/SeleniumHQ/selenium/actions/workflows/ci-rust.yml)). This workflow creates binaries for Windows, Linux, and macOS. You can download these binaries from these workflow executions.
+- From the build workflow. Selenium Manager is compiled using a [GitHub Actions workflow](https://github.com/SeleniumHQ/selenium/actions/workflows/ci-rust.yml). This workflow creates binaries for Windows, Linux, and macOS. You can download these binaries from these workflow executions.
 - From the cache. As of version 4.15.0 of the Selenium Java bindings, the Selenium Manager binary is extracted and copied to the cache folder. For instance, the Selenium Manager binary shipped with Selenium 4.15.0 is stored in the folder `~/.cache/selenium/manager/0.4.15`).
 
 ## Examples

website_and_docs/content/documentation/selenium_manager.ja.md

@@ -169,7 +169,7 @@ Selenium Manager follows the same versioning schema as Selenium. Nevertheless, w
 For most users, direct interaction with Selenium Manager is not required since the Selenium bindings use it internally. Nevertheless, if you want to *play* with Selenium Manager or use it for your use case involving driver or browser management, you can get the Selenium Manager binaries in different ways:
 
 - From the Selenium repository. The Selenium Manager source code is stored in the main Selenium repo under the folder [rust](https://github.com/SeleniumHQ/selenium/tree/trunk/rust). Moreover, you can find the compiled versions for Windows, Linux, and macOS in the [Selenium Manager Artifacts](https://github.com/SeleniumHQ/selenium_manager_artifacts) repo. The stable Selenium Manager binaries (i.e., those distributed in the latest stable Selenium version) are linked in this [file](https://github.com/SeleniumHQ/selenium/blob/trunk/common/selenium_manager.bzl).
-- From the build workflow. Selenium Manager is compiled using a [GitHub Actions workflow]((https://github.com/SeleniumHQ/selenium/actions/workflows/ci-rust.yml)). This workflow creates binaries for Windows, Linux, and macOS. You can download these binaries from these workflow executions.
+- From the build workflow. Selenium Manager is compiled using a [GitHub Actions workflow](https://github.com/SeleniumHQ/selenium/actions/workflows/ci-rust.yml). This workflow creates binaries for Windows, Linux, and macOS. You can download these binaries from these workflow executions.
 - From the cache. As of version 4.15.0 of the Selenium Java bindings, the Selenium Manager binary is extracted and copied to the cache folder. For instance, the Selenium Manager binary shipped with Selenium 4.15.0 is stored in the folder `~/.cache/selenium/manager/0.4.15`).
 
 ## Examples

website_and_docs/content/documentation/selenium_manager.pt-br.md

@@ -169,7 +169,7 @@ Selenium Manager follows the same versioning schema as Selenium. Nevertheless, w
 For most users, direct interaction with Selenium Manager is not required since the Selenium bindings use it internally. Nevertheless, if you want to *play* with Selenium Manager or use it for your use case involving driver or browser management, you can get the Selenium Manager binaries in different ways:
 
 - From the Selenium repository. The Selenium Manager source code is stored in the main Selenium repo under the folder [rust](https://github.com/SeleniumHQ/selenium/tree/trunk/rust). Moreover, you can find the compiled versions for Windows, Linux, and macOS in the [Selenium Manager Artifacts](https://github.com/SeleniumHQ/selenium_manager_artifacts) repo. The stable Selenium Manager binaries (i.e., those distributed in the latest stable Selenium version) are linked in this [file](https://github.com/SeleniumHQ/selenium/blob/trunk/common/selenium_manager.bzl).
-- From the build workflow. Selenium Manager is compiled using a [GitHub Actions workflow]((https://github.com/SeleniumHQ/selenium/actions/workflows/ci-rust.yml)). This workflow creates binaries for Windows, Linux, and macOS. You can download these binaries from these workflow executions.
+- From the build workflow. Selenium Manager is compiled using a [GitHub Actions workflow](https://github.com/SeleniumHQ/selenium/actions/workflows/ci-rust.yml). This workflow creates binaries for Windows, Linux, and macOS. You can download these binaries from these workflow executions.
 - From the cache. As of version 4.15.0 of the Selenium Java bindings, the Selenium Manager binary is extracted and copied to the cache folder. For instance, the Selenium Manager binary shipped with Selenium 4.15.0 is stored in the folder `~/.cache/selenium/manager/0.4.15`).
 
 ## Examples

website_and_docs/content/documentation/selenium_manager.zh-cn.md

@@ -169,7 +169,7 @@ Selenium Manager follows the same versioning schema as Selenium. Nevertheless, w
 For most users, direct interaction with Selenium Manager is not required since the Selenium bindings use it internally. Nevertheless, if you want to *play* with Selenium Manager or use it for your use case involving driver or browser management, you can get the Selenium Manager binaries in different ways:
 
 - From the Selenium repository. The Selenium Manager source code is stored in the main Selenium repo under the folder [rust](https://github.com/SeleniumHQ/selenium/tree/trunk/rust). Moreover, you can find the compiled versions for Windows, Linux, and macOS in the [Selenium Manager Artifacts](https://github.com/SeleniumHQ/selenium_manager_artifacts) repo. The stable Selenium Manager binaries (i.e., those distributed in the latest stable Selenium version) are linked in this [file](https://github.com/SeleniumHQ/selenium/blob/trunk/common/selenium_manager.bzl).
-- From the build workflow. Selenium Manager is compiled using a [GitHub Actions workflow]((https://github.com/SeleniumHQ/selenium/actions/workflows/ci-rust.yml)). This workflow creates binaries for Windows, Linux, and macOS. You can download these binaries from these workflow executions.
+- From the build workflow. Selenium Manager is compiled using a [GitHub Actions workflow](https://github.com/SeleniumHQ/selenium/actions/workflows/ci-rust.yml). This workflow creates binaries for Windows, Linux, and macOS. You can download these binaries from these workflow executions.
 - From the cache. As of version 4.15.0 of the Selenium Java bindings, the Selenium Manager binary is extracted and copied to the cache folder. For instance, the Selenium Manager binary shipped with Selenium 4.15.0 is stored in the folder `~/.cache/selenium/manager/0.4.15`).
 
 ## Examples

website_and_docs/content/documentation/webdriver/drivers/remote_webdriver.en.md

@@ -201,7 +201,7 @@ but you can also delete all files during the session.
 
 ## Browser specific functionalities
 
-Each [browser](({{< ref "../browsers/" >}})) has implemented special functionality that is available only to that browser.
+Each [browser]({{< ref "../browsers/" >}}) has implemented special functionality that is available only to that browser.
 Each of the Selenium bindings has implemented a different way to use those features in a Remote Session
 
 {{< tabpane text=true >}}

website_and_docs/content/documentation/webdriver/drivers/remote_webdriver.ja.md

@@ -201,7 +201,7 @@ but you can also delete all files during the session.
 
 ## Browser specific functionalities
 
-Each [browser](({{< ref "../browsers/" >}})) has implemented special functionality that is available only to that browser.
+Each [browser]({{< ref "../browsers/" >}}) has implemented special functionality that is available only to that browser.
 Each of the Selenium bindings has implemented a different way to use those features in a Remote Session
 
 {{< tabpane text=true >}}