From 0f17e458c7fb63a7432fcb893a6bb4b72ab32b24 Mon Sep 17 00:00:00 2001
From: M33 <327-m33@git.qoto.org>
Date: Sat, 1 Jan 2022 21:13:49 +0000
Subject: [PATCH] Update README.md

---
 README.md | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 63f50ab..d0e5887 100644
--- a/README.md
+++ b/README.md
@@ -44,10 +44,19 @@ Deploying your misskey instance on arm64 using docker is pretty straightforward,
 
 # Scripts list:
 
-## start_misskey.sh stop_misskey.sh update_misskey.sh
-In a small VPS, or a limited computer like the rapsberry, or just because systemd, you may want to start stop and update misskey with simple scripts like this.
+## start_misskey.sh stop_misskey.sh
+In a small VPS, or a limited computer like the rapsberry, or just because systemd, you may want to start and stop misskey with simple scripts like this.
 For automatic start on boot, you may add this to your crontab: `@reboot /usr/local/bin/start_misskey.sh 1>>/var/log/syslog 2>&1`
 
+## check_update_misskey_git.sh
+This script tries to determine if an update is needed, without pulling all source code from Misskey's github depot.
+Return 1 if an update is detected.
+
+## update_misskey.sh
+Handles the grunt work for a git update, and containers rebuild.
+It takes care of code base backup, you really should take care of database (and maybe data files) backup before upgrading. To this day Misskey updates have not always been a smooth road.
+It may automatically restart your instance to apply the update.
+
 ## backup_postgres.sh
 A daily backup for your docker postgresql database, run it daily
 It will cycle with the day of week (1..7)