[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 <[email protected]>
Commit-Queue: Tien Mai <[email protected]>
Auto-Submit: Johann Koenig <[email protected]>
Cr-Commit-Position: refs/heads/master@{#902553}
diff --git a/docs/cl_respect.md b/docs/cl_respect.md
index 225af940..12018aa 100644
--- a/docs/cl_respect.md
+++ b/docs/cl_respect.md
@@ -52,7 +52,7 @@
#### 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
