diff --git a/.github/workflows/validate.yml b/.github/workflows/validate.yml
index fa292e04..08e4cd27 100644
--- a/.github/workflows/validate.yml
+++ b/.github/workflows/validate.yml
@@ -3,7 +3,7 @@ on:
   push:
     branches:
       - '+([0-9])?(.{+([0-9]),x}).x'
-      - 'master'
+      - 'main'
       - 'next'
       - 'next-major'
       - 'beta'
@@ -45,7 +45,7 @@ jobs:
     runs-on: ubuntu-latest
     if:
       ${{ github.repository == 'testing-library/jest-dom' &&
-      contains('refs/heads/master,refs/heads/beta,refs/heads/next,refs/heads/alpha',
+      contains('refs/heads/main,refs/heads/beta,refs/heads/next,refs/heads/alpha',
       github.ref) && github.event_name == 'push' }}
     steps:
       - name: ⬇️ Checkout repo
@@ -71,7 +71,7 @@ jobs:
           branches: |
             [
               '+([0-9])?(.{+([0-9]),x}).x',
-              'master',
+              'main',
               'next',
               'next-major',
               {name: 'beta', prerelease: true},
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index d67d8b5d..e68882cc 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -11,20 +11,20 @@ series [How to Contribute to an Open Source Project on GitHub][egghead]
 2. Run `npm run setup -s` to install dependencies and run validation
 3. Create a branch for your PR with `git checkout -b pr/your-branch-name`
 
-> Tip: Keep your `master` branch pointing at the original repository and make
-> pull requests from branches on your fork. To do this, run:
+> Tip: Keep your `main` branch pointing at the original repository and make pull
+> requests from branches on your fork. To do this, run:
 >
 > ```
 > git remote add upstream https://github.com/testing-library/jest-dom.git
 > git fetch upstream
-> git branch --set-upstream-to=upstream/master master
+> git branch --set-upstream-to=upstream/main main
 > ```
 >
 > This will add the original repository as a "remote" called "upstream," Then
-> fetch the git information from that remote, then set your local `master`
-> branch to use the upstream master branch whenever you run `git pull`. Then you
-> can make all of your pull request branches based on this `master` branch.
-> Whenever you want to update your version of `master`, do a regular `git pull`.
+> fetch the git information from that remote, then set your local `main` branch
+> to use the upstream main branch whenever you run `git pull`. Then you can make
+> all of your pull request branches based on this `main` branch. Whenever you
+> want to update your version of `main`, do a regular `git pull`.
 
 ## Committing and Pushing changes
 
diff --git a/README.md b/README.md
index 542937b8..97da97f9 100644
--- a/README.md
+++ b/README.md
@@ -6,7 +6,7 @@
     height="80"
     width="80"
     alt="owl"
-    src="https://raw.githubusercontent.com/testing-library/jest-dom/master/other/owl.png"
+    src="https://raw.githubusercontent.com/testing-library/jest-dom/main/other/owl.png"
   />
 </a>
 
@@ -1220,14 +1220,14 @@ MIT
 [npmtrends]: http://www.npmtrends.com/@testing-library/jest-dom
 [license-badge]: 
   https://img.shields.io/npm/l/@testing-library/jest-dom.svg?style=flat-square
-[license]: https://github.com/testing-library/jest-dom/blob/master/LICENSE
+[license]: https://github.com/testing-library/jest-dom/blob/main/LICENSE
 [prs-badge]: 
   https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square
 [prs]: http://makeapullrequest.com
 [coc-badge]: 
   https://img.shields.io/badge/code%20of-conduct-ff69b4.svg?style=flat-square
 [coc]: 
-  https://github.com/testing-library/jest-dom/blob/master/other/CODE_OF_CONDUCT.md
+  https://github.com/testing-library/jest-dom/blob/main/other/CODE_OF_CONDUCT.md
 [github-watch-badge]:
   https://img.shields.io/github/watchers/testing-library/jest-dom.svg?style=social
 [github-watch]: https://github.com/testing-library/jest-dom/watchers
diff --git a/other/MAINTAINING.md b/other/MAINTAINING.md
index cade1c2a..da09ba7c 100644
--- a/other/MAINTAINING.md
+++ b/other/MAINTAINING.md
@@ -48,7 +48,7 @@ to release. See the next section on Releases for more about that.
 
 ## Release
 
-Our releases are automatic. They happen whenever code lands into `master`. A
+Our releases are automatic. They happen whenever code lands into `main`. A
 github action gets kicked off and if it's successful, a tool called
 [`semantic-release`](https://github.com/semantic-release/semantic-release) is
 used to automatically publish a new release to npm as well as a changelog to