diff --git a/dnsapi.md b/DNS-API-plugins.md
similarity index 86%
rename from dnsapi.md
rename to DNS-API-plugins.md
index b960c8e..e4504e5 100644
--- a/dnsapi.md
+++ b/DNS-API-plugins.md
@@ -10,13 +10,13 @@ Cloudflare Domain API offers two methods to automatically issue certs.
 
 ### Using the global API key
 First you need to login to your Cloudflare account to get your [API key](https://dash.cloudflare.com/profile). Each token generated is not stored on cloudflare account and will have expiry if not set correctly. You will get this in API keys section.  
-```
+```sh
 export CF_Key="sdfsdfsdfljlbjkljlkjsdfoiwje"
 export CF_Email="xxxx@sss.com"
 ```
 
 ### Using the new cloudflare api token, you will get this after normal login and  scroll down on dashboard and copy credentials. 
-```
+```sh
 export CF_Token="sdfsdfsdfljlbjkljlkjsdfoiwje"
 export CF_Account_ID="xxxxxxxxxxxxx"
 ```
@@ -24,15 +24,15 @@ In order to use the new token, the token currently needs access read access to Z
 
 Alternatively, if the certificate only covers a single zone, you can restrict the API Token only for write access to Zone.DNS for a single domain, and then specify the `CF_Zone_ID` directly:
 
-```
+```sh
 export CF_Token="sdfsdfsdfljlbjkljlkjsdfoiwje"
 export CF_Account_ID="xxxxxxxxxxxxx"
 export CF_Zone_ID="xxxxxxxxxxxxx"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_cf -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_cf -d example.com -d www.example.com
 ```
 
 The `CF_Key` and `CF_Email` or `CF_Token`and `CF_Account_ID`will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -41,14 +41,14 @@ The `CF_Key` and `CF_Email` or `CF_Token`and `CF_Account_ID`will be saved in `~/
 
 The DNSPod.cn Domain API option requires that you first login to your account to get a DNSPod API Key and ID.
 
-```
+```sh
 export DP_Id="1234"
 export DP_Key="sADDsdasdgdsf"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_dp -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_dp -d example.com -d www.example.com
 ```
 
 The `DP_Id` and `DP_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -58,14 +58,14 @@ The `DP_Id` and `DP_Key` will be saved in `~/.acme.sh/account.conf` and will be
 
 First you need to login to your CloudXNS account to get your API Key and Secret.
 
-```
+```sh
 export CX_Key="1234"
 export CX_Secret="sADDsdasdgdsf"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_cx -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_cx -d example.com -d www.example.com
 ```
 
 The `CX_Key` and `CX_Secret` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -79,14 +79,14 @@ https://developer.godaddy.com/keys/
 
 Please create a Production key, instead of a Test key.
 
-```
+```sh
 export GD_Key="sdfsdfsdfljlbjkljlkjsdfoiwje"
 export GD_Secret="asdfsdafdsfdsfdsfdsfdsafd"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_gd -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_gd -d example.com -d www.example.com
 ```
 
 The `GD_Key` and `GD_Secret` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -98,7 +98,7 @@ First you need to login to your PowerDNS account to enable the API and set your
 
 https://doc.powerdns.com/md/httpapi/README/
 
-```
+```sh
 export PDNS_Url="http://ns.example.com:8081"
 export PDNS_ServerId="localhost"
 export PDNS_Token="0123456789ABCDEF"
@@ -106,8 +106,8 @@ export PDNS_Ttl=60
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_pdns -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_pdns -d example.com -d www.example.com
 ```
 
 The `PDNS_Url`, `PDNS_ServerId`, `PDNS_Token` and `PDNS_Ttl` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -121,7 +121,7 @@ https://github.com/Neilpang/acme.sh/wiki/How-to-use-OVH-domain-api
 ## 7. Use nsupdate to automatically issue cert
 
 First, generate a key for updating the zone
-```
+```sh
 b=$(dnssec-keygen -a hmac-sha512 -b 512 -n USER -K /tmp foo)
 cat > /etc/named/keys/update.key <<EOF
 key "update" {
@@ -133,21 +133,21 @@ rm -f /tmp/$b.{private,key}
 ```
 
 Include this key in your named configuration
-```
+```sh
 include "/etc/named/keys/update.key";
 ```
 
 Next, configure your zone to allow dynamic updates.
 
 Depending on your named version, use either
-```
+```sh
 zone "example.com" {
     type master;
     allow-update { key "update"; };
 };
 ```
 or
-```
+```sh
 zone "example.com" {
     type master;
     update-policy {
@@ -157,7 +157,7 @@ zone "example.com" {
 ```
 Notes on BIND 9.16.1-Ubuntu 20.04.3 LTS
 
-```
+```sh
 # dnssec-keygen no longer do tsig algorithm, so tsig-keygen (came with bind9)
 tsig-keygen -a hmac-sha512 acme | sudo tee /etc/bind/acme.key
 # as nsupdate need creation of *.jnl where zone file resides, read /var/log/syslog for error details
@@ -166,21 +166,20 @@ sudo chmod g+w /etc/bind
 # echo 'include "/etc/bind/acme.key";' | sudo tee --append /etc/bind/named.conf.local
 ```
 
-
 Finally, make the DNS server and update Key available to `acme.sh`
 
-```
+```sh
 export NSUPDATE_SERVER="dns.example.com"
 export NSUPDATE_KEY="/path/to/your/nsupdate.key"
 ```
 and optionally (depending on DNS server)
-```
+```sh
 export NSUPDATE_ZONE="example.com"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_nsupdate -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_nsupdate -d example.com -d www.example.com
 ```
 
 The `NSUPDATE_SERVER`, `NSUPDATE_KEY`, and `NSUPDATE_ZONE` settings will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -190,31 +189,30 @@ The `NSUPDATE_SERVER`, `NSUPDATE_KEY`, and `NSUPDATE_ZONE` settings will be save
 
 Get your API token at https://api.luadns.com/settings
 
-```
+```sh
 export LUA_Key="sdfsdfsdfljlbjkljlkjsdfoiwje"
 export LUA_Email="xxxx@sss.com"
 ```
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_lua -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_lua -d example.com -d www.example.com
 ```
 
 The `LUA_Key` and `LUA_Email` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
-
 ## 9. Use DNSMadeEasy domain API
 
 Get your API credentials at https://cp.dnsmadeeasy.com/account/info
 
-```
+```sh
 export ME_Key="sdfsdfsdfljlbjkljlkjsdfoiwje"
 export ME_Secret="qdfqsdfkjdskfj"
 ```
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_me -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_me -d example.com -d www.example.com
 ```
 
 The `ME_Key` and `ME_Secret` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -224,20 +222,19 @@ The `ME_Key` and `ME_Secret` will be saved in `~/.acme.sh/account.conf` and will
 
 https://github.com/Neilpang/acme.sh/wiki/How-to-use-Amazon-Route53-API
 
-```
+```sh
 export  AWS_ACCESS_KEY_ID=XXXXXXXXXX
 export  AWS_SECRET_ACCESS_KEY=XXXXXXXXXXXXXXX
-
 ```
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_aws -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_aws -d example.com -d www.example.com
 ```
 
 If you get an `AWS Route53 rate exceeded` error, you can add a sleep time between api requests:
 
-```
+```sh
 export  AWS_DNS_SLOWRATE=1 (sleep between API requests in seconds)
 ```
 
@@ -248,14 +245,14 @@ The `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY` and `AWS_DNS_SLOWRATE` will be
 First you need to login to your Aliyun account to get your RAM API key.
 [https://ram.console.aliyun.com/users](https://ram.console.aliyun.com/users)
 
-```
+```sh
 export Ali_Key="sdfsdfsdfljlbjkljlkjsdfoiwje"
 export Ali_Secret="jlsdflanljkljlfdsaklkjflsa"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_ali -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_ali -d example.com -d www.example.com
 ```
 
 The `Ali_Key` and `Ali_Secret` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -266,7 +263,7 @@ This only works for ISPConfig 3.1 (and newer).
 
 Create a Remote User in the ISPConfig Control Panel. The Remote User must have access to at least `DNS zone functions`, `DNS txt functions` and `Client functions`.
 
-```
+```sh
 export ISPC_User="xxx"
 export ISPC_Password="xxx"
 export ISPC_Api="https://ispc.domain.tld:8080/remote/json.php"
@@ -276,8 +273,8 @@ If you have installed ISPConfig on a different port, then alter the 8080 accordi
 Leave ISPC_Api_Insecure set to 1 if you have no valid ssl cert for your installation. Change it to 0 if you have a valid ssl cert.
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_ispconfig -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_ispconfig -d example.com -d www.example.com
 ```
 
 The `ISPC_User`, `ISPC_Password`, `ISPC_Api`and `ISPC_Api_Insecure` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -293,7 +290,7 @@ export AD_API_KEY="myalwaysdataapikey"
 Ok, let's issue a cert now:
 
 ```sh
-acme.sh --issue --dns dns_ad -d example.com -d www.example.com
+./acme.sh --issue --dns dns_ad -d example.com -d www.example.com
 ```
 
 The `AD_API_KEY` will be saved in `~/.acme.sh/account.conf` and will be reused
@@ -322,7 +319,7 @@ Due to the reload time of any changes in the DNS records, we have to use the
 Ok, let's issue a cert now:
 
 ```sh
-acme.sh --issue --dns dns_linode_v4 --dnssleep 900 -d example.com -d www.example.com
+./acme.sh --issue --dns dns_linode_v4 --dnssleep 900 -d example.com -d www.example.com
 ```
 
 The `LINODE_V4_API_KEY` will be saved in `~/.acme.sh/account.conf` and will be
@@ -348,7 +345,7 @@ reuses that when needed.
 Now you can issue a certificate.
 
 ```sh
-acme.sh --issue --dns dns_freedns -d example.com -d www.example.com
+./acme.sh --issue --dns dns_freedns -d example.com -d www.example.com
 ```
 
 Note that you cannot use acme.sh automatic DNS validation for FreeDNS public domains or for a subdomain that
@@ -363,15 +360,15 @@ https://github.com/Neilpang/acme.sh/issues/2305
 You only need to set your cyon.ch login credentials.
 If you also have 2 Factor Authentication (OTP) enabled, you need to set your secret token too and have `oathtool` installed.
 
-```
+```sh
 export CY_Username="your_cyon_username"
 export CY_Password="your_cyon_password"
 export CY_OTP_Secret="your_otp_secret" # Only required if using 2FA
 ```
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_cyon -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_cyon -d example.com -d www.example.com
 ```
 
 The `CY_Username`, `CY_Password` and `CY_OTP_Secret` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -381,40 +378,40 @@ The `CY_Username`, `CY_Password` and `CY_OTP_Secret` will be saved in `~/.acme.s
 ATTENTION: You need to be a registered Reseller to be able to use the ResellerInterface. As a normal user you can not use this method.
 
 You will need your login credentials (Partner ID+Password) to the Resellerinterface, and export them before you run `acme.sh`:
-```
+```sh
 export DO_PID="KD-1234567"
 export DO_PW="cdfkjl3n2"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_do -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_do -d example.com -d www.example.com
 ```
 
 ## 18. Use Gandi LiveDNS API
 
 You must enable the new Gandi LiveDNS API first and the create your api key, See: https://api.gandi.net/docs/livedns/
 
-```
+```sh
 export GANDI_LIVEDNS_KEY="fdmlfsdklmfdkmqsdfk"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_gandi_livedns -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_gandi_livedns -d example.com -d www.example.com
 ```
 
 ## 19. Use Knot (knsupdate) DNS API to automatically issue cert
 
 First, generate a TSIG key for updating the zone.
 
-```
+```sh
 keymgr tsig generate -t acme_key hmac-sha512 > /etc/knot/acme.key
 ```
 
 Include this key in your knot configuration file.
 
-```
+```sh
 include: /etc/knot/acme.key
 ```
 
@@ -422,7 +419,7 @@ Next, configure your zone to allow dynamic updates.
 
 Dynamic updates for the zone are allowed via proper ACL rule with the `update` action. For in-depth instructions, please see [Knot DNS's documentation](https://www.knot-dns.cz/documentation/).
 
-```
+```sh
 acl:
   - id: acme_acl
     address: 192.168.1.0/24
@@ -437,20 +434,20 @@ zone:
 
 Finally, make the DNS server and TSIG Key available to `acme.sh`
 
-```
+```sh
 export KNOT_SERVER="dns.example.com"
 export KNOT_KEY=`grep \# /etc/knot/acme.key | cut -d' ' -f2`
 ```
 
 and optionally (if you use challenge alias zone)
 
-```
+```sh
 export KNOT_ZONE="le.example.com"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_knot -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_knot -d example.com -d www.example.com
 ```
 
 The `KNOT_SERVER` and `KNOT_KEY` and `KNOT_ZONE` settings will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -459,20 +456,20 @@ The `KNOT_SERVER` and `KNOT_KEY` and `KNOT_ZONE` settings will be saved in `~/.a
 
 You need to obtain a read and write capable API key from your DigitalOcean account. See: https://www.digitalocean.com/help/api/
 
-```
+```sh
 export DO_API_KEY="75310dc4ca779ac39a19f6355db573b49ce92ae126553ebd61ac3a3ae34834cc"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_dgon -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_dgon -d example.com -d www.example.com
 ```
 
 ## 21. Use ClouDNS.net API
 
 You need to set the HTTP API user ID and password credentials. See: https://www.cloudns.net/wiki/article/42/. For security reasons, it's recommended to use a sub user ID that only has access to the necessary zones, as a regular API user has access to your entire account.
 
-```
+```sh
 # Use this for a sub auth ID
 export CLOUDNS_SUB_AUTH_ID=XXXXX
 # Use this for a regular auth ID
@@ -481,8 +478,8 @@ export CLOUDNS_AUTH_PASSWORD="YYYYYYYYY"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_cloudns -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_cloudns -d example.com -d www.example.com
 ```
 The `CLOUDNS_AUTH_ID` and `CLOUDNS_AUTH_PASSWORD` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
@@ -490,14 +487,14 @@ The `CLOUDNS_AUTH_ID` and `CLOUDNS_AUTH_PASSWORD` will be saved in `~/.acme.sh/a
 
 First you need to create/obtain API credentials on your Infoblox appliance.
 
-```
+```sh
 export Infoblox_Creds="username:password"
 export Infoblox_Server="ip or fqdn of infoblox appliance"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_infoblox -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_infoblox -d example.com -d www.example.com
 ```
 
 Note: This script will automatically create and delete the ephemeral txt record.
@@ -508,27 +505,27 @@ The `Infoblox_Creds` and `Infoblox_Server` will be saved in `~/.acme.sh/account.
 
 First you need to create/obtain API tokens on your [settings panel](https://vscale.io/panel/settings/tokens/).
 
-```
+```sh
 export VSCALE_API_KEY="sdfsdfsdfljlbjkljlkjsdfoiwje"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_vscale -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_vscale -d example.com -d www.example.com
 ```
 
 ##  24. Use Dynu API
 
 First you need to create/obtain API credentials from your Dynu account. See: https://www.dynu.com/resources/api/documentation
 
-```
+```sh
 export Dynu_ClientId="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
 export Dynu_Secret="yyyyyyyyyyyyyyyyyyyyyyyyy"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_dynu -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_dynu -d example.com -d www.example.com
 ```
 
 The `Dynu_ClientId` and `Dynu_Secret` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -543,14 +540,14 @@ Note that this is an _account_ token and not a user token. The account token is
 needed to infer the `account_id` used in requests. A user token will not be able
 to determine the correct account to use.
 
-```
+```sh
 export DNSimple_OAUTH_TOKEN="sdfsdfsdfljlbjkljlkjsdfoiwje"
 ```
 
 To issue the cert just specify the `dns_dnsimple` API.
 
-```
-acme.sh --issue --dns dns_dnsimple -d example.com
+```sh
+./acme.sh --issue --dns dns_dnsimple -d example.com
 ```
 
 The `DNSimple_OAUTH_TOKEN` will be saved in `~/.acme.sh/account.conf` and will
@@ -561,18 +558,18 @@ https://github.com/pho3nixf1re/acme.sh/issues.
 
 ## 26. Use NS1.com API
 
-```
+```sh
 export NS1_Key="fdmlfsdklmfdkmqsdfk"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_nsone -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_nsone -d example.com -d www.example.com
 ```
 
 ## 27. Use DuckDNS.org API
 
-```
+```sh
 export DuckDNS_Token="aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee"
 ```
 
@@ -588,15 +585,15 @@ Create your API token here: https://www.name.com/account/settings/api
 
 Note: `Namecom_Username` should be your Name.com username and not the token name.  If you accidentally run the script with the token name as the username see `~/.acme.sh/account.conf` to fix the issue
 
-```
+```sh
 export Namecom_Username="testuser"
 export Namecom_Token="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
 ```
 
 And now you can issue certs with:
 
-```
-acme.sh --issue --dns dns_namecom -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_namecom -d example.com -d www.example.com
 ```
 If you had Two-step Authentication enabled, make sure to change your security setting, read this guide for help: [Using API with Two-step Authentication](https://www.name.com/support/articles/360007989433-Using-API-with-Two-step-Authentication)
 
@@ -621,28 +618,28 @@ ZonePublish
 ```
 
 Pass the API user credentials to the environment:
-```
+```sh
 export DYN_Customer="customer"
 export DYN_Username="apiuser"
 export DYN_Password="secret"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_dyn -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_dyn -d example.com -d www.example.com
 ```
 
 The `DYN_Customer`, `DYN_Username` and `DYN_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
 ## 30. Use pdd.yandex.ru API
 
-```
+```sh
 export PDD_Token="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
 ```
 
 Follow these instructions to get the token for your domain https://tech.yandex.com/domain/doc/concepts/access-docpage/
-```
-acme.sh --issue --dns dns_yandex -d mydomain.example.org
+```sh
+./acme.sh --issue --dns dns_yandex -d mydomain.example.org
 ```
 
 Sometimes cloudflare / google doesn't pick new dns records fast enough. You can add `--dnssleep XXX` to params as workaround.
@@ -653,15 +650,15 @@ For issues, please report to https://github.com/non7top/acme.sh/issues.
 
 Hurricane Electric (https://dns.he.net/) doesn't have an API so just set your login credentials like so:
 
-```
+```sh
 export HE_Username="yourusername"
 export HE_Password="password"
 ```
 
 Then you can issue your certificate:
 
-```
-acme.sh --issue --dns dns_he -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_he -d example.com -d www.example.com
 ```
 
 The `HE_Username` and `HE_Password` settings will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -672,14 +669,14 @@ Please report any issues to https://github.com/angel333/acme.sh or to <me@ondrej
 
 First you need to login to your UnoEuro account to get your API key.
 
-```
+```sh
 export UNO_Key="sdfsdfsdfljlbjkljlkjsdfoiwje"
 export UNO_User="UExxxxxx"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_unoeuro -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_unoeuro -d example.com -d www.example.com
 ```
 
 The `UNO_Key` and `UNO_User` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -688,22 +685,22 @@ The `UNO_Key` and `UNO_User` will be saved in `~/.acme.sh/account.conf` and will
 
 [INWX](https://www.inwx.de/) offers an [xmlrpc api](https://www.inwx.de/de/help/apidoc)  with your standard login credentials, set them like so:
 
-```
+```sh
 export INWX_User="yourusername"
 export INWX_Password="password"
 ```
 
 Then you can issue your certificates with:
 
-```
-acme.sh --issue --dns dns_inwx -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_inwx -d example.com -d www.example.com
 ```
 
 The `INWX_User` and `INWX_Password` settings will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
 If your account is secured by mobile tan you have also defined the shared secret.
 
-```
+```sh
 export INWX_Shared_Secret="shared secret"
 ```
 
@@ -713,15 +710,15 @@ You may need to re-enable the mobile tan to gain the shared secret.
 
 Create a new user from the servercow control center. Don't forget to activate **DNS API** for this user.
 
-```
+```sh
 export SERVERCOW_API_Username=username
 export SERVERCOW_API_Password=password
 ```
 
 Now you cann issue a cert:
 
-```
-acme.sh --issue --dns dns_servercow -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_servercow -d example.com -d www.example.com
 ```
 Both, `SERVERCOW_API_Username` and `SERVERCOW_API_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
@@ -730,21 +727,21 @@ Both, `SERVERCOW_API_Username` and `SERVERCOW_API_Password` will be saved in `~/
 You'll need to generate an API key at https://www.namesilo.com/account/api-manager
 Optionally you may restrict the access to an IP range there.
 
-```
+```sh
 export Namesilo_Key="xxxxxxxxxxxxxxxxxxxxxxxx"
 ```
 
 And now you can issue certs with:
 
-```
-acme.sh --issue --dns dns_namesilo --dnssleep 900 -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_namesilo --dnssleep 900 -d example.com -d www.example.com
 ```
 
 ## 36. Use autoDNS (InternetX)
 
 [InternetX](https://www.internetx.com/) offers an [xml api](https://help.internetx.com/display/API/AutoDNS+XML-API)  with your standard login credentials, set them like so:
 
-```
+```sh
 export AUTODNS_USER="yourusername"
 export AUTODNS_PASSWORD="password"
 export AUTODNS_CONTEXT="context"
@@ -752,8 +749,8 @@ export AUTODNS_CONTEXT="context"
 
 Then you can issue your certificates with:
 
-```
-acme.sh --issue --dns dns_autodns -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_autodns -d example.com -d www.example.com
 ```
 
 The `AUTODNS_USER`, `AUTODNS_PASSWORD` and `AUTODNS_CONTEXT` settings will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -762,7 +759,7 @@ The `AUTODNS_USER`, `AUTODNS_PASSWORD` and `AUTODNS_CONTEXT` settings will be sa
 
 You have to create a service principal first. See:[How to use Azure DNS](https://github.com/acmesh-official/acme.sh/wiki/How-to-use-Azure-DNS)
 
-```
+```sh
 export AZUREDNS_SUBSCRIPTIONID="12345678-9abc-def0-1234-567890abcdef"
 export AZUREDNS_TENANTID="11111111-2222-3333-4444-555555555555"
 export AZUREDNS_APPID="3b5033b5-7a66-43a5-b3b9-a36b9e7c25ed"
@@ -771,8 +768,8 @@ export AZUREDNS_CLIENTSECRET="1b0224ef-34d4-5af9-110f-77f527d561bd"
 
 Then you can issue your certificates with:
 
-```
-acme.sh --issue --dns dns_azure -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_azure -d example.com -d www.example.com
 ```
 
 `AZUREDNS_SUBSCRIPTIONID`, `AZUREDNS_TENANTID`,`AZUREDNS_APPID` and `AZUREDNS_CLIENTSECRET` settings will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -799,8 +796,8 @@ export SL_Key="sdfsdfsdfljlbjkljlkjsdfoiwje"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_selectel -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_selectel -d example.com -d www.example.com
 ```
 
 The `SL_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -821,8 +818,8 @@ export ZM_Key="1063364558943540954358668888888888"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_zonomi -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_zonomi -d example.com -d www.example.com
 ```
 
 The `ZM_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -832,9 +829,9 @@ The `ZM_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when
 DNS API keys may be created at https://panel.dreamhost.com/?tree=home.api.
 Ensure the created key has add and remove privelages.
 
-```
+```sh
 export DH_API_KEY="<api key>"
-acme.sh --issue --dns dns_dreamhost -d example.com -d www.example.com
+./acme.sh --issue --dns dns_dreamhost -d example.com -d www.example.com
 ```
 
 The 'DH_API_KEY' will be saved in `~/.acme.sh/account.conf` and will
@@ -854,15 +851,15 @@ You can create an user which only has access to
 By using the Login Keys function.
 See also https://www.directadmin.com/api.php and https://www.directadmin.com/features.php?id=1298
 
-```
+```sh
 export DA_Api="https://remoteUser:remotePassword@da.domain.tld:8443"
 export DA_Api_Insecure=1
 ```
 Set `DA_Api_Insecure` to 1 for insecure and 0 for secure -> difference is whether ssl cert is checked for validity (0) or whether it is just accepted (1)
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_da -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_da -d example.com -d www.example.com
 ```
 
 The `DA_Api` and `DA_Api_Insecure` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -871,10 +868,10 @@ The `DA_Api` and `DA_Api_Insecure` will be saved in `~/.acme.sh/account.conf` an
 
 API access must be enabled at https://painel.kinghost.com.br/painel.api.php
 
-```
+```sh
 export KINGHOST_Username="yourusername"
 export KINGHOST_Password="yourpassword"
-acme.sh --issue --dns dns_kinghost -d example.com -d *.example.com
+./acme.sh --issue --dns dns_kinghost -d example.com -d *.example.com
 ```
 
 The `KINGHOST_username` and `KINGHOST_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -883,13 +880,13 @@ The `KINGHOST_username` and `KINGHOST_Password` will be saved in `~/.acme.sh/acc
 
 First, get your API key at https://my.zilore.com/account/api
 
-```
+```sh
 export Zilore_Key="5dcad3a2-36cb-50e8-cb92-000002f9"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_zilore -d example.com -d *.example.com
+```sh
+./acme.sh --issue --dns dns_zilore -d example.com -d *.example.com
 ```
 
 The `Zilore_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -908,7 +905,7 @@ The user needs the following permissions:
 
 Set the API endpoint:
 
-```
+```sh
 export LOOPIA_Api="https://api.loopia.<TLD>/RPCSERV"
 ```
 
@@ -917,15 +914,15 @@ Depending on your hosting location, `<TLD>` is one of: `com`, `no`,
 
 Set the login credentials:
 
-```
+```sh
 export LOOPIA_User="user@loopiaapi"
 export LOOPIA_Password="password"
 ```
 
 And to issue a cert run:
 
-```
-acme.sh --issue --dns dns_loopia -d example.com -d *.example.com
+```sh
+./acme.sh --issue --dns dns_loopia -d example.com -d *.example.com
 ```
 
 The exported variables will be saved in `~/.acme.sh/account.conf` and
@@ -946,7 +943,7 @@ https://github.com/joohoi/acme-dns
 # export ACMEDNS_PASSWORD="<password>"
 # export ACMEDNS_SUBDOMAIN="<subdomain>"
 
-acme.sh --issue --dns dns_acmedns -d example.com -d www.example.com
+./acme.sh --issue --dns dns_acmedns -d example.com -d www.example.com
 ```
 
 The credentials will be saved in `~/.acme.sh/account.conf` and will
@@ -956,11 +953,11 @@ be reused when needed.
 First you need to login to your TELE3 account to set your API-KEY.
 https://www.tele3.cz/system-acme-api.html
 
-```
+```sh
 export TELE3_Key="MS2I4uPPaI..."
 export TELE3_Secret="kjhOIHGJKHg"
 
-acme.sh --issue --dns dns_tele3 -d example.com -d *.example.com
+./acme.sh --issue --dns dns_tele3 -d example.com -d *.example.com
 ```
 
 The TELE3_Key and TELE3_Secret will be saved in ~/.acme.sh/account.conf and will be reused when needed.
@@ -973,14 +970,14 @@ First you need to login to your euserv.eu account and activate your API Administ
 Once you've activate, login to your API Admin Interface and create an API account.
 Please specify the scope (active groups: domain) and assign the allowed IPs.
 
-```
+```sh
 export EUSERV_Username="99999.user123"
 export EUSERV_Password="Asbe54gHde"
 ```
 
 Ok, let's issue a cert now: (Be aware to use the `--insecure` flag, cause euserv.eu is still using self-signed certificates!)
-```
-acme.sh --issue --dns dns_euserv -d example.com -d *.example.com --insecure
+```sh
+./acme.sh --issue --dns dns_euserv -d example.com -d *.example.com --insecure
 ```
 
 The `EUSERV_Username` and `EUSERV_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -991,14 +988,14 @@ Please report any issues to https://github.com/initit/acme.sh or to <github@init
 
 First you need to get your API Key and ID by this [get-the-user-token](https://www.dnspod.com/docs/info.html#get-the-user-token).
 
-```
+```sh
 export DPI_Id="1234"
 export DPI_Key="sADDsdasdgdsf"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_dpi -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_dpi -d example.com -d www.example.com
 ```
 
 The `DPI_Id` and `DPI_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1017,9 +1014,9 @@ If needed, create additional [gcloud configurations](https://cloud.google.com/sd
 You can change the configuration being used without *activating* it; simply set the `CLOUDSDK_ACTIVE_CONFIG_NAME` environment variable.
 
 To issue a certificate you can:
-```
+```sh
 export CLOUDSDK_ACTIVE_CONFIG_NAME=default  # see the note above
-acme.sh --issue --dns dns_gcloud -d example.com -d '*.example.com'
+./acme.sh --issue --dns dns_gcloud -d example.com -d '*.example.com'
 ```
 
 `dns_gcloud` also supports [DNS alias mode](https://github.com/Neilpang/acme.sh/wiki/DNS-alias-mode).
@@ -1028,7 +1025,7 @@ acme.sh --issue --dns dns_gcloud -d example.com -d '*.example.com'
 
 First you need to login to your ConoHa account to get your API credentials.
 
-```
+```sh
 export CONOHA_Username="xxxxxx"
 export CONOHA_Password="xxxxxx"
 export CONOHA_TenantId="xxxxxx"
@@ -1036,8 +1033,8 @@ export CONOHA_IdentityServiceApi="https://identity.xxxx.conoha.io/v2.0"
 ```
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_conoha -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_conoha -d example.com -d www.example.com
 ```
 
 The `CONOHA_Username`, `CONOHA_Password`, `CONOHA_TenantId` and `CONOHA_IdentityServiceApi` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1045,15 +1042,15 @@ The `CONOHA_Username`, `CONOHA_Password`, `CONOHA_TenantId` and `CONOHA_Identity
 ## 51. Use netcup DNS API to automatically issue cert
 
 First you need to login in your CCP account to get your API Key and API Password.
-```
+```sh
 export NC_Apikey="<Apikey>"
 export NC_Apipw="<Apipassword>"
 export NC_CID="<Customernumber>"
 ```
 
 Now, let's issue a cert:
-```
-acme.sh --issue --dns dns_netcup -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_netcup -d example.com -d www.example.com
 ```
 
 The `NC_Apikey`,`NC_Apipw` and `NC_CID` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1077,7 +1074,7 @@ Note: It usually takes a few minutes (usually 3-4 minutes) before the changes pr
 and in rare cases I have seen over 5 minutes before google DNS catches it. Therefor a DNS sleep of at least 300 seconds are recommended-
 
 ```sh
-acme.sh --issue --dns dns_gdnsdk --dnssleep 300 -d example.com -d *.example.com
+./acme.sh --issue --dns dns_gdnsdk --dnssleep 300 -d example.com -d *.example.com
 ```
 
 ## 53. Use Namecheap
@@ -1098,7 +1095,7 @@ The username and password will be saved in `~/.acme.sh/account.conf` and will be
 Now you can issue a certificate.
 
 ```sh
-acme.sh --issue --dns dns_namecheap -d example.com -d *.example.com
+./acme.sh --issue --dns dns_namecheap -d example.com -d *.example.com
 ```
 
 If you find any bugs of namecheap dns API, please report here: https://github.com/Neilpang/acme.sh/issues/2107
@@ -1107,15 +1104,15 @@ If you find any bugs of namecheap dns API, please report here: https://github.co
 
 First, register to MyDNS.JP and get MasterID and Password.
 
-```
+```sh
 export MYDNSJP_MasterID=MasterID
 export MYDNSJP_Password=Password
 ```
 
 To issue a certificate:
 
-```
-acme.sh --issue --dns dns_mydnsjp -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_mydnsjp -d example.com -d www.example.com
 ```
 The `MYDNSJP_MasterID` and `MYDNSJP_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
@@ -1129,7 +1126,7 @@ The key needs the following rights:
 
 Set your API Key and endpoint:
 
-```
+```sh
 export HOSTINGDE_APIKEY='xxx'
 export HOSTINGDE_ENDPOINT='https://secure.hosting.de'
 ```
@@ -1137,21 +1134,21 @@ export HOSTINGDE_ENDPOINT='https://secure.hosting.de'
 The plugin can also be used for the http.net API. http.net customers have to set endpoint to https://partner.http.net.
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_hostingde -d example.com -d *.example.com
+```sh
+./acme.sh --issue --dns dns_hostingde -d example.com -d *.example.com
 ```
 
 The hosting.de API key and endpoint will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
 ## 56. Use Neodigit.net API
 
-```
+```sh
 export NEODIGIT_API_TOKEN="eXJxTkdUVUZmcHQ3QWJackQ4ZGlMejRDSklRYmo5VG5zcFFKK2thYnE0WnVnNnMy"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_neodigit -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_neodigit -d example.com -d www.example.com
 ```
 
 Neodigit API Token will be saved in `~/.acme.sh/account.conf` and will be used when needed.
@@ -1162,14 +1159,14 @@ Create an API key and secret key in the Exoscale account section
 
 Set your API and secret key:
 
-```
+```sh
 export EXOSCALE_API_KEY='xxx'
 export EXOSCALE_SECRET_KEY='xxx'
 ```
 
 Now, let's issue a cert:
-```
-acme.sh --issue --dns dns_exoscale -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_exoscale -d example.com -d www.example.com
 ```
 
 The `EXOSCALE_API_KEY` and `EXOSCALE_SECRET_KEY` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1183,7 +1180,7 @@ exportPointHQ_Email="accountemail@yourdomain.com"
 ```
 
 You can then issue certs by using:
-```acme.sh --issue --dns dns_pointhq -d example.com -d www.example.com
+```./acme.sh --issue --dns dns_pointhq -d example.com -d www.example.com
 ```
 
 ## 59. Use Active24 API
@@ -1192,13 +1189,13 @@ Create an API token in the Active24 account section, documentation on https://fa
 
 Set your API token:
 
-```
+```sh
 export ACTIVE24_Token='xxx'
 ```
 
 Now, let's issue a cert, set `dnssleep` for propagation new DNS record:
-```
-acme.sh --issue --dns dns_active24 -d example.com -d www.example.com --dnssleep 1000
+```sh
+./acme.sh --issue --dns dns_active24 -d example.com -d www.example.com --dnssleep 1000
 ```
 
 The `ACTIVE24_Token` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1208,13 +1205,13 @@ The `ACTIVE24_Token` will be saved in `~/.acme.sh/account.conf` and will be reus
 Create an API token in your do.de account ([Create token here](https://www.do.de/account/letsencrypt/) | [Documentation](https://www.do.de/wiki/LetsEncrypt_-_Entwickler)).
 
 Set your API token:
-```
+```sh
 export DO_LETOKEN='FmD408PdqT1E269gUK57'
 ```
 
 To issue a certificate run:
-```
-acme.sh --issue --dns dns_doapi -d example.com -d *.example.com
+```sh
+./acme.sh --issue --dns dns_doapi -d example.com -d *.example.com
 ```
 
 The API token will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1225,15 +1222,15 @@ First, you'll need to login to the [Nexcess.net Client Portal](https://portal.ne
 
 Once you have a token, set it in your systems environment:
 
-```
+```sh
 export NW_API_TOKEN="YOUR_TOKEN_HERE"
 export NW_API_ENDPOINT="https://portal.nexcess.net"
 ```
 
 Finally, we'll issue the certificate: (Nexcess DNS publishes at max every 15 minutes, we recommend setting a 900 second `--dnssleep`)
 
-```
-acme.sh --issue --dns dns_nw -d example.com --dnssleep 900
+```sh
+./acme.sh --issue --dns dns_nw -d example.com --dnssleep 900
 ```
 
 The `NW_API_TOKEN` and `NW_API_ENDPOINT` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1246,15 +1243,15 @@ First, you'll need to login to the [Thermo.io Client Portal](https://core.thermo
 
 Once you have a token, set it in your systems environment:
 
-```
+```sh
 export NW_API_TOKEN="YOUR_TOKEN_HERE"
 export NW_API_ENDPOINT="https://core.thermo.io"
 ```
 
 Finally, we'll issue the certificate: (Thermo DNS publishes at max every 15 minutes, we recommend setting a 900 second `--dnssleep`)
 
-```
-acme.sh --issue --dns dns_nw -d example.com --dnssleep 900
+```sh
+./acme.sh --issue --dns dns_nw -d example.com --dnssleep 900
 ```
 
 The `NW_API_TOKEN` and `NW_API_ENDPOINT` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1265,15 +1262,15 @@ First, you'll need to login to the [Futurehosting Client Portal](https://my.futu
 
 Once you have a token, set it in your systems environment:
 
-```
+```sh
 export NW_API_TOKEN="YOUR_TOKEN_HERE"
 export NW_API_ENDPOINT="https://my.futurehosting.com"
 ```
 
 Finally, we'll issue the certificate: (Futurehosting DNS publishes at max every 15 minutes, we recommend setting a 900 second `--dnssleep`)
 
-```
-acme.sh --issue --dns dns_nw -d example.com --dnssleep 900
+```sh
+./acme.sh --issue --dns dns_nw -d example.com --dnssleep 900
 ```
 
 The `NW_API_TOKEN` and `NW_API_ENDPOINT` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1282,15 +1279,15 @@ The `NW_API_TOKEN` and `NW_API_ENDPOINT` will be saved in `~/.acme.sh/account.co
 
 Set username and API key, which is available under "My Profile & Settings"
 
-```
+```sh
 export RACKSPACE_Username='username'
 export RACKSPACE_Apikey='xxx'
 ```
 
 Now, let's issue a cert:
 
-```
-acme.sh --issue --dns dns_rackspace -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_rackspace -d example.com -d www.example.com
 ```
 
 If you find any bugs of Rackspace dns API, please report here: https://github.com/Neilpang/acme.sh/issues/2091
@@ -1299,14 +1296,14 @@ If you find any bugs of Rackspace dns API, please report here: https://github.co
 
 First, you'll need to retrive your API key, which is available under https://console.online.net/en/api/access
 
-```
+```sh
 export ONLINE_API_KEY='xxx'
 ```
 
 To issue a cert run:
 
-```
-acme.sh --issue --dns dns_online -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_online -d example.com -d www.example.com
 ```
 
 `ONLINE_API_KEY` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1328,7 +1325,7 @@ If you're not using private IP and depend on default IP provided by host, you ma
 To issue a new certificate, run:
 
 ```sh
-acme.sh --issue --dns dns_mydevil -d example.com -d *.example.com
+./acme.sh --issue --dns dns_mydevil -d example.com -d *.example.com
 ```
 
 After certificate is ready, you can install it with [deploy command](https://github.com/Neilpang/acme.sh/wiki/deployhooks#14-deploy-your-cert-on-mydevilnet).
@@ -1338,14 +1335,14 @@ After certificate is ready, you can install it with [deploy command](https://git
 First you need to login to your Core-Networks account to to set up an API-User.
 Then export username and password to use these credentials.
 
-```
+```sh
 export CN_User="user"
 export CN_Password="passowrd"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_cn -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_cn -d example.com -d www.example.com
 ```
 
 The `CN_User` and `CN_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1357,13 +1354,13 @@ If you find any bugs of core-networks.de dns API, please report here: https://gi
 Create an API token in Mijn NederHost.
 
 Set your API key:
-```
+```sh
 export NederHost_Key='xxx'
 ```
 
 To issue a certificate run:
-```
-acme.sh --issue --dns dns_nederhost -d example.com -d *.example.com
+```sh
+./acme.sh --issue --dns dns_nederhost -d example.com -d *.example.com
 ```
 
 If you find any bugs of NederHost dns API, please report here: https://github.com/Neilpang/acme.sh/issues/2089
@@ -1372,15 +1369,15 @@ If you find any bugs of NederHost dns API, please report here: https://github.co
 
 First, you'll need to retrive your API key. Estonian insructions https://help.zone.eu/kb/zoneid-api-v2/
 
-```
+```sh
 export ZONE_Username=yourusername
 export ZONE_Key=keygoeshere
 ```
 
 To issue a cert run:
 
-```
-acme.sh --issue -d example.com -d www.example.com --dns dns_zone
+```sh
+./acme.sh --issue -d example.com -d www.example.com --dns dns_zone
 ```
 
 `ZONE_Username` and `ZONE_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1402,13 +1399,13 @@ Set your UltraDNS User name, and password; these would be the same you would use
 
 https://portal.ultradns.com/ - or if you create an API only user, that username and password would be better utilized.
 
-```
+```sh
 export ULTRA_USR="abcd"
 export ULTRA_PWD="efgh"
 
 To issue a cert run:
 
-acme.sh --issue --dns dns_ultra -d example.com -d www.example.com
+./acme.sh --issue --dns dns_ultra -d example.com -d www.example.com
 ```
 
 `ULTRA_USR` and `ULTRA_PWD` will be saved in `~/.acme.sh/account.conf` and will be resued when needed.
@@ -1418,12 +1415,12 @@ acme.sh --issue --dns dns_ultra -d example.com -d www.example.com
 Sign up for dynDNS at https://desec.io first.
 
 Set your API token (password) by generating one from your account on desec.io (it's also a good idea to restrict the IPv4 / IPv6 address(es) it can be used from).
-```
+```sh
 export DEDYN_TOKEN=d41d8cd98f00b204e9800998ecf8427e
 ```
 To issue a certificate run:
-```
-acme.sh --issue --dns dns_desec -d foobar.dedyn.io -d *.foobar.dedyn.io
+```sh
+./acme.sh --issue --dns dns_desec -d foobar.dedyn.io -d *.foobar.dedyn.io
 ```
 
 If you find any bugs of deSEC.io  API, please report here: https://github.com/Neilpang/acme.sh/issues/2180
@@ -1433,11 +1430,11 @@ If you find any bugs of deSEC.io  API, please report here: https://github.com/Ne
 
 First, you need to enable API access and retrieve your password hash on https://rcp.openprovider.eu/account/dashboard.php
 
-```
+```sh
 export OPENPROVIDER_USER='username'
 export OPENPROVIDER_PASSWORDHASH='xxx'
 
-acme.sh --issue --dns dns_openprovider -d example.com -d www.example.com
+./acme.sh --issue --dns dns_openprovider -d example.com -d www.example.com
 ```
 
 `OPENPROVIDER_USER` and `OPENPROVIDER_PASSWORDHASH` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1450,7 +1447,7 @@ Make sure you've configured MaraDNS properly and setup a zone file for your doma
 
 Set the path to your zone file, and path to duende's pid file (see, [`duende(8)`](https://manpages.debian.org/stretch/duende/duende.8.en.html) or `ps -C duende o pid,cmd`).
 The pid file is used to ask duende to reload the configuration automatically after DNS records are added.
-```
+```sh
 export MARA_ZONE_FILE="/etc/maradns/db.domain.com"
 export MARA_DUENDE_PID_PATH="/run/maradns/etc_maradns_mararc.pid"
 ```
@@ -1458,8 +1455,8 @@ export MARA_DUENDE_PID_PATH="/run/maradns/etc_maradns_mararc.pid"
 Ensure that the acme.sh process has write access to the zone file and read access to the pid file.
 
 Issuing a certificate:
-```
-acme.sh --issue --dns dns_maradns -d example.com -d '*.example.com'
+```sh
+./acme.sh --issue --dns dns_maradns -d example.com -d '*.example.com'
 ```
 
 `MARA_ZONE_FILE` and `MARA_DUENDE_PID_PATH` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1474,15 +1471,15 @@ First create an account at https://ddnss.de. After that create a new host record
 In the defenition for the host make sure to set the checkbox for "Wildcard" and for "TXT".
 
 Note your Api Key (aka "Update Key") displayed at ddnss.de and export in DDNSS_Token variable
-```
+```sh
 export DDNSS_Token="e4155767few8erwf59353633tz342ce85werddc99432"
 ```
 **Note: Every Cert needs it own Update Key, if you already use the Update Key please generate a new one and export to DDNSS_Token before issue a new Cert. **
 
 
 After that you can issue a new certificate:
-```
-acme.sh --issue --dns dns_ddnss -d example.com
+```sh
+./acme.sh --issue --dns dns_ddnss -d example.com
 ```
 
 If you find any bugs of ddnss.de API, please report here: https://github.com/Neilpang/acme.sh/issues/2230
@@ -1490,22 +1487,22 @@ If you find any bugs of ddnss.de API, please report here: https://github.com/Nei
 ## 75. Use NLnetLabs NSD
 
 You need to export two variables. Your zonefile which the script will automatically edit:
-```
+```sh
 export Nsd_ZoneFile="/etc/nsd/zones/example.com.zone"
 ```
 And something that calls the nsd-control reload command, either via a script:
-```
+```sh
 export Nsd_Command="/usr/local/bin/sign-and-update.sh example.com"
 ```
 or directly:
-```
+```sh
 export Nsd_Command="sudo nsd-control reload example.com"
 ```
 The variables are saved per-domain, not per-account.
 
 To issue a new certificate, run:
-```
-acme.sh --issue --dns dns_nsd -d example.com -d *.example.com
+```sh
+./acme.sh --issue --dns dns_nsd -d example.com -d *.example.com
 ```
 
 If you find any bugs of NLnetLabs NSD dns API, please report here: https://github.com/Neilpang/acme.sh/issues/2245
@@ -1514,15 +1511,15 @@ If you find any bugs of NLnetLabs NSD dns API, please report here: https://githu
 
 [Schlundtech](https://www.schlundtech.de/) offers an [xml api](https://www.schlundtech.de/services/xml-gateway/)  with your standard login credentials, set them like so:
 
-```
+```sh
 export SCHLUNDTECH_USER="yourusername"
 export SCHLUNDTECH_PASSWORD="password"
 ```
 
 Then you can issue your certificates with:
 
-```
-acme.sh --issue --dns dns_schlundtech -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_schlundtech -d example.com -d www.example.com
 ```
 
 The `SCHLUNDTECH_USER` and `SCHLUNDTECH_PASSWORD` settings will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1531,14 +1528,14 @@ If you find any bugs of Schlundtech.de API, please report here: https://github.c
 
 ## 77. Use your one.com credentials as you would login into the control panel.
 
-```
+```sh
 export ONECOM_User="sdfsdfsdfljlbjkljlkjsdfoiwje"
 export ONECOM_Password="xxxx@sss.com"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_one -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_one -d example.com -d www.example.com
 ```
 
 Note:
@@ -1552,7 +1549,7 @@ But if you would like to use the build-in SSL (for your Web-Site etc.) from one.
 
 You can set "ONECOM_KeepCnameProxy" to keep the CNAME record.
 
-```
+```sh
 export ONECOM_KeepCnameProxy=1
 ```
 
@@ -1566,7 +1563,7 @@ If you find any bugs of one.com dns API, please report here: https://github.com/
 
 [Acmeproxy](https://github.com/mdbraber/acmeproxy/) can be used to as a single host in your network to request certificates through a DNS API. Clients can connect with one single host (the acmeproxy) so you don't need to store your DNS API credentials on every single host that wants to request a certificate.
 
-```
+```sh
 export ACMEPROXY_ENDPOINT="https://acmeproxy.yourhost.com:9096"
 export ACMEPROXY_USERNAME="username"
 export ACMEPROXY_PASSWORD="password"
@@ -1574,8 +1571,8 @@ export ACMEPROXY_PASSWORD="password"
 
 Then you can issue your certificates with:
 
-```
-acme.sh --issue --dns dns_acmeproxy -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_acmeproxy -d example.com -d www.example.com
 ```
 
 The `ACMEPROXY_ENDPOINT`, `ACMEPROXY_USERNAME` and `ACMEPROXY_PASSWORD` settings will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1587,14 +1584,14 @@ If you find any bugs of acmeproxy DNS API, please report here: https://github.co
 Create an API token in your internetbs.net account.
 
 Set your API token:
-```
+```sh
 export INTERNETBS_API_KEY="..."
 export INTERNETBS_API_PASSWORD="..."
 ```
 
 To issue a certificate run:
-```
-acme.sh --issue --dns dns_internetbs -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_internetbs -d example.com -d www.example.com
 ```
 
 The `INTERNETBS_API_KEY` and `INTERNETBS_API_PASSWORD` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1606,14 +1603,14 @@ If you find any bugs of internetbs.net API, please report here: https://github.c
 Create an API token in your durabledns.com account.
 
 Set your API token:
-```
+```sh
 export DD_API_User="..."
 export DD_API_Key="..."
 ```
 
 To issue a certificate run:
-```
-acme.sh --issue --dns dns_durabledns -d example.com -d '*.example.com'
+```sh
+./acme.sh --issue --dns dns_durabledns -d example.com -d '*.example.com'
 ```
 
 The `DD_API_User` and `DD_API_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1624,14 +1621,14 @@ If you find any bugs of durabledns.com API, please report here: https://github.c
 ## 81. Use reg.ru API
 
 Set your API credentials:
-```
+```sh
 export REGRU_API_Username='test'
 export REGRU_API_Password='test'
 ```
 
 To issue a certificate run:
-```
-acme.sh --issue --dns dns_regru -d 'example.com' -d '*.example.com'
+```sh
+./acme.sh --issue --dns dns_regru -d 'example.com' -d '*.example.com'
 ```
 
 The `REGRU_API_Username` and `REGRU_API_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1659,13 +1656,13 @@ response='{
 acme-v02.api.letsencrypt.org - `172.65.32.248` для получения SSL и api.reg.ru - `194.58.116.30` для тхт записи _acme-challenge
 
 Для авторизатции в API выполните:
-```
+```sh
 export REGRU_API_Username='водим свой логин для входа на REG.RU'
 export REGRU_API_Password='водим пароль каторый настроили в настройках API для авторизации'
 ```
 Для получения сертификата выполните:
-```
-acme.sh --issue --dns dns_regru -d 'example.com' -d '*.example.com'
+```sh
+./acme.sh --issue --dns dns_regru -d 'example.com' -d '*.example.com'
 ```
 Настройки для авторизации `REGRU_API_Username` и `REGRU_API_Password` будут сохранены в `~/.acme.sh/account.conf` и будут использоваться повторно при необходимости из конфига acme.
 
@@ -1684,7 +1681,7 @@ export VULTR_API_KEY="<Your API key>"
 To issue a cert:
 
 ```sh
-acme.sh --issue --dns dns_vultr -d example.com -d www.example.com
+./acme.sh --issue --dns dns_vultr -d example.com -d www.example.com
 ```
 
 The `VULTR_API_KEY` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1707,14 +1704,14 @@ export JD_ACCESS_KEY_SECRET="xxxxxxx"
 然后生成证书:
 
 ```sh
-acme.sh --issue --dns dns_jd  -d example.com -d www.example.com
+./acme.sh --issue --dns dns_jd  -d example.com -d www.example.com
 ```
 
 `JD_ACCESS_KEY_ID` 和 `JD_ACCESS_KEY_SECRET` 会自动保存在这里 `~/.acme.sh/account.conf`, 下次再生成证书时, 可以自动重用.
 
 高级选项:
 1. 默认使用的是 `cn-north-1` 区域. 目前不需要改动, 如果需要改的话, 再生成证书之前执行:
-```
+```sh
 export JD_REGION="cn-north-1" # 这里写你要改的区域
 ```
 
@@ -1749,7 +1746,7 @@ export Hexonet_Login='neilpang!testid'
 To issue a cert:
 
 ```sh
-acme.sh --issue --dns dns_hexonet  -d example.com -d www.example.com
+./acme.sh --issue --dns dns_hexonet  -d example.com -d www.example.com
 ```
 
 The `Hexonet_Login` and `Hexonet_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1763,14 +1760,14 @@ https://github.com/Neilpang/acme.sh/issues/2389
 
 You'll have to get a Domeneshop API key and secret (https://api.domeneshop.no/docs/).
 
-```
+```sh
 export DOMENESHOP_Token="1234567890"
 export DOMENESHOP_Secret="1234567890abcdefghijklmnopqrstuvw"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_domeneshop -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_domeneshop -d example.com -d www.example.com
 ```
 
 The `DOMENESHOP_Token` and `DOMENESHOP_Secret` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1786,7 +1783,7 @@ First you need to login to your OPNsense account and create an API Key for a use
 
 https://docs.opnsense.org/development/api.html
 
-```
+```sh
 export OPNs_Host="opnsense.example.com"
 export OPNs_Port="443"
 export OPNs_Key="qocfU9RSbt8vTIBcnW8bPqCrpfAHMDvj5OzadE7Str+rbjyCyk7u6yMrSCHtBXabgDDXx/dY0POUp7ZA"
@@ -1795,8 +1792,8 @@ export OPNs_Api_Insecure=0
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_opnsense -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_opnsense -d example.com -d www.example.com
 ```
 
 The `OPNs_Host`, `OPNs_Port`, `OPNs_Key`, `OPNs_Token` and `OPNs_Api_Insecure` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1811,23 +1808,23 @@ First you need to login to your RcodeZero account, enable the REST API and gener
 
 https://my.rcodezero.at/enableapi
 
-```
+```sh
 export RCODE0_API_TOKEN="acme_1232342342343OEH1G1gDcKNMsN7mx9EZgSU6AX79u5KRSxWnC"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_rcode0 -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_rcode0 -d example.com -d www.example.com
 ```
 
 The `RCODE0_API_TOKEN` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
 The RcodeZero API driver supports two addtional environment variables
-```
+```sh
 export RCODE0_URL=https://my.rcodezero.at
 ```
 Use a different RcodeZero API Endpoint (e.g. the RcodeZero Testsystem)
-```
+```sh
 export RCODE0_TTL=60
 ```
 Use a different TTL for the generated records
@@ -1840,15 +1837,15 @@ https://github.com/Neilpang/acme.sh/issues/2490
 
 Use the MailinaBox (MIAB) Custom DNS REST API interface to MIAB DNS. You only need to set your MIAB login credentials and the fully qualified domain name of the MIAB Server. Suggest single quote over double quote to ensure characters are not interpreted by the shell - important for passwords.
 
-```
+```sh
 export MIAB_Username='your_MIAB_admin_username'
 export MIAB_Password='your_MIAB_admin_password'
 export MIAB_Server='FQDN_of_your_MIAB_Server'
 ```
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_miab -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_miab -d example.com -d www.example.com
 ```
 
 The `MIAB_Username`, `MIAB_Password` and `MIAB_Server` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1879,7 +1876,7 @@ export NIC_ClientSecret='xxxxxxxx'
 
 To issue a cert:
 ```bash
-acme.sh --issue --dns dns_nic -d domain.com -d www.domain.com
+./acme.sh --issue --dns dns_nic -d domain.com -d www.domain.com
 ```
 The NIC_Username, NIC_Password, NIC_ClientID and NIC_ClientSecret will be saved in ~/.acme.sh/account.conf and will be reused when needed.
 
@@ -1895,13 +1892,13 @@ Docs:
 
 First you need to login to your Leaseweb account to get your API Key.
 
-```
+```sh
 export LSW_Key="safas-3fs3sd-34sdf-safss"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_leaseweb -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_leaseweb -d example.com -d www.example.com
 ```
 
 The `LSW_Key` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1913,13 +1910,13 @@ If you find any bugs, please report here: https://github.com/Neilpang/acme.sh/is
 
 First you need to obtain your API Key from variomedia's customer support.
 
-```
+```sh
 export VARIOMEDIA_API_TOKEN="sdfsdfsdfljlbjkljlkjsdfoiwjesdfsdfsdfljlbjkljlkjsdfoiwje"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_variomedia -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_variomedia -d example.com -d www.example.com
 ```
 
 The `VARIOMEDIA_API_TOKEN` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -1937,15 +1934,15 @@ https://address-of-my-plesk-server.net:8443/enterprise/control/agent.php
 
 All commands are CASE SENSITIVE:
 
-```
+```sh
 export pleskxml_uri="address of my Plesk server's API"
 export pleskxml_user="my plesk username"
 export pleskxml_pass="my plesk password"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_pleskxml -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_pleskxml -d example.com -d www.example.com
 ```
 
 The `pleskxml_uri`, `pleskxml_user` and `pleskxml_pass` will be saved in `~/.acme.sh/account.conf` and reused when needed.
@@ -1958,7 +1955,7 @@ If you find any bugs, please report here: https://github.com/Neilpang/acme.sh/is
 
 This script uses PDNS Manager API and its "[Update via GET request](https://pdnsmanager.org/documentation/api/)" method. So only single record update possible and no wildcards, for now.
 
-```
+```sh
 export PDNS_MANAGER_URL=https://mypdnsmanagerurl.nx
 export PDNS_MANAGER_RECORDID=<record id>
 export PDNS_MANAGER_PASSWORD=<record password>
@@ -1969,35 +1966,35 @@ export PDNS_MANAGER_PASSWORD=<record password>
 
 Then issue a new certificate:
 
-```
-acme.sh --issue -d example.com --dns dns_pdnsmanager
+```sh
+./acme.sh --issue -d example.com --dns dns_pdnsmanager
 ```
 
 ## 94. Use Misaka.io domain API
 
 Get your API token at https://console.misaka.io/settings
 
-```
+```sh
 export Misaka_Key="sdfsdfsdfljlbjkljlkjsdfoiwje"
 ```
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_misaka -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_misaka -d example.com -d www.example.com
 ```
 
 ## 95. Use easyDNS.net API to automatically issue a cert
 You need to sign up for beta API access [here](http://docs.sandbox.rest.easydns.net/beta_signup.php).
 Docs: http://sandbox.rest.easydns.net:3000/
 
-```
+```sh
 export EASYDNS_Key="xxxxxxxxxxxxxxxxx.xxxxxxxx"
 export EASYDNS_Token="xxxxxxxxxxxxxxx.xxxxxxxx"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_easydns -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_easydns -d example.com -d www.example.com
 ```
 The `EASYDNS_Key` and `EASYDNS_Token` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
@@ -2008,15 +2005,15 @@ https://github.com/Neilpang/acme.sh/issues/2647
 ## 96. Use CloudDNS API to automatically issue a cert
 Docs: https://github.com/vshosting/clouddns
 
-```
+```sh
 export CLOUDDNS_EMAIL="email@example.com"
 export CLOUDDNS_PASSWORD="xxxxxxxx"
 export CLOUDDNS_CLIENT_ID="xxxxxxxxxxxxxxxxxxxx"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_clouddns -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_clouddns -d example.com -d www.example.com
 ```
 The `CLOUDDNS_EMAIL`, `CLOUDDNS_PASSWORD` and `CLOUDDNS_CLIENT_ID` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
@@ -2032,8 +2029,8 @@ Alternatively you can use the [HTTP REST API](https://dynv6.github.io/api-spec/)
 If both a SSH Key and a HTTP Token are specified the REST API will be used.
 
 To issue a cert use:
-```
-acme.sh --issue --dns dns_dynv6 -d www.example.dynv6.net
+```sh
+./acme.sh --issue --dns dns_dynv6 -d www.example.dynv6.net
 ```
 If you find any bugs, please report here:  
 https://github.com/acmesh-official/acme.sh/issues/2702
@@ -2041,14 +2038,14 @@ https://github.com/acmesh-official/acme.sh/issues/2702
 ## 98. Use All-Inkl.com domain API to automatically issue cert
 
 You need your login credentials for All-Inkl (https://kas.all-inkl.com).
-```
+```sh
 export KAS_Login="....."
 export KAS_Authtype="sha1"
 export KAS_Authdata="....."
 ```
 Now you are able to issue a cert:
-```
-acme.sh --issue --dns dns_kas -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_kas -d example.com -d www.example.com
 ```
 The `KAS_Login`, `KAS_Authtype` and `KAS_Authdata` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
@@ -2056,14 +2053,14 @@ The `KAS_Login`, `KAS_Authtype` and `KAS_Authdata` will be saved in `~/.acme.sh/
 
 Get your API credentials at https://manage.constellix.com/users
 
-```
+```sh
 export CONSTELLIX_Key="XXX"
 export CONSTELLIX_Secret="XXX"
 ```
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_constellix -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_constellix -d example.com -d www.example.com
 ```
 
 The `CONSTELLIX_Key` and `CONSTELLIX_Secret` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -2072,14 +2069,14 @@ The `CONSTELLIX_Key` and `CONSTELLIX_Secret` will be saved in `~/.acme.sh/accoun
 
 Get your API credentials at https://namemaster.de DNS/API 
 
-```
+```sh
 export NM_user="XXX"
 export NM_sha256="XXX"
 ```
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_nm -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_nm -d example.com -d www.example.com
 ```
 
 The `NM_user` and `NM_sha256` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -2096,11 +2093,11 @@ HostingUkraine_Token="XXX"
 ```
 
 To issue a cert:
-```
+```sh
 ./acme.sh --issue --dns dns_hostingukraine -d yourdomain.com -d www.yourdomain.com
 ```
 To issue a wildcard cert: 
-```
+```sh
 ./acme.sh --issue --dns dns_hostingukraine -d yourdomain.com -d '*.yourdomain.com' 
 ```
 
@@ -2110,13 +2107,13 @@ The `HostingUkraine_Login` and `HostingUkraine_Token` will be saved in `~/.acme.
 
 Get your API token at https://npanel.arvancloud.com/profile/api-keys
 
-```
+```sh
 export Arvan_Token="fsdasdfsdfljlbjkljlkjsdfoiwje"
 ```
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_arvan -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_arvan -d example.com -d www.example.com
 ```
 
 The `Arvan_Token` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -2130,14 +2127,14 @@ You must activate Dynamic DNS in Joker.com DNS configuration first. Username and
 
 Report bugs to https://github.com/acmesh-official/acme.sh/issues/2840
 
-```
+```sh
 export JOKER_USERNAME="xxxx"
 export JOKER_PASSWORD="xxxx"
 ```
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_joker -d example.com
+```sh
+./acme.sh --issue --dns dns_joker -d example.com
 ```
 
 The `JOKER_USERNAME`  and `JOKER_PASSWORD` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -2164,7 +2161,7 @@ in `~/.acme.sh/account.conf` and reuses it when needed.
 Ok, let's issue a cert now:
 
 ```sh
-acme.sh --issue --dns dns_1984hosting -d example.com -d *.example.com
+./acme.sh --issue --dns dns_1984hosting -d example.com -d *.example.com
 ```
 
 If you have any issues with 1984Hosting DNS API please report them [here](https://github.com/Neilpang/acme.sh/issues/2851).
@@ -2172,14 +2169,14 @@ If you have any issues with 1984Hosting DNS API please report them [here](https:
 ## 105. Use Aruba domain API
 
 Get your api token following instruction here at https://admin.arubabusiness.it/DashBoard/WebApiGuide.aspx
-```
+```sh
 export ARUBA_TK="sdfsdfsdfljlbjkljlkjsdfoiwje" #ARUBA API Token
 export ARUBA_AK="xxxxxxxxxxxxx" #ARUBA Username
 export ARUBA_AS="xxxxxxxxxxxxx" #ARUBA Password
 ```
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_aruba -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_aruba -d example.com -d www.example.com
 ```
 
 If you find any bugs, please report here:
@@ -2189,7 +2186,7 @@ https://github.com/JTrotta/acme.sh/issues
 ## 106. Use TransIP domain API:
 
 First you need to login to your TransIP account to get your [private key](https://www.transip.nl/cp/account/api/).
-```
+```sh
 export TRANSIP_Username="MyUserName"
 export TRANSIP_Key_File="private_key"
 ```
@@ -2213,33 +2210,33 @@ you can add this trusted root CA with
 This script will create a new access token with a default lifetime of 30 minutes. Note that these tokens are by default IP-whitelisted and will not work if your IP is not whitelisted in the Transip control panel.
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_transip --dnssleep 300 -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_transip --dnssleep 300 -d example.com -d www.example.com
 ```
 
 ## 107. Use dyndnsfree.de API
 
-```
+```sh
 export df_user="XXX"
 export df_password="XXX"
 ```
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_df -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_df -d example.com -d www.example.com
 ```
 
 The `df_user` and `df_password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
 ## 108. Use Njalla API
 
-```
+```sh
 export NJALLA_Token="XXX"
 ```
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_njalla -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_njalla -d example.com -d www.example.com
 ```
 
 Please report any bugs here: https://github.com/acmesh-official/acme.sh/issues/2913
@@ -2249,13 +2246,13 @@ Please report any bugs here: https://github.com/acmesh-official/acme.sh/issues/2
 
 Obtain an account token from https://vercel.com/account/tokens.
 
-```
+```sh
 export VERCEL_TOKEN="sdfsdfsdfljlbjkljlkjsdfoiwje"
 ```
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_vercel -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_vercel -d example.com -d www.example.com
 ```
 
 
@@ -2269,7 +2266,7 @@ export HETZNER_Token="somelongrandomstring"
 
 Ok, let's issue a cert now:
 ```sh
-acme.sh --issue --dns dns_hetzner -d example.com -d www.example.com
+./acme.sh --issue --dns dns_hetzner -d example.com -d www.example.com
 ```
 
 The `HETZNER_Token` settings will be saved in `[acme.sh-config-home-path]/account.conf`
@@ -2285,19 +2282,19 @@ in order to avoid multiple `get_zone_id` requests two months later.
 Contact kapper.net support via support@kapper.net to get your kapper.net DNS Panel API Key and Secret.
 
 For initialzation call following in commandline
-```
+```sh
 export KAPPERNETDNS_Key="yourKAPPERNETapikey"
 export KAPPERNETDNS_Secret="yourKAPPERNETapisecret"
 ```
 
 You can start the acme.sh with following parameters for testing
 
-```
-acme.sh --issue --dns dns_kappernet -d <example.com> 
+```sh
+./acme.sh --issue --dns dns_kappernet -d <example.com> 
 
 or for a wildcertificate
 
-acme.sh --issue --dns dns_kappernet -d <example.com> -d *.<example.com> 
+./acme.sh --issue --dns dns_kappernet -d <example.com> -d *.<example.com> 
 
 ```
 Please replace "<example.com>" with the name of the domain you wish to create a certificate for.
@@ -2305,8 +2302,8 @@ Please replace "<example.com>" with the name of the domain you wish to create a
 After the test you can replace your kapper.net DNS Panel API Key and Secret, it is stored in ~/.acme.sh/account.conf.
 
 For repeated calls use
-```
-acme.sh --issue --dns dns_kappernet -d <example.com>
+```sh
+./acme.sh --issue --dns dns_kappernet -d <example.com>
 ```
 
 ## 112. Use Wedos API
@@ -2315,7 +2312,7 @@ First create your WAPI password and add your IP address to access list at custom
 
 Set variables:
 
-```
+```sh
 export WEDOS_User='xxx@xxx.xx'
 export WEDOS_Pass='xxx123'
 or use sha1 hash of WEDOS_Pass directly
@@ -2323,8 +2320,8 @@ export WEDOS_Hash='xxxxxxxxxx'
 ```
 
 Issue your certs:
-```
-acme.sh --issue --dns dns_wedos -d xxx.xx -d www.xxx.xx
+```sh
+./acme.sh --issue --dns dns_wedos -d xxx.xx -d www.xxx.xx
 ```
 
 WEDOS_User and WEDOS_Hash will be stored in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -2336,22 +2333,22 @@ Shellrent API offers one method to automatically issue certs.
 First you need to login to your Shellrent account to get your API key.
 In order to use the token, you need to authorize your IP to have access to it.
 More Info on https://api.shellrent.com and https://guide.shellrent.com
-```
+```sh
 export SH_Username="usrXXXX"
 export SH_Token="sdfsdfsdfljlbjkljlkjsdfoiwje"
 ```
 
 Alternatively, if the certificate only covers a single zone, you can speed up the process by specify the SH_Domain_ID directly:
 
-```
+```sh
 export SH_Username="usrXXXX"
 export SH_Token="sdfsdfsdfljlbjkljlkjsdfoiwje"
 export SH_Domain_ID="xxxxxxxxxxxxx"
 ```
 Let's issue a cert now:
 
-```
-acme.sh --issue --dns dns_shellrent -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_shellrent -d example.com -d www.example.com
 ```
 The SH_Username and SH_Token and SH_Domain_ID will be saved in ~/.acme.sh/account.conf and will be reused when needed.
 
@@ -2375,7 +2372,7 @@ You will most likely want to source your OpenStack RC file to set your environme
 . openrc.sh
 ```
 or manually like:
-```
+```sh
 export OS_AUTH_URL=https://keystone.example.com:5000/
 export OS_USERNAME=<username>
 export OS_PASSWORD=<password>
@@ -2385,8 +2382,8 @@ export OS_USER_DOMAIN_NAME=Default
 ```
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_openstack -d example.com
+```sh
+./acme.sh --issue --dns dns_openstack -d example.com
 ```
 
 Your OpenStack credentials will be saved to `~/.acme.sh/account.conf` and reused on renewal.
@@ -2397,14 +2394,14 @@ Your OpenStack credentials will be saved to `~/.acme.sh/account.conf` and reused
 
 2. Set your token for use with
 
-```
+```sh
 export NETLIFY_ACCESS_TOKEN='arstdhneioqwfpgjluyzxcvbkm'
 ```
 
 3.  Issue a cert with:
 
-```
-acme.sh --issue --dns dns_netlify -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_netlify -d example.com -d www.example.com
 ```
 
 [Report a Netlify-related Bug](https://github.com/acmesh-official/acme.sh/issues/3088)
@@ -2418,7 +2415,7 @@ Report any issues to https://github.com/acmesh-official/acme.sh/issues/3157
 This provider requires Akamai Open Edgegrid Credentials with EdgeDNS API access authorization. To create and establish your Akamai OPEN CREDENTIALS, see the [authorization](https://developer.akamai.com/legacy/introduction/Prov_Creds.html) and [credentials](https://developer.akamai.com/legacy/introduction/Conf_Client.html) sections of the Akamai Developer Get Started guide.
 
 The Akamai Open Edgegrid credentials must be specified as environment variables as follows:
-```
+```sh
 export AKAMAI_CLIENT_TOKEN=<akamai edgegrid client token>
 export AKAMAI_ACCESS_TOKEN=<akamai edgegrid access token>
 export AKAMAI_CLIENT_SECRET=<akamai edgegrid client secret>
@@ -2426,8 +2423,8 @@ export AKAMAI_HOST=<akamai edgegrid api host>
 ```
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_edgedns -d example.com
+```sh
+./acme.sh --issue --dns dns_edgedns -d example.com
 ```
 
 Your Akamai Edgegrid credentials will be saved to `~/.acme.sh/account.conf` and reused on renewal.
@@ -2436,14 +2433,14 @@ Your Akamai Edgegrid credentials will be saved to `~/.acme.sh/account.conf` and
 WEDOS DNS provider comes from Czech Republic. DNS API implementation for WEDOS require your WEDOS's account to allow WAPI interface. You have to login to WEDOS administration, in setting allow WAPI interface (in days when this manual were written it was for free completelly). Configure WAPI interface to XML interface and register the IP addresses (IPv4 and IPv6) of the server where you plan to use acme.sh. That is from the manual side.
 
 By doing this setting you should have WEDOS web account username and configured WAPI password. This must be configured to your acme.sh account in the first execution of acme.sh script. To save it to `~/.acme.sh/account.conf` (and for subsequent acme.sh executions) just execute following before first execution of acme.sh script.
-```
+```sh
 export WEDOS_Username=<your user name to login to wedos web account>
 export WEDOS_Wapipass=<your WAPI passwords you setup using wedos web pages>
 ```
 
 Then you can issue a certificates:
-```
-acme.sh --issue --dns dns_wedos -d "*.example.com" -d "examle.com"
+```sh
+./acme.sh --issue --dns dns_wedos -d "*.example.com" -d "examle.com"
 ```
 
 If you face any bug, please use this [page](https://github.com/acmesh-official/acme.sh/issues/3166) to report it. But before reporting run the acme.sh with `--debug 2` switch and append full acme.sh output to the issue report. 
@@ -2452,14 +2449,14 @@ Enjoy it.
 
 ## 118. Use Websupport DNS API
 Obtain an api key and secret from https://admin.websupport.sk/en/auth/apiKey
-```
+```sh
 export WS_ApiKey="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
 export WS_ApiSecret="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
 ```
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_websupport -d "*.example.com" -d "examle.com"
+```sh
+./acme.sh --issue --dns dns_websupport -d "*.example.com" -d "examle.com"
 ```
 
 Report any issues to https://github.com/akulumbeg/acme.sh/issues
@@ -2471,9 +2468,9 @@ Create a token with Domain scope in the API dashboard at
 https://manager.infomaniak.com/v3/<account_id>/api/dashboard
 and export it as an environment variable:
 
-```
+```sh
 export INFOMANIAK_API_TOKEN=xxx
-acme.sh --issue --dns dns_infomaniak -d example.com -d www.example.com
+./acme.sh --issue --dns dns_infomaniak -d example.com -d www.example.com
 ```
 
 Please report any issue to https://github.com/acmesh-official/acme.sh/issues/3188
@@ -2484,10 +2481,10 @@ Bookmyname hosts domains and has a small API.
 
 Export your login/pass as an environment variable:
 
-```
+```sh
 export BOOKMYNAME_USERNAME=xxx
 export BOOKMYNAME_PASSWORD=yyy
-acme.sh --issue --dns dns_bookmyname --dnssleep 600 -d example.com -d www.example.com
+./acme.sh --issue --dns dns_bookmyname --dnssleep 600 -d example.com -d www.example.com
 ```
 
 Please report any issue to https://github.com/acmesh-official/acme.sh/issues/3209
@@ -2498,9 +2495,9 @@ For DNS records managed via https://engine.anexia-it.com/clouddns
 
 Export your token as an environment variable:
 
-```
+```sh
 export ANX_Token='XXXXXXXXXXXXXXXXXXX'
-acme.sh --issue --dns dns_anx -d example.com -d www.example.com
+./acme.sh --issue --dns dns_anx -d example.com -d www.example.com
 ```
 Please report any issue to https://github.com/acmesh-official/acme.sh/issues/3238
 
@@ -2508,11 +2505,13 @@ Please report any issue to https://github.com/acmesh-official/acme.sh/issues/323
 Note that in order the script to be working properly acme.sh should be installed on Synology itself.
 
 To issue a cert:
-
-    ./acme.sh --issue --dns dns_synology_dsm -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_synology_dsm -d example.com -d www.example.com
+```
 To issue a wildcard cert:
-
-    ./acme.sh --issue --dns dns_synology_dsm -d example.com -d *.example.com
+```
+./acme.sh --issue --dns dns_synology_dsm -d example.com -d *.example.com
+```
 You can find more details [here](https://github.com/arabezar/acme.sh/wiki)
 
 Please report any issue [here](https://github.com/acmesh-official/acme.sh/issues/3248)
@@ -2523,52 +2522,52 @@ Export your credentials as an environment variable:
 ProjectID can be found at [here](https://console-intl.huaweicloud.com/iam/?region=ap-southeast-1#/myCredential)
 It seems that project ID can be retrieved automatically, but this dnsapi does not implement it yet.
 
-```
+```sh
 export HUAWEICLOUD_Username=<Your Username> # Usually hwxxxxxx
 export HUAWEICLOUD_Password=<Your Password>
 export HUAWEICLOUD_ProjectID=<A Project ID> 
 ```
 
 To issue a cert:
-```
+```sh
 ./acme.sh --issue --dns dns_huaweicloud -d example.com -d www.example.com
 ```
 To issue a wildcard cert:
-```
+```sh
 ./acme.sh --issue --dns dns_huaweicloud -d example.com -d *.example.com
 ```
 
 ## 124. Use Simply API
 Export your credentials, you will find your API key by logging in to your Simply.com account:
 
-```
+```sh
 export SIMPLY_AccountName=<Your accountname>
 export SIMPLY_ApiKey=<Your API-key>
 ```
 
 To issue a cert:
-```
+```sh
 ./acme.sh --issue --dns dns_simply -d example.com -d www.example.com
 ```
 To issue a wildcard cert:
-```
+```sh
 ./acme.sh --issue --dns dns_simply -d example.com -d *.example.com
 ```
 
 ## 125. Use World4You API
 Export your credentials as an environment variable:
 
-```
+```sh
 export WORLD4YOU_USERNAME=<customer-id>
 export WORLD4YOU_PASSWORD=<password>
 ```
 
 To issue a cert:
-```
+```sh
 ./acme.sh --issue --dns dns_world4you -d example.com -d www.example.com
 ```
 To issue a wildcard cert:
-```
+```sh
 ./acme.sh --issue --dns dns_world4you -d example.com -d *.example.com
 ```
 
@@ -2576,42 +2575,42 @@ To issue a wildcard cert:
 
 First, you'll need to retrieve your [Api Key](https://www.scaleway.com/en/docs/generate-api-keys/)
 
-```
+```sh
 export SCALEWAY_API_TOKEN='xxx'
 ```
 
 To issue a cert run:
 
-```
-acme.sh --issue --dns dns_scaleway -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_scaleway -d example.com -d www.example.com
 ```
 
 Please report any issue [here](https://github.com/acmesh-official/acme.sh/issues/3295)
 
 ## 127 First you need to login to your LS account to get your API Key.
 
-```
+```sh
 export LS_Key="KEY"
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_ls -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_ls -d example.com -d www.example.com
 ```
 
 ## 128. Use RackCorp API
 Export your credentials as an environment variable:
-```
+```sh
 export RACKCORP_APIUUID="UUIDHERE"
 export RACKCORP_APISECRET="SECRETHERE"
 ```
 To issue a cert:
-```
-acme.sh --issue --dns dns_rackcorp -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_rackcorp -d example.com -d www.example.com
 ```
 To issue a wildcard cert:
-```
-acme.sh --issue --dns dns_rackcorp -d example.com -d *.example.com
+```sh
+./acme.sh --issue --dns dns_rackcorp -d example.com -d *.example.com
 ```
 
 ## 129. Using the IONOS domain API
@@ -2619,19 +2618,19 @@ acme.sh --issue --dns dns_rackcorp -d example.com -d *.example.com
 Read [Getting Started](https://developer.hosting.ionos.de/docs/getstarted) to learn how to create an API key.
 Export your credentials as environment variables:
 
-```
+```sh
 export IONOS_PREFIX="..."
 export IONOS_SECRET="..."
 ```
 
 To issue a certificate, execute:
-```
-acme.sh --issue --dns dns_ionos -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_ionos -d example.com -d www.example.com
 ```
 
 To issue a wildcard certificate, execute:
-```
-acme.sh --issue --dns dns_ionos -d example.com -d *.example.com
+```sh
+./acme.sh --issue --dns dns_ionos -d example.com -d *.example.com
 ```
 
 ## 130. Using the Porkbun API
@@ -2639,19 +2638,19 @@ acme.sh --issue --dns dns_ionos -d example.com -d *.example.com
 Read [Getting Started](https://porkbun.com/api/json/v3/documentation) to learn how to create an API key.
 Export your credentials as environment variables:
 
-```
+```sh
 export PORKBUN_API_KEY="..."
 export PORKBUN_SECRET_API_KEY="..."
 ```
 
 To issue a certificate, execute:
-```
-acme.sh --issue --dns dns_porkbun -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_porkbun -d example.com -d www.example.com
 ```
 
 To issue a wildcard certificate, execute:
-```
-acme.sh --issue --dns dns_porkbun -d example.com -d *.example.com
+```sh
+./acme.sh --issue --dns dns_porkbun -d example.com -d *.example.com
 ```
 
 ## 131. Using the Aurora API
@@ -2659,14 +2658,14 @@ acme.sh --issue --dns dns_porkbun -d example.com -d *.example.com
 [PCextreme B.V.](https://www.pcextreme.nl/) is a Dutch cloud provider offering cloud services under the family name Aurora. Head over to [DNS & Health Checks > Users](https://cp.pcextreme.nl/auroradns/users) to get your API credentials.
 Export your credentials as environment variables:
 
-```
+```sh
 export AURORA_Key="..."
 export AURORA_Secret="..."
 ```
 
 To issue a certificate, execute:
-```
-acme.sh --issue --dns dns_aurora -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_aurora -d example.com -d www.example.com
 ```
 
 Please report any issue to https://github.com/acmesh-official/acme.sh/issues/3459
@@ -2676,14 +2675,14 @@ Please report any issue to https://github.com/acmesh-official/acme.sh/issues/345
 [Azion](https://www.azion.com/) is a Edge Computing Platform to build modern applications at edge. This API reflects the [Intelligent DNS](https://www.azion.com/en/documentation/products/intelligent-dns/) product. Read this [documentation](https://www.azion.com/en/documentation/products/api/v3/) to create an username/password and permissions to use this plugin.
 
 Export your username/password as environment variables:
-```
+```sh
 export AZION_Email="user@example.com"
 export AZION_Password="password"
 ```
 
 To issue a certificate, execute:
-```
-acme.sh --issue --dns dns_azion -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_azion -d example.com -d www.example.com
 ```
 
 Please report any issue to https://github.com/acmesh-official/acme.sh/issues/3555
@@ -2697,17 +2696,17 @@ See: <https://github.com/acmesh-official/acme.sh/wiki/Using-Oracle-Cloud-Infrast
 Créer un token API sur votre compte [Hostline Hébergement VPS](https://www.hostline.fr).
 
 Ajouter les variables API suivantes :
-```
+```sh
 export HOSTLINE_Token="xxx" (obligatoire)
 export HOSTLINE_Url="https://api.hostline.fr" (optionnel)
 export HOSTLINE_Ttl="60" ttl custom record (optionnel)
 ```
 
 Pour générer un certificat exécuter la commande correspondante à votre cas :
-```
-acme.sh --issue --dns dns_hostline -d www.example.com # simple domain
-acme.sh --issue --dns dns_hostline -d example.com -d www.example.com # multi domain
-acme.sh --issue --dns dns_hostline -d example.com -d *.example.com # wildcard
+```sh
+./acme.sh --issue --dns dns_hostline -d www.example.com # simple domain
+./acme.sh --issue --dns dns_hostline -d example.com -d www.example.com # multi domain
+./acme.sh --issue --dns dns_hostline -d example.com -d *.example.com # wildcard
 ```
 
 Les variables `HOSTLINE_Token`, `HOSTLINE_Url` (optionnel) et `HOSTLINE_Ttl` (optionnel) doivent être définies dans le fichier `/root/.acme.sh/account.conf`.
@@ -2719,14 +2718,14 @@ Si vous rencontrez un problème sur l'API Hostline Hébergement VPS, merci de ra
 
 [Veesp](https://veesp.com/) offers HTTP REST [API](https://secure.veesp.com/userapi#dns-82) to manage vital details of account and services like DNS. Your standard login credentials is needed:
 
-```
+```sh
 export VEESP_User="username@domain.com"
 export VEESP_Password="password"
 ```
 
 To issue a cert:
-```
-acme.sh --issue --dns dns_veesp -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_veesp -d example.com -d www.example.com
 ```
 
 The `VEESP_User` and `VEESP_Password` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -2738,22 +2737,22 @@ Please report any issue to [https://github.com/acmesh-official/acme.sh/issues/37
 First you need to log into the cPanel interface and generate an API key for your account (under Security -> Manage API Tokens).
 Then set your username, api token and hostname:
 
-```
+```sh
 export cPanel_Username=username
 export cPanel_Apitoken=apitoken
 export cPanel_Hostname=https://hostname:port
 ```
 example
 
-```
+```sh
 export cPanel_Username=myadminuseratnordicway
 export cPanel_Apitoken=CXJ8HRXFNS363RQ71Z51TKM9KTHRFZVE
 export cPanel_Hostname=https://cp04.nordicway.dk:2083
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_cpanel -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_cpanel -d example.com -d www.example.com
 ```
 
 (see https://api.docs.cpanel.net/cpanel/introduction/#cpanel-or-webmail-session-url-1 regarding cPanel ports)
@@ -2779,21 +2778,21 @@ The `ISPMan_Username` and `ISPMan_Password` will be saved in `$LE_WORKING_DIR/ac
 Ok, let's issue a cert:
 
 ```sh
-acme.sh --issue --dns dns_ispman -d example.com -d *.example.com
+./acme.sh --issue --dns dns_ispman -d example.com -d *.example.com
 ```
 
 Please report bugs to [https://github.com/acmesh-official/acme.sh/issues/3751](https://github.com/acmesh-official/acme.sh/issues/3751)
 
 ## 138. Use dnsHome.de DNS API
 
-```
+```sh
 export DNSHOME_Subdomain=""
 export DNSHOME_SubdomainPassword=""
 ```
 
 Ok, let's issue a cert now:
-```
-acme.sh --issue --dns dns_dnshome -d subdomain.ddnsdomain.tld
+```sh
+./acme.sh --issue --dns dns_dnshome -d subdomain.ddnsdomain.tld
 ```
 
 The `DNSHOME_Subdomain` and `DNSHOME_SubdomainPassword` will be saved in the domain conf and will be reused when needed.
@@ -2811,7 +2810,7 @@ export MB_AS="Secret"
 
 Ok, let's issue a cert now:
 ```sh
-acme.sh --issue --dns dns_mythic_beasts --domain example.com
+./acme.sh --issue --dns dns_mythic_beasts --domain example.com
 ```
 
 The credentials will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -2829,13 +2828,13 @@ export SDNS_ZONE_KEY="Key"
 
 Ok, let's issue a cert now:
 ```sh
-acme.sh --issue --dns dns_sdns --domain example.com
+./acme.sh --issue --dns dns_sdns --domain example.com
 ```
 
 S-dns nameservers use anycast. It is therefore possible that the server next to your location already provides the new record, while the CA reaches another one that does not have the TXT record yet. To avoid such timing errors the dnssleep flag can be set to a value of 240 seconds.
 
 ```sh
-acme.sh --issue --dns dns_sdns --domain example.com --dnssleep 240
+./acme.sh --issue --dns dns_sdns --domain example.com --dnssleep 240
 ```
 
 ## 141. Using the united-domains reselling DNS API
@@ -2851,12 +2850,12 @@ export UDR_PASS="..."
 
 To issue a certificate, execute:
 ```sh
-acme.sh --issue --dns dns_udr -d example.com -d www.example.com
+./acme.sh --issue --dns dns_udr -d example.com -d www.example.com
 ```
 
 To issue a wildcard certificate, execute:
 ```sh
-acme.sh --issue --dns dns_udr -d example.com -d *.example.com
+./acme.sh --issue --dns dns_udr -d example.com -d *.example.com
 ```
 
 The `UDR_USER` and `UDR_PASS` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
@@ -2872,16 +2871,42 @@ export CURANET_AUTHSECRET="..."
 
 To issue a certificate, execute:
 ```sh
-acme.sh --issue --dns dns_curanet -d example.com -d www.example.com
+./acme.sh --issue --dns dns_curanet -d example.com -d www.example.com
 ```
 
 To issue a wildcard certificate, execute:
 ```sh
-acme.sh --issue --dns dns_curanet -d example.com -d *.example.com
+./acme.sh --issue --dns dns_curanet -d example.com -d *.example.com
 ```
 
 The `CURANET_AUTHCLIENTID` and `CURANET_AUTHSECRET` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
 
+## 143. Use ArtFiles.de DNS API
+
+First, verify that API access is already enabled:
+1. Go to ArtFiles.de's **DCP** (Domain Control Panel).
+2. Click **Passwords** in the left menu.
+3. To the menu's right, the drop-down menu for **Active** is either `active` or `inactive`.
+4. If **Active** is already set to `active`, skip this step. Otherwise, enter your desired password into both text boxes, save it somewhere else (e. g. Firefox, KeePass, etc.) & click **Apply** below.
+5. Copy **User name**'s value, i. e. the one that starts with `api` & then continues with your account number which is something like `a12345678`.
+
+Export `AF_API_Username` & `AF_API_Password` only once (saved into domain's config file upon 1st successful script run):
+```sh
+export AF_API_Username="api12345678"
+export AF_API_Password="apiPassword"
+```
+
+To issue a certificate, execute:
+```sh
+./acme.sh --issue --dns dns_artfiles -d yourDomain.tld
+```
+To issue a wildcard certificate, execute:
+```sh
+./acme.sh --issue --dns dns_artfiles -d yourDomain.tld -d *.yourDomain.tld
+```
+
+Please report any issue at [Eagle3386/acme.sh/issues](https://github.com/Eagle3386/acme.sh/issues).
+
 # ##################
 # Use custom API
 
@@ -2893,8 +2918,8 @@ Let's assume you want to name it 'myapi':
 2. In the script you must have a function named `dns_myapi_add()` which will be called by acme.sh to add the DNS records.
 3. Then you can use your API to issue cert like this:
 
-```
-acme.sh --issue --dns dns_myapi -d example.com -d www.example.com
+```sh
+./acme.sh --issue --dns dns_myapi -d example.com -d www.example.com
 ```
 
 For more details, please check our sample script: [dns_myapi.sh](https://github.com/Neilpang/acme.sh/blob/master/dnsapi/dns_myapi.sh)