From f5d7e754a67e39fe9af5f6f60e3a720a150d4162 Mon Sep 17 00:00:00 2001
From: salartarium <34082385+salartarium@users.noreply.github.com>
Date: Mon, 15 Jan 2024 05:18:33 -0800
Subject: [PATCH 1/3] Update upgrade1.py

update link
---
 eos/db/migrations/upgrade1.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/eos/db/migrations/upgrade1.py b/eos/db/migrations/upgrade1.py
index 9059b28de5..8531a0421d 100644
--- a/eos/db/migrations/upgrade1.py
+++ b/eos/db/migrations/upgrade1.py
@@ -7,7 +7,7 @@
     loaded as they no longer exist in the database. We therefore replace these
     modules with their new replacements
 
-    Based on http://community.eveonline.com/news/patch-notes/patch-notes-for-oceanus/
+    Based on https://www.eveonline.com/news/view/patch-notes-for-oceanus
     and output of itemDiff.py
 """
 

From f5f7f921665eaae97c762c3dabca7879de71e798 Mon Sep 17 00:00:00 2001
From: salartarium <34082385+salartarium@users.noreply.github.com>
Date: Mon, 15 Jan 2024 05:20:26 -0800
Subject: [PATCH 2/3] Update upgrade25.py

update link, typos in comments
---
 eos/db/migrations/upgrade25.py | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/eos/db/migrations/upgrade25.py b/eos/db/migrations/upgrade25.py
index b3a2ce124c..488c90d465 100644
--- a/eos/db/migrations/upgrade25.py
+++ b/eos/db/migrations/upgrade25.py
@@ -2,7 +2,7 @@
 Migration 25
 
 - Converts T3C fitting configurations based on the spreadsheet noted here:
-https://community.eveonline.com/news/patch-notes/patch-notes-for-july-2017-release
+https://www.eveonline.com/news/view/patch-notes-for-july-2017-release
 
 (csv copies can be found on the pyfa repo in case the official documents are deleted)
 
@@ -4228,8 +4228,8 @@ def upgrade(saveddata_engine):
                 # We don't have a conversion for this. I don't think this will ever happen, but who knows
                 continue
 
-            # It doesn't actully matter which old module is replaced with which new module, so we don't have to worry
-            # about module position or anything like that. Just doe a straight up record UPDATE
+            # It doesn't actually matter which old module is replaced with which new module, so we don't have to worry
+            # about module position or anything like that. Just do a straight up record UPDATE
             for i, old in enumerate(oldModules[:4]):
                 saveddata_engine.execute("UPDATE modules SET itemID = ? WHERE ID = ?", (newModules[i], old[0]))
 

From ecf4d6c0de98f9406f08f416f140b01cb4a20714 Mon Sep 17 00:00:00 2001
From: salartarium <34082385+salartarium@users.noreply.github.com>
Date: Mon, 15 Jan 2024 05:21:38 -0800
Subject: [PATCH 3/3] Update upgrade4.py

update link
---
 eos/db/migrations/upgrade4.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/eos/db/migrations/upgrade4.py b/eos/db/migrations/upgrade4.py
index b94d965f2e..257e5a5cd7 100644
--- a/eos/db/migrations/upgrade4.py
+++ b/eos/db/migrations/upgrade4.py
@@ -6,7 +6,7 @@
     from database), which causes pyfa to crash. We therefore replace these
     modules with their new replacements
 
-    Based on http://community.eveonline.com/news/patch-notes/patch-notes-for-proteus/
+    Based on https://www.eveonline.com/news/view/patch-notes-for-proteus
     and output of itemDiff.py
 """