[docs] use relative paths for links

Add some minor cleanups to extension_query_script.md.

Change-Id: Ic5930697cbe75818bf774462971b7b1d03975ee6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3029301
Reviewed-by: Tien Mai <tienmai@chromium.org>
Commit-Queue: Tien Mai <tienmai@chromium.org>
Auto-Submit: Johann Koenig <johannkoenig@google.com>
Cr-Commit-Position: refs/heads/master@{#902553}

docs/cl_respect.md

@@ -52,7 +52,7 @@ looking at OWNERS files, asking a teammate, or using tools ('_git cl owners_',
 #### Provide context
 
 Change descriptions are the first impression your change makes, both on
-reviewers and on code archeologists from the future. A [good description](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/contributing.md#Uploading-a-change-for-review)
+reviewers and on code archeologists from the future. A [good description](contributing.md#Uploading-a-change-for-review)
 aims to do two things. First, it conveys at a glance the high level view.
 Second, it provides references to all the relevant information for a deep dive:
 design docs, bugs, testing instructions. The bug\# is a useful reference, but

docs/enterprise/add_new_policy.md

@@ -65,7 +65,7 @@ Usually you need a policy when
             traditionally, and we've seen requests from organizations to
             explicitly spell out the behavior for all possible values and for
             when the policy is unset.
-    -   See [description_guidelines.md](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/enterprise/description_guidelines.md)
+    -   See [description_guidelines.md](description_guidelines.md)
         for additional guidelines when creating a description, including how
         various products should be referenced.
 3.  Create a preference and map the policy value to it.

docs/enterprise/extension_query_script.md

@@ -19,14 +19,12 @@ Before using CBCM Takeout API you will need to do some initial setup:
     settings -> Manage API client access. On this page, the Client ID
     corresponds to the Unique ID of your service account. You will need to
     authorize the client ID for the scope:
-    *   https://www.googleapis.com/auth/admin.directory.device.chromebrowsers.readonly
+    * https://www.googleapis.com/auth/admin.directory.device.chromebrowsers.readonly
 
 ## Running the Script
 
-You can download the scripts
-[here](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/enterprise/extension_query.py)
-or here [here](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/enterprise/extension_query_py2.py)
-for a python 2.7 compatible version.
+You can download the scripts [here](extension_query.py) (or [here](extension_query_py2.py)
+for a python 2.7 compatible version).
 
 With the service account keys, you can now run the script which uses Google API
 Client Libraries to make the necessary queries to the API. The script requires
@@ -34,10 +32,14 @@ that both the service account keys you downloaded from the developers console as
 well as the e-mail of an admin user in your domain that is allowed to access the
 data you wish to query.
 
-You can run the script from the command-line: python extension_query.py
---service_account_key_path <service_account_key_file> --admin_email
-<admin_email> (also: `python extension_query.py --help` for a reminder of the
+You can run the script from the command-line:
+``` sh
+python extension_query.py --service_account_key_path <service_account_key_file> --admin_email <admin_email>
+```
+(also: `python extension_query.py --help` for a reminder of the
 argument names)
 
-Example Data output Here is an example of what that data will look like:
-![Sample Results](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/enterprise/extension_query_sample.png)
+## Example Data output
+
+Here is an example of what that data will look like:
+![Sample Results](extension_query_sample.png)

docs/mac_lld.md

@@ -62,8 +62,7 @@ There are a few open issues:
 
 ## Hacking on LLD
 
-If you want to work on LLD, follow
-[this paragraph](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/clang.md#Using-a-custom-clang-binary).
+If you want to work on LLD, follow [this paragraph](clang.md#Using-a-custom-clang-binary).
 
 ## Creating stand-alone repros for bugs
 
@@ -71,4 +70,4 @@ For simple cases, LLD's `--reproduce=foo.tar` flag / `LLD_REPRODUCE=foo.tar`
 env var is sufficient.
 
 See "Note to self:" [here](https://bugs.llvm.org/show_bug.cgi?id=48657#c0) for
-making a repro file that involved the full app and framework bundles.
+making a repro file that involved the full app and framework bundles.

docs/vscode.md

@@ -43,8 +43,8 @@ Here's what works well:
 Please keep this doc up-to-date. VS Code is still in active development and
 subject to changes. This doc is checked into the Chromium git repo, so if you
 make changes, read the [documentation
-guidelines](https://chromium.googlesource.com/chromium/src/+/main/docs/documentation_guidelines.md)
-and [submit a change list](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/contributing.md).
+guidelines](documentation_guidelines.md)
+and [submit a change list](contributing.md).
 
 All file paths and commands have been tested on Linux. Windows and Mac might
 require a slightly different setup (e.g. `Ctrl` -> `Cmd`). Please update this