From 320408d5c79ce9c930d34212464e84d1ada3d312 Mon Sep 17 00:00:00 2001
From: Christian <43847817+codiflow@users.noreply.github.com>
Date: Thu, 13 Apr 2023 15:03:13 +0200
Subject: [PATCH] Clarified what happens after --install-cert command

---
 README.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 15bc4089..0a9c8a3a 100644
--- a/README.md
+++ b/README.md
@@ -239,8 +239,9 @@ The ownership and permission info of existing files are preserved. You can pre-c
 
 Install/copy the cert/key to the production Apache or Nginx path.
 
-The cert will be renewed every **60** days by default (which is configurable). Once the cert is renewed, the Apache/Nginx service will be reloaded automatically by the command: `service apache2 force-reload` or `service nginx force-reload`.
+There's no need to issue the command `--install-command` again because the given paths are stored inside the configuration file of each certificate (`.acme.sh/example.com_ecc/example.com.conf`).
 
+The cert will be renewed every **60** days by default (which is configurable). Once the cert is renewed, the Apache/Nginx service will be reloaded automatically by the command: `service apache2 force-reload` or `service nginx force-reload`.
 
 **Please take care:  The reloadcmd is very important. The cert can be automatically renewed, but, without a correct 'reloadcmd' the cert may not be flushed to your server(like nginx or apache), then your website will not be able to show renewed cert in 60 days.**