chore: fix markdown errors (#2027)[deploy site]

Author: Delta456

CONTRIBUTING.md

@@ -1,4 +1,3 @@
 # Contributing to the Selenium site and docs
 
-Please follow this [link](https://selenium.dev/documentation/about/contributing/) 
-for all the contribution details. 
+Please follow this [link](https://selenium.dev/documentation/about/contributing/) for all the contribution details.

GOVERNANCE.md

@@ -1,3 +1,3 @@
 # Governance
 
-Content moved to https://www.selenium.dev/governance/
+Content moved to <https://www.selenium.dev/governance/>

README.md

@@ -25,31 +25,26 @@ A full contribution guideline can be seen at [contributing](https://selenium.dev
 
 ## How to get involved?
 
-Please check all the information available at https://selenium.dev/getinvolved/
+Please check all the information available at <https://selenium.dev/getinvolved/>
 
-### Do not want to clone the repository to contribute? Use GitPod.
+### Do not want to clone the repository to contribute? Use GitPod
 
 [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/SeleniumHQ/seleniumhq.github.io)
 
-
 ## For Selenium Site and Documentation maintainers
 
 ### How does the site and docs get build?
 
 GitHub actions runs for every commit on each PR and protected branch. The regular CI execution will
 build the site with Hugo to verify that the commit works. The description of these steps can be seen
-at the actions configuration file, [one for testing a PR](./.github/workflows/test.yml), and 
-[one for deploying the site](./.github/workflows/deploy.yml)
+at the actions configuration file, [one for testing a PR](./.github/workflows/test.yml), and [one for deploying the site](./.github/workflows/deploy.yml)
 
 ### How are the site and docs deployed?
 
-After each CI execution that happens in the `trunk` branch, the script [build-site.sh](./build-site.sh) 
-is executed for deployment. This script checks for the string `[deploy site]` in the commit message.
+After each CI execution that happens in the `trunk` branch, the script [build-site.sh](./build-site.sh) is executed for deployment. This script checks for the string `[deploy site]` in the commit message.
 
-If the commit message contains that string, and the commit is in `trunk`, a 
-[GitHub action](./.github/workflows/deploy.yml) is triggered to build and deploy the site. 
-The site and docs will be built, and the changes will be committed to the branch `publish` 
-by the user [Selenium-CI](https://github.com/selenium-ci/).
+If the commit message contains that string, and the commit is in `trunk`, a [GitHub action](./.github/workflows/deploy.yml) is triggered to build and deploy the site.
+The site and docs will be built, and the changes will be committed to the branch `publish` by the user [Selenium-CI](https://github.com/selenium-ci/).
 
 *What is important to take into account is that the source files for the site are in the `trunk`
 branch, and the files that get deployed are pushed to the `publish` branch.*
@@ -59,11 +54,9 @@ repo [settings](https://github.com/SeleniumHQ/seleniumhq.github.io/settings) (if
 you should be able to access the link).
 
 The selenium.
-domain is managed at https://www.gandi.net/en, if you need access to it, reach out to
-any of the [PLC](https://www.selenium.dev/project/structure/#plc) or [TLC](https://www.selenium.dev/project/structure/#tlc)
+domain is managed at <https://www.gandi.net/en>, if you need access to it, reach out to any of the [PLC](https://www.selenium.dev/project/structure/#plc) or [TLC](https://www.selenium.dev/project/structure/#tlc)
 members, who can help you with that.
 
 If for any reason, you need to setup the domain redirection again,
 we followed this [guide](http://spector.io/how-to-set-up-github-pages-with-a-custom-domain-on-gandi/),
-but any tutorial/guide showing how to redirect a domain to GitHub pages should do.   
-
+but any tutorial/guide showing how to redirect a domain to GitHub pages should do.