From f0528aa2149509a13b8bc317a5615700915b9c7f Mon Sep 17 00:00:00 2001 From: Max Date: Sun, 28 Nov 2021 02:15:05 +0100 Subject: [PATCH] Remove superfluous spaces --- Change-default-CA-to-ZeroSSL.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Change-default-CA-to-ZeroSSL.md b/Change-default-CA-to-ZeroSSL.md index c891659..7abd18c 100644 --- a/Change-default-CA-to-ZeroSSL.md +++ b/Change-default-CA-to-ZeroSSL.md @@ -21,13 +21,13 @@ Q&A: Yes, of course. You are still free to use any supported CA with providing `--server` parameter. ``` - acme.sh --issue -d example.com --dns dns_cf --server letsencrypt + acme.sh --issue -d example.com --dns dns_cf --server letsencrypt ``` 3. What if I don't like this change? I want to stick to letsencrypt? Yes, sure. You can `--set-default-ca` now or any time you like. Then acme.sh will always use the default ca you set: ``` - acme.sh --set-default-ca --server letsencrypt + acme.sh --set-default-ca --server letsencrypt ``` If you set the default CA, acme.sh will respect your choice first. It will always use this default ca in the future, no matter in `v2.*`, `v3.*` or any future `v4.*`. @@ -43,14 +43,14 @@ Q&A: You can also issue certs as normal [See how to issue a cert](https://github.com/acmesh-official/acme.sh/wiki/How-to-issue-a-cert): ``` - acme.sh --issue -d example.com --dns dns_cf + acme.sh --issue -d example.com --dns dns_cf ``` The cert will be issued with the default CA [ZeroSSL](https://github.com/acmesh-official/acme.sh/wiki/ZeroSSL.com-CA) You can also try with letsencrypt: ``` - acme.sh --issue -d example.com --dns dns_cf --server letsencrypt + acme.sh --issue -d example.com --dns dns_cf --server letsencrypt ```