README.md in beaker-hostgenerator-2.8.2 vs README.md in beaker-hostgenerator-2.9.0

@@ -392,13 +392,13 @@
 environment_variables: {}
 expected_hash:
   HOSTS:
     centos9-64-1:
       pe_dir: "/opt/hello"
-      pe_ver: 
-      pe_upgrade_dir: 
-      pe_upgrade_ver: 
+      pe_ver:
+      pe_upgrade_dir:
+      pe_upgrade_ver:
       hypervisor: vmpooler
       platform: el-9-x86_64
       template: centos-9-x86_64
       roles:
       - agent
@@ -407,11 +407,11 @@
       - dashboard
   CONFIG:
     nfs_server: none
     consoleport: 443
     pooling_api: http://vmpooler.delivery.puppetlabs.net/
-expected_exception: 
+expected_exception:
 ```
 
 These test fixtures are yaml files searched for in the directory
 `test/fixtures`. The data structure expected in these files is a hash with four
 keys:
@@ -419,10 +419,10 @@
 - `arguments_string`: The command line arguments that should be passed to
   `beaker-hostgenerator`
 - `environment_variables`: The environment variables that should be set during
   the `beaker-hostgenerator` call.
 - `expected_hash`: A hash that should match the output of `beaker-hostgenerator`
-  when it is run with `options\_string`
+  when it is run with `arguments_string`
 - `expected_exception`: If the `arguments_string` passed to `beaker-hostgenerator`
   is expected to lead to an exceptional state, this is the name of the exception
   that the fixture test will attempt to match.
 
 #### Generated Fixtures