Improve clarification for `fixed`

6 months ago · 60b988df41
1 changed files with 1 additions and 1 deletions
--- a/docs/en/docs/deployment/https.md
+++ b/docs/en/docs/deployment/https.md
@ -65,7 +65,7 @@ Here's an example of how an HTTPS API could look like, step by step, paying atte

 It would probably all start by you **acquiring** some **domain name**. Then, you would configure it in a DNS server (possibly your same cloud provider).

-You would probably get a cloud server (a virtual machine) or something similar, and it would have a <dfn title="That doesn't change">fixed</dfn> **public IP address**.
+You would probably get a cloud server (a virtual machine) or something similar, and it would have a <dfn title="Doesn't change over time. Not dynamic">fixed</dfn> **public IP address**.

 In the DNS server(s) you would configure a record (an "`A record`") to point **your domain** to the public **IP address of your server**.