From 72c45de1d1e999043130dcb41f8602c951c24db1 Mon Sep 17 00:00:00 2001
From: xeruf <27jf@pm.me>
Date: Thu, 23 Jan 2025 13:02:40 +0100
Subject: [PATCH] docs: small readme updates

---
 README.md | 11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/README.md b/README.md
index ea26fd7..18cfce5 100644
--- a/README.md
+++ b/README.md
@@ -531,7 +531,7 @@ postgresql:
 
 This chart enables you to create a default admin user.
 It is also possible to update the password for this user by upgrading or redeploying the chart.
-Deleting the admin user can only be done from the UI.
+To delete it, you need to remove this block and delete the user in the UI.
 You cannot use `admin` as username.
 
 ```yaml
@@ -693,12 +693,7 @@ route:
 
 When using the rootless image, the GPG key folder is not persistent by default.
 If you want commits by Forgejo (e.g. initial commit) to be signed,
-you need to provide a signing key.
-Prior to [PR186](https://gitea.com/gitea/helm-chart/pulls/186),
-imported keys had to be re-imported once the container got replaced by another.
-
-The mentioned PR introduced a new configuration object `signing` so you can configure prerequisites for commit signing.
-By default this section is disabled to maintain backwards compatibility.
+you need to provide a signing key:
 
 ```yaml
 signing:
@@ -706,6 +701,8 @@ signing:
   gpgHome: /data/git/.gnupg
 ```
 
+By default this section is disabled to maintain backwards compatibility.
+
 Regardless of the used container image the `signing` object allows to specify a private GPG key.
 Either using the `signing.privateKey` to define the key inline, or referring to an existing secret containing the key data with `signing.existingSecret`.