docs: Make bare URLs clickable (see #4085)

Author: magreenblatt

docs/automated_build_setup.md

@@ -17,7 +17,7 @@ This page describes the setup of an automated build system for CEF.
 
 # Overview
 
-CEF provides tools for automatically downloading, building and packaging Chromium and CEF source code. These tools are the recommended way of building CEF locally and can also be integrated with an automated build system. Examples of automated build systems for CEF include https://cef-builds.spotifycdn.com/index.html hosted by Spotify. This document outlines how to build a system similar to Spotify's. For general CEF build instructions see the [Branches And Building](branches_and_building.md) page.
+CEF provides tools for automatically downloading, building and packaging Chromium and CEF source code. These tools are the recommended way of building CEF locally and can also be integrated with an automated build system. Examples of automated build systems for CEF include <https://cef-builds.spotifycdn.com/index.html> hosted by Spotify. This document outlines how to build a system similar to Spotify's. For general CEF build instructions see the [Branches And Building](branches_and_building.md) page.
 
 # Services
 
@@ -39,7 +39,7 @@ The reference build system works by executing the following steps in order:
 
 Runs automatically at some interval (for example, once daily) to check if a new change has been committed to the CEF repository. The [GitHub REST API](https://docs.github.com/en/rest/branches/branches#get-a-branch) exposes an endpoint that can be queried to identify the most recent commit in a branch. For example, this will return the most recent commit for 2785 branch:
 
-https://api.github.com/repos/chromiumembedded/cef/branches/2785
+<https://api.github.com/repos/chromiumembedded/cef/branches/2785>
 
 The resulting "commit.sha" value can then be compared to the last successful CEF build version to identify if a new build is required (e.g. a sha value of "1e15b7626244fa6c6455b7a24552664e4cc14fd3" from branch 2785 will match a build artifact file named "cef_binary_3.2785.\*.g1e15b76_\*.tar.bz2").
 

docs/branches_and_building.md

@@ -33,7 +33,7 @@ Win 10+ deployment, Win 10+ build system w/ VS2022 17.13.4, Win 10.0.26100.4654
 
 The following URLs should be used for downloading development versions of CEF.
 
-  * CEF3 - https://github.com/chromiumembedded/cef/tree/master
+  * CEF3 - <https://github.com/chromiumembedded/cef/tree/master>
 
 CEF1 is no longer actively developed or supported. See the [CEF1 Retirement Plan](http://magpcss.org/ceforum/viewtopic.php?f=10&t=10647) for details.
 

docs/chromium_update.md

@@ -118,7 +118,7 @@ $ cd /path/to/chromium_git/chromium/src
 $ git log --full-history -1 -- content/public/browser/document_service_base.h
 ```
 
-Once you know the offending Git commit hash you can use the `git show <hash>` command or load `https://crrev.com/<hash>` in a web browser to see the contents of the change. Edit the patch file manually in a text editor to fix the paths and then re-run the `patch_updater.py` script as shown above.
+Once you know the offending Git commit hash you can use the `git show <hash>` command or load <https://crrev.com/>`<hash>` in a web browser to see the contents of the change. Edit the patch file manually in a text editor to fix the paths and then re-run the `patch_updater.py` script as shown above.
 
 **To create a new patch file use this command:**
 

docs/contributing_with_git.md

@@ -27,7 +27,7 @@ The CEF project uses the Git source code management system hosted via GitHub. Th
 
 Git can maintain your changes both locally and on a remote server. To work with Git efficiently the remote server locations must be configured properly.
 
-1\. Log into GitHub and create a public forked version of the cef.git repository using the Fork button at https://github.com/chromiumembedded/cef. This public linked fork will be used to create and submit pull requests.
+1\. Log into GitHub and create a public forked version of the cef.git repository using the Fork button at <https://github.com/chromiumembedded/cef>. This public linked fork will be used to create and submit pull requests.
 
 2\. Optionally, create a private unlinked fork using git commands directly. This private fork can be used for day-to-day development without exposing your work publicly.
 

docs/linking_different_runtime_libraries.md

@@ -44,4 +44,4 @@ Sandbox support (linking `cef_sandbox.lib`) is only possible when your applicati
 # Additional Information
 
 More information on Microsoft run-time flags can be found here:
-http://msdn.microsoft.com/en-us/library/2kzt1wy3.aspx
+<http://msdn.microsoft.com/en-us/library/2kzt1wy3.aspx>