From 8ad4341dd6210d2161ace3bcc8d12207ff4cb1fe Mon Sep 17 00:00:00 2001
From: Cyborus <87248184+Cyborus04@users.noreply.github.com>
Date: Wed, 26 Jul 2023 15:35:53 -0400
Subject: [PATCH] "loose" should be "lose"

# Conflicts:
#	v1.19/admin/upgrade.md
---
 admin/upgrade.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/admin/upgrade.md b/admin/upgrade.md
index bd0aabfe..ffaca2bc 100644
--- a/admin/upgrade.md
+++ b/admin/upgrade.md
@@ -24,7 +24,7 @@ In the simplest case where everything is on a single file system and if the inst
 
 ### Verify Forgejo works
 
-It is **critical** to verify that Forgejo works very carefully. Restoring the backup done before the upgrade is easy and does not loose any information. But if a problem is discovered days or weeks after the upgrade, it will not be an option and fixing it on a live Forgejo instance will be much more challenging.
+It is **critical** to verify that Forgejo works very carefully. Restoring the backup done before the upgrade is easy and does not lose any information. But if a problem is discovered days or weeks after the upgrade, it will not be an option and fixing it on a live Forgejo instance will be much more challenging.
 
 - Run `forgejo doctor --all --log-file /tmp/doctor.log` and make sure it does not report any problem.
 - Manually verify via the web interface. Making a checklist of a typical use case is a good way to not miss anything.