diff --git a/tig-advances/README.md b/tig-advances/README.md
index f47a63c..40e39df 100644
--- a/tig-advances/README.md
+++ b/tig-advances/README.md
@@ -16,7 +16,7 @@ Each submissions is committed to their own branch with the naming pattern:
 2. Email the following to `advances@tig.foundation` with subject "Advance Submission (`<advance_name>`)":
     * **Evidence form**: copy & fill in [`evidence.md`](./evidence.md). Of particular importance is Section 1 which describes your advance
 
-    * **Invention assignment**: copy & replace [invention_assignment.doc](../docs/agreements/invention_assignment.doc) the highlighted parts. Inventor and witness must sign.
+    * **Invention assignment**: copy & replace [invention_assignment.docx](../docs/agreements/invention_assignment.docx) the highlighted parts. Inventor and witness must sign.
 
     * **Address Signature**: use [etherscan](https://etherscan.io/verifiedSignatures#) to sign a message `I am signing this message to confirm my submission of advance <advance_name>`. Use your player_id that is making the submission. Send the verified etherscan link with message and signature.
 
@@ -41,4 +41,4 @@ Each submissions is committed to their own branch with the naming pattern:
 4. At the start of round `X + 4`, if the submission has at least 50% yes votes, it becomes active
 5. Every block, a method's adoption is the sum of all algorithm adoption, where the algorithm is attributed to that method. Methods with at least 50% adoption earn rewards and a merge point
 6. At the end of a round, a method from each challenge with the most merge points, meeting the minimum threshold of 5040, gets merged to the `main` branch
-    * Merged methods are considered advances, and receive rewards every block where their adoption is greater than 0%
\ No newline at end of file
+    * Merged methods are considered advances, and receive rewards every block where their adoption is greater than 0%