diff --git a/content/blog/2022-05-15-upgrades.md b/content/blog/2022-05-15-upgrades.md
index 8f5ea73..88b5cee 100644
--- a/content/blog/2022-05-15-upgrades.md
+++ b/content/blog/2022-05-15-upgrades.md
@@ -26,11 +26,11 @@ This started to show in the past few weeks to [users running the Gitea binary on
   * downgrade from 1.16.6 or 1.16.7 to 1.16.5 (do **not** downgrade from 1.17.x, it may corrupt your the Gitea database)
 * If the Gitea binary was installed independently of git, upgrade git to a version that is [greater or equal to 2.36](https://git-scm.com/docs/git-config#Documentation/git-config.txt-safedirectory) and disable the security check entirely with:
     * impersonate the [user dedicated to Gitea](https://docs.gitea.io/en-us/install-from-binary/#recommended-server-configuration) (usually git)
-    * `git config --system --replace-all safe.directory '*'`
+    * `git config --global --replace-all safe.directory '*'`
 
 ### Bug fix
 
-The [bug fix](https://github.com/go-gitea/gitea/pull/19707) is for Gitea to ensure `git config --system --replace-all safe.directory '*'` is set on its [dedicated user](https://docs.gitea.io/en-us/install-from-binary/#recommended-server-configuration) when it initializes. It is effective on the condition that the git CLI version is [greater or equal to 2.36](https://git-scm.com/docs/git-config#Documentation/git-config.txt-safedirectory).
+The [bug fix](https://github.com/go-gitea/gitea/pull/19707) is for Gitea to ensure `git config --global --replace-all safe.directory '*'` is set on its [dedicated user](https://docs.gitea.io/en-us/install-from-binary/#recommended-server-configuration) when it initializes. It is effective on the condition that the git CLI version is [greater or equal to 2.36](https://git-scm.com/docs/git-config#Documentation/git-config.txt-safedirectory).
 
 ### Bug fix rationale