Added note about Ansible inventory

docs/content/docs/1.getting-started/2.prerequisites.md

@@ -88,5 +88,5 @@ Before you run [`spin provision`](/docs/command-reference/provision), the follow
 - You have a running **Ubuntu 22.04 LTS Server** running on any host of your choice
 - You have SSH access configured working between your computer and your server
 - The SSH account has `sudo` access to perform root-level changes
-- Your `.spin-inventory` is configured correctly
+- Your `.spin-inventory` is configured correctly (following [Ansible's standard inventory format](https://docs.ansible.com/ansible/latest/inventory_guide/intro_inventory.html))
 - Your `.spin.yml` is configured correctly

docs/content/docs/3.guide/2.add-spin-to-an-existing-project.md

@@ -51,7 +51,7 @@ Spin will not overwrite any files. It will only create files that don't exist. I
 ### Spin will create the following files & directories:
 - `.infrastructure/`
 - `.spin.yml`
-- `.spin-inventory.ini`
+- `.spin-inventory.ini` (it's just an [Ansible inventory file](https://docs.ansible.com/ansible/latest/inventory_guide/intro_inventory.html))
 - `docker-compose.yml`
 - `docker-compose.dev.yml`
 - `docker-compose.ci.yml`

docs/content/docs/3.guide/3.preparing-your-servers-for-spin.md

@@ -26,7 +26,7 @@ There are two files that will need to be configured:
 - `.spin.yml`
 
 #### Inventory
-We call the list of our servers "inventory". 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:
+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:
 
 ::code-panel
 ---