diff --git a/Change-default-CA-to-ZeroSSL.md b/Change-of-default-CA-to-ZeroSSL.md
similarity index 57%
rename from Change-default-CA-to-ZeroSSL.md
rename to Change-of-default-CA-to-ZeroSSL.md
index b7b8ceb..7298dc3 100644
--- a/Change-default-CA-to-ZeroSSL.md
+++ b/Change-of-default-CA-to-ZeroSSL.md
@@ -1,4 +1,4 @@
-Previously, if no `server` was provided, or if don't have `--set-default-ca` set, acme.sh used letsencrypt as the default CA.
+Previously, if no `server` was provided, or if `--set-default-ca` was not run, acme.sh used letsencrypt as the default CA.
 
 https://github.com/acmesh-official/acme.sh/wiki/Server
 
@@ -13,22 +13,22 @@ Q&A:
 
 1. As an existing user, what do I need to do?
 
-    Generally, nothing needs to do.  (If auto-upgrade is enabled, acme.sh can upgrade itself). 
-    No matter acme.sh is upgraded to v3.0 or not, your existing certs will be renewed as before, against the same CA it's currently using.
+    Generally, nothing needs doing.  (If auto-upgrade is enabled, acme.sh can upgrade itself). 
+    No matter if acme.sh is upgraded to v3.0 or not, your existing certs will be renewed as before, against the same CA they're currently using.
 
 2. Will I still be able to use letsencrypt then?
 
-    Yes, of course. You are still free to use any supported CA with providing `--server` parameter.
+    Yes, of course. You are still free to use any supported CA by providing `--server` parameter.
     ```
     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?
+3. What if I don't like this change, and 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:
+    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
     ```
-    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.*`.
+    If you set the default CA, acme.sh will respect your choice first. It will always use this default CA in the future, in `v2.*`, `v3.*` or any future `v4.*`.
 
     **acme.sh always respects your choice first, and will never make any changes to your files without your permissions.**
 
@@ -38,14 +38,14 @@ Q&A:
 
 5. As a new user after `August-1st 2021`(v3.0), what will it look like to me?
 
-    You can install acme.sh as normal, nothing is changed.
+    You can install acme.sh as normal, nothing has changed.
     
-    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):
+    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
     ```
 
-    The cert will be issued with the default CA [ZeroSSL](https://github.com/acmesh-official/acme.sh/wiki/ZeroSSL.com-CA)
+    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:
     ```
@@ -53,7 +53,7 @@ Q&A:
     ```
 
 
-There is a comparison: ZeroSSL vs Let's Encrypt:
+Here is a comparison of ZeroSSL to Let's Encrypt:
 
 https://zerossl.com/letsencrypt-alternative/