docs(cryptosctl): say a switched-off block's settings change needs no reboot

The config get help and the ACME and EST warnings said every protocol
change waits for a reboot. Changing only the settings of a block with
enabled: false is live, so say so.

Signed-off-by: Bugs5382 <12115015+Bugs5382@users.noreply.github.com>

Author: Bugs5382

cmd/cryptosctl/config.go

@@ -60,8 +60,9 @@ func newConfigGetCmd(opts *globalOpts) *cobra.Command {
 			"hmac_key_base64 and password_sha256 are write-only. Leave a blank secret " +
 			"as it is and `config apply` keeps the one the node stores for that key_id " +
 			"or username; set it to replace it. A new key_id or username needs its " +
-			"secret. Switching a protocol on or off, or changing its settings, takes " +
-			"effect at the next reboot.",
+			"secret. Switching a protocol on or off, or changing the settings of one " +
+			"that is on, takes effect at the next reboot. A block with enabled: false " +
+			"keeps its settings; changing only those needs no reboot.",
 		Args: cobra.NoArgs,
 		RunE: func(cmd *cobra.Command, _ []string) error {
 			client, closeConn, err := dial(opts)

docs/acme.md

@@ -173,8 +173,8 @@ Over the API the block is `Pki.acme` with an explicit `enabled` flag.
 of an `ApplyConfig` keeps what the node has, on or off.
 
 > [!WARNING]
-> Every ACME change, switching it on or off included, takes effect at the
-> next reboot, not when you apply it. `config apply` stores the change and
+> Switching ACME on or off, or changing its settings while it is on, takes
+> effect at the next reboot, not when you apply it. `config apply` stores the change and
 > prints `requires_reboot=true`; the listener starts, stops or picks up the new
 > settings only when the node boots again. Plan the reboot for a maintenance
 > window, because the node stops issuing while it restarts, then use

docs/est.md

@@ -235,8 +235,8 @@ Over the API the block is `Pki.est` with an explicit `enabled` flag.
 of an `ApplyConfig` keeps what the node has, on or off.
 
 > [!WARNING]
-> Every EST change, switching it on or off included, takes effect at the
-> next reboot, not when you apply it. `config apply` stores the change and
+> Switching EST on or off, or changing its settings while it is on, takes
+> effect at the next reboot, not when you apply it. `config apply` stores the change and
 > prints `requires_reboot=true`; the listener starts, stops or picks up the new
 > settings only when the node boots again. Plan the reboot for a maintenance
 > window, because the node stops issuing while it restarts, then use