From 9ec14470de96604b7248e77124cfddd1a43e3036 Mon Sep 17 00:00:00 2001
From: Mike Lissner <mike@free.law>
Date: Wed, 20 Mar 2024 10:11:32 -0700
Subject: [PATCH] fix(docs): s/freelawproject.org/free.law/

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 8c4a7775..630e96d1 100644
--- a/README.md
+++ b/README.md
@@ -82,7 +82,7 @@ When a new version is needed, the release process is:
 1. Commit the code.
 1. Tag the code with something like:
 
-        git tag -s '0.8.4' -m "Releases 0.8.4, fixing replaceState and pushState to work in Chrome 43." -u 'mike@freelawproject.org' -f
+        git tag -s '0.8.4' -m "Releases 0.8.4, fixing replaceState and pushState to work in Chrome 43." -u 'mike@free.law' -f
         git push --tags -f
 
 1. Make sure you don't have any working/testing code in your tree that could get zipped up in the next step.