From af197d80f23a0ee557f9f2b6847337b69f44f7a5 Mon Sep 17 00:00:00 2001
From: "Joakim L. Christiansen" <{ID}+{username}@users.noreply.github.com>
Date: Tue, 22 Aug 2023 23:26:07 +0200
Subject: [PATCH] .

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

diff --git a/readme.md b/readme.md
index 235cb8e..63e0b61 100644
--- a/readme.md
+++ b/readme.md
@@ -41,7 +41,7 @@ Well, originally I had my archiver running in [Node.js](https://nodejs.org/) tog
 
 Hence I had to mitigate their detection and the only way I could reliably do this was to actually run the archiver in the browser (pretending to be Midjourney website itself).
 
-At fist I did this by using the Chrome DevTools Protocol to (locally) inject my own script into their website (which is impossible for them to reliably block). But since it also works to inject the script into their website via the DevTools Console (and this is the simpler way); this is what I have decided to do for now!
+At first I did this by using the Chrome DevTools Protocol to (locally) inject my own script into their website (which is impossible for them to reliably block). But since it also works to inject the script into their website via the DevTools Console (and this is the simpler way); this is what I have decided to do for now!
 
 If they block it I'll find a way around their block. But I'm not trying to misuse their service or anything, all I want is just to enable a way for people to easily backup their own archives (which cost them money to create and which they legally own).