diff --git a/Contributing.md b/Contributing.md
index c4eb2f0..37a573c 100644
--- a/Contributing.md
+++ b/Contributing.md
@@ -27,9 +27,7 @@ steps for creating a successful PR:
 6. Push your code and create a PR on github. Please make sure to reference your
    issue number in your PR description.
 
-Branch all work off the `master` branch. In the future, we will create branches
-for specific release series, and `master` will be used for the current stable
-release series.
+Branch all work off the `main` branch.
 
 ### Documentation
 
diff --git a/Readme.md b/Readme.md
index 8732d4f..c9aa30b 100644
--- a/Readme.md
+++ b/Readme.md
@@ -1,6 +1,6 @@
 # HTTPure
 
-[![License](https://img.shields.io/badge/license-MIT-blue.svg)](https://raw.githubusercontent.com/cprussin/purescript-httpure/master/License)
+[![License](https://img.shields.io/badge/license-MIT-blue.svg)](https://raw.githubusercontent.com/cprussin/purescript-httpure/main/License)
 [![Latest release](http://img.shields.io/github/release/cprussin/purescript-httpure.svg)](https://github.com/cprussin/purescript-httpure/releases)
 [![purescript-httpure on Pursuit](https://pursuit.purescript.org/packages/purescript-httpure/badge)](https://pursuit.purescript.org/packages/purescript-httpure)
 
diff --git a/Releasing.md b/Releasing.md
index c945077..d8d8ff4 100644
--- a/Releasing.md
+++ b/Releasing.md
@@ -1,8 +1,7 @@
 # HTTPure Releasing Guide
 
-1. Check out the release series branch (or `master` if you are releasing the
-   next major/minor version). Ensure all relevant commits and PRs have been
-   merged.
+1. Check out the release series branch (or `main` if you are releasing the next 
+   major/minor version). Ensure all relevant commits and PRs have been merged.
 2. Update [History.md](./History.md) by changing "unreleased" to the new
    version/date.  Example diff:
 ```diff