diff --git a/README.md b/README.md
index 7513f65..517a792 100644
--- a/README.md
+++ b/README.md
@@ -51,7 +51,7 @@ The playbook uses the ArchLinux ISO as a foundational tool to provides an effici
 
 ## 2. Global Variables
 
-Global variables apply across your Ansible project and are loaded from `vars.yml` by default. These variables define common settings such as hypervisor connection details and the boot ISO path. They can be overridden by inventory variables for specific hosts or VMs if needed.
+Global variables apply across your Ansible project and can be supplied via inventory or `-e @vars_example.yml`. These variables define common settings such as hypervisor connection details and the boot ISO path. They can be overridden by inventory variables for specific hosts or VMs if needed.
 
 ### 2.1 Core Provisioning
 
@@ -179,17 +179,17 @@ Before running the playbook, ensure you have Ansible installed and configured co
 
 ### 4.2 Running the Playbook
 
-Execute the playbook using the `ansible-playbook` command, ensuring that all necessary variables are defined, typically by specifying a `vars.yml` file containing the required configurations.
+Execute the playbook using the `ansible-playbook` command, ensuring that all necessary variables are defined, typically by specifying a vars file (such as `vars_example.yml`) containing the required configurations.
 
 ### 4.3 Example Usage
 
-An effective way to use the playbook involves defining all necessary configurations within a `vars.yml` file. This file should include all relevant global variables tailored to your specific deployment requirements. Additionally, you should prepare an inventory file (`inventory.yml`) that lists all the hosts along with any specific inventory variables they might need. Then, you can run the playbook as follows:
+An effective way to use the playbook involves defining all necessary configurations within a vars file (for example, `vars_example.yml`). This file should include all relevant global variables tailored to your specific deployment requirements. Additionally, you should prepare an inventory file (`inventory.yml`) that lists all the hosts along with any specific inventory variables they might need. Then, you can run the playbook as follows:
 
 ```bash
-ansible-playbook -i inventory.yml -e @vars.yml main.yml
+ansible-playbook -i inventory.yml -e @vars_example.yml main.yml
 ```
 
-This command prompts Ansible to execute the `main.yml` playbook, applying configurations defined in both `vars.yml` and the inventory file.
+This command prompts Ansible to execute the `main.yml` playbook, applying configurations defined in both the vars file and the inventory file.
 
 Use `inventory_example.yml`, `inventory_libvirt_example.yml`, `vars_example.yml`, and the bare-metal examples as starting points for new inventories.
 
diff --git a/main.yml b/main.yml
index 74cb760..8f047dc 100644
--- a/main.yml
+++ b/main.yml
@@ -24,7 +24,6 @@
       prompt: |
         What is your root password?
       confirm: true
-  vars_files: vars.yml
   pre_tasks:
     - name: Load global defaults
       ansible.builtin.import_role: