diff --git a/README.md b/README.md
index 9c9fbc6..8238db6 100644
--- a/README.md
+++ b/README.md
@@ -147,7 +147,7 @@ Get the Vault command-line client via [vaultproject.io/downloads](https://www.va
     Log in to Vault with `userpass` and the `zabbix` account from above, get the account's token and lastly double-check that `zabbix` with its token can read a secret:
     ```
     curl --silent --location --header 'X-Vault-Token: <token>' \
-        'https://fully.qualified.domain.name/v1/kv/data/for_rbacgroup_zabbix/some/secret' \
+        'https://f.q.d.n/v1/kv/data/for_rbacgroup_zabbix/some/secret' \
         | jq '.data.data'
     ```
 
@@ -157,7 +157,7 @@ Get the Vault command-line client via [vaultproject.io/downloads](https://www.va
     ```
     # Look up a token's own attributes
     curl --silent --location --header 'X-Vault-Token: <token>' \
-        'https://fully.qualified.domain.name/v1/auth/token/lookup-self' \
+        'https://f.q.d.n/v1/auth/token/lookup-self' \
         | jq '.data.ttl'
 
     # .data.ttl will show remaining validity in secs:
@@ -168,7 +168,7 @@ Get the Vault command-line client via [vaultproject.io/downloads](https://www.va
 
     Their `list` permission only begins one lever deeper at `kv/list/for_rbacgroup_zabbix`. It may make sense to communicate an entrypoint link to end users that - in this case - will look like:
     ```
-    https://fully.qualified.domain.name/ui/vault/secrets/kv/list/for_rbacgroup_zabbix
+    https://f.q.d.n/ui/vault/secrets/kv/list/for_rbacgroup_zabbix
     ```
 
 ## Clean-up