diff --git a/content/blog/2022-05-15-unsafe-repository-is-owned-by-someone-else.md b/content/blog/2022-05-15-unsafe-repository-is-owned-by-someone-else.md
index 85d7403..ada848b 100644
--- a/content/blog/2022-05-15-unsafe-repository-is-owned-by-someone-else.md
+++ b/content/blog/2022-05-15-unsafe-repository-is-owned-by-someone-else.md
@@ -22,11 +22,11 @@ This started to show in the past few weeks to [users running the Gitea binary on
 ### Workarounds
 
 * If using [Gitea docker images](https://hub.docker.com/r/gitea/gitea):
-  * do not upgrade to 1.16.6, 1.16.7 or 1.16.8, or
-  * downgrade from 1.16.6, 1.16.7 or 1.16.8 to 1.16.5 (do **not** downgrade from 1.17.x, it may corrupt your the Gitea database)
+  * upgrade to [Gitea >=1.16.9](https://github.com/go-gitea/gitea/pull/19876) or 1.17, both have git >=2.36
+  * `git config --global --replace-all safe.directory '*'`
 * 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 --global --replace-all safe.directory '*'`
+  * impersonate the [user dedicated to Gitea](https://docs.gitea.io/en-us/install-from-binary/#recommended-server-configuration) (usually git)
+  * `git config --global --replace-all safe.directory '*'`
 
 ### Bug fix