From 60b988df414bb7fb5e54c29bea006f3ff9b5701e Mon Sep 17 00:00:00 2001 From: Yurii Motov Date: Wed, 21 Jan 2026 10:57:02 +0100 Subject: [PATCH] Improve clarification for `fixed` --- docs/en/docs/deployment/https.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/docs/deployment/https.md b/docs/en/docs/deployment/https.md index 6f45a8903a..3dc624c724 100644 --- 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 fixed **public IP address**. +You would probably get a cloud server (a virtual machine) or something similar, and it would have a fixed **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**.