docs: Add note about server host name

docs/content/docs/2.getting-started/3.preparing-your-servers-for-spin.md

@@ -99,8 +99,10 @@ apt -y update && apt -y upgrade && apt -y autoremove && apt -y autoclean && rebo
 ```
 ::
 
-
 ## Configure server inventory and settings
+::note
+If your files are encrypted, you need to use the [`spin vault edit`](/docs/command-reference/vault) command to edit the file. This will decrypt the file, open it in your default editor, and then re-encrypt it when you save and close the file.
+::
 Assuming you've already ran [`spin new`](/docs/command-reference/new) or [`spin init`](/docs/command-reference/init) in your project, there are two files that will need to be configured:
 - `.spin-inventory.ini`
 - `.spin.yml`
@@ -109,7 +111,7 @@ Assuming you've already ran [`spin new`](/docs/command-reference/new) or [`spin
 We call the list of our servers "inventory". This follows the [Ansible Inventory format](https://docs.ansible.com/ansible/latest/inventory_guide/intro_inventory.html). For example, if you wanted to add `server01.example.com` as the production server, we would configure our file to look like this and add this server to go underneath the `production_manager_servers` group:
 
 ::note
-If your files are encrypted, you need to use the [`spin vault edit`](/docs/command-reference/vault) command to edit the file. This will decrypt the file, open it in your default editor, and then re-encrypt it when you save and close the file.
+Be sure to use your **server's hostname** (NOT your application's **domain name**) in the inventory file. This will ensure we have a dedicated DNS entry for managing your server.
 ::
 
 ::code-panel