From cad02b437a3f74d5a3c93fe7a0d28d768921878c Mon Sep 17 00:00:00 2001 From: Markus Pesch Date: Sat, 19 Jul 2025 15:00:09 +0200 Subject: [PATCH] docs(README): one sentence per line --- README.md | 17 +++++++---------- 1 file changed, 7 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index f00c5c0..72732b5 100644 --- a/README.md +++ b/README.md @@ -819,15 +819,13 @@ gitea: ## TLS certificate rotation -If Gitea uses TLS certificates that are mounted as a secret in the container file system, Gitea will not automatically -apply them when the TLS certificates are rotated. Such a rotation can be for example triggered, when the cert-manager -issues new TLS certificates before expiring. Further information is described as GitHub +If Gitea uses TLS certificates that are mounted as a secret in the container file system, Gitea will not automatically apply them when the TLS certificates are rotated. +Such a rotation can be for example triggered, when the cert-manager issues new TLS certificates before expiring. Further information is described as GitHub [issue](https://github.com/go-gitea/gitea/issues/27962). -Until the issue is present, a workaround can be applied. For example stakater's -[reloader](https://github.com/stakater/Reloader) controller can be used to trigger a rolling update. The following -annotation must be added to instruct the reloader controller to trigger a rolling update, when the mounted `configMaps` -and `secrets` have been changed. +Until the issue is present, a workaround can be applied. +For example stakater's [reloader](https://github.com/stakater/Reloader) controller can be used to trigger a rolling update. +The following annotation must be added to instruct the reloader controller to trigger a rolling update, when the mounted `configMaps` and `secrets` have been changed. ```yaml deployment: @@ -835,9 +833,8 @@ deployment: reloader.stakater.com/auto: "true" ``` -Instead of triggering a rolling update for configMap and secret resources, this action can also be defined for -individual items. For example, when the secret named `gitea-tls` is mounted and the reloader controller should only -listen for changes of this secret: +Instead of triggering a rolling update for configMap and secret resources, this action can also be defined for individual items. +For example, when the secret named `gitea-tls` is mounted and the reloader controller should only listen for changes of this secret: ```yaml deployment: