[COIL] Change chromium code search type links to use main rather than master for docs
See this doc: go/chromium-coil-change for more info
BUG=1210385
Change-Id: I6cd8548301e360bae8e71384dbd8ef11aa6c985f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2902904
Reviewed-by: My Nguyen <[email protected]>
Commit-Queue: My Nguyen <[email protected]>
Auto-Submit: John Palmer <[email protected]>
Cr-Commit-Position: refs/heads/master@{#885851}
diff --git a/docs/documentation_guidelines.md b/docs/documentation_guidelines.md
index e934bbc..a2e0937e 100644
--- a/docs/documentation_guidelines.md
+++ b/docs/documentation_guidelines.md
@@ -65,7 +65,7 @@
If you got this far and have some experience with Chromium's code, you'll have figured out that these guidelines are aspirational more than what the world looks like today. So what do we do when working with existing code.
-First off: ***[Documentation changes can be TBRed](https://chromium.googlesource.com/chromium/src/+/master/docs/code_reviews.md#documentation-updates)***. Even in-code changes. If you have discovered something that isn't documented, have figured out how it works and would like to pay it forward, feel free to write something down and check it in.
+First off: ***[Documentation changes can be TBRed](https://chromium.googlesource.com/chromium/src/+/main/docs/code_reviews.md#documentation-updates)***. Even in-code changes. If you have discovered something that isn't documented, have figured out how it works and would like to pay it forward, feel free to write something down and check it in.
At the component level, if you are the owner of a component that isn't documented, please add a README.md with content as per the above.
