Switch Chromium references to main branch.
Chromium switched to the main branch last week, so update references to
point to that branch.
Change-Id: I7c3699a7c0aa387fbed8dc5ba86487018ff672bc
Reviewed-on: https://pdfium-review.googlesource.com/c/pdfium/+/79250
Commit-Queue: Lei Zhang <thestig@chromium.org>
Commit-Queue: Daniel Hosseinian <dhoss@chromium.org>
Auto-Submit: Lei Zhang <thestig@chromium.org>
Reviewed-by: Daniel Hosseinian <dhoss@chromium.org>
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 5f2a9f7..4c20a5d 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,6 +1,6 @@
# CONTRIBUTING
In general, we follow the
-[Chromium Contributing](https://chromium.googlesource.com/chromium/src/+/master/docs/contributing.md)
+[Chromium Contributing](https://chromium.googlesource.com/chromium/src/+/main/docs/contributing.md)
guidelines in PDFium. The code review process, and the build tools are all very
similar to Chromium. The PDFium
[README](https://pdfium.googlesource.com/pdfium/+/refs/heads/master/README.md)
@@ -145,7 +145,7 @@
discussing with a top-level owner). If the disagreement has moved up through
all the OWNERS files in the PDFium repo, the escalation should then proceed to
the Chromium
-[ENG_REVIEW_OWNERS](https://chromium.googlesource.com/chromium/src/+/refs/heads/master/ENG_REVIEW_OWNERS)
+[ENG_REVIEW_OWNERS](https://chromium.googlesource.com/chromium/src/+/refs/heads/main/ENG_REVIEW_OWNERS)
as the final deciders.
The
