[devtools] add some quick links to the readme for locating the necessary files when adding new devtools versions

Author: titusfortner

common/devtools/README.md

@@ -10,17 +10,19 @@ Fortunately both Chrome and Edge are based off Chromium releases and those
 are OSS. In order to get the versions of the protocol spoken by particular
 releases of Chrome:
 
-  * Find out the latest release version of stable Chrome (as I write this 
-    it's `84.0.4147.125`).
+* Find out the latest version of [Stable Channel Update for Desktop](https://chromereleases.googleblog.com/search/label/Stable%20updates)
+  (e.g., `84.0.4147.125`).
   * Navigate to the [Chromium source](https://github.com/chromium/chromium/)
   * Open the tag matching the release number.
   * Grab `//third_party/blink/public/devtools_protocol/browser_protocol.pdl`
+    (Quick link: https://raw.githubusercontent.com/chromium/chromium/<LATEST_VERSION_NUMBER>/third_party/blink/public/devtools_protocol/browser_protocol.pdl)
   * Now figure out the version of v8 used by the version of Chromium. In
     Chromium's source, navigate to `//:DEPS` and search for `v8_revision`
+    (Quick link: https://github.com/chromium/chromium/blob/<LATEST_VERSION_NUMBER>/DEPS#:~:text=the%20commit%20queue%20can%20handle%20cls%20rolling%20v8)
   * Head over to the [v8 source](https://github.com/v8/v8) and switch to
-    the indicated revision (as I write this it's 
-    `451d38b60be0a0f692b11815289cf8cbc9b1dc98`)
+    the indicated revision (e.g., `451d38b60be0a0f692b11815289cf8cbc9b1dc98`)
   * Grab `//include:js_protocol.pdl`
+    (Quick link: https://github.com/v8/v8/raw/<V8_REVISION_NUMBER>/include/js_protocol.pdl)
 
 You may also find the same information at the [OmahaProxy CSV 
 Viewer](https://omahaproxy.appspot.com)