clarified the settings commands documentation

README.md

@@ -91,6 +91,10 @@ longer need to fiddle with the `startup` commands of each profile, instead you
 can use voice commands to change settings! See the `docs/` and the 
 `_configuration` commands section of each profile.
 
+Basically all the settings are available using the `customize settings` prefix, 
+then saying `[enable;disable] <setting>` for on/off switches and `set <setting>` 
+for text variables.
+
 One caveat applies: settings are stored in the _profile where you run the 
 configuration commands_. If you change your active, main profile around a lot 
 you’ll have to set everything up for each of them separately. I suggest instead 

docs/EliteDangerous.md

@@ -412,6 +412,10 @@ manipulating some UI element(s).
 There are a bunch of configuration variables. You should not overwrite those 
 manually, instead use the provided commands in the `_configuration` section!
 
+Basically all the settings are available using the `customize settings` prefix, 
+then saying `[enable;disable] <setting>` for on/off switches and `set <setting>` 
+for text variables.
+
 * `EDDI.quietMode` (boolean): whether or not to set EDDI to quite mode. Default: 
   true.
 * `Elite.pasteKey` (string): the key used for pasting into Elite. On QWERTY this 

docs/RatAttack.md

@@ -224,6 +224,10 @@ don’t unless it’s a config variable …) from other profiles.
 There are a bunch of configuration variables. You should not overwrite those 
 manually, instead use the provided commands in the `_configuration` section!
 
+Basically all the settings are available using the `customize settings` prefix, 
+then saying `[enable;disable] <setting>` for on/off switches and `set <setting>` 
+for text variables.
+
 * `EDDI.quietMode` (boolean): whether or not to set EDDI to quite mode. Default: 
   true.
 * `EDDI.useEddiForVoice` (boolean): whether to use the EDDI plugin to handle 

docs/SealAttack.md

@@ -216,6 +216,10 @@ don’t unless it’s a config variable …) from other profiles.
 There are a bunch of configuration variables. You should not overwrite those 
 manually, instead use the provided commands in the `_configuration` section!
 
+Basically all the settings are available using the `customize settings` prefix, 
+then saying `[enable;disable] <setting>` for on/off switches and `set <setting>` 
+for text variables.
+
 * `EDDI.quietMode` (boolean): whether or not to set EDDI to quite mode. Default: 
   true.
 * `EDDI.useEddiForVoice` (boolean): whether to use the EDDI plugin to handle 

docs/SpanshAttack.md

@@ -179,6 +179,10 @@ don’t unless it’s a config variable …) from other profiles:
 There are a bunch of configuration variables. You should not overwrite those 
 manually, instead use the provided commands in the `_configuration` section!
 
+Basically all the settings are available using the `customize settings` prefix, 
+then saying `[enable;disable] <setting>` for on/off switches and `set <setting>` 
+for text variables.
+
 * `EDDI.quietMode` (boolean): whether or not to set EDDI to quite mode. Default: 
   true.
 * `EDDI.useEddiForVoice` (boolean): whether to use EDDI over VA’s builtin `say` 

docs/StreamAttack.md

@@ -89,6 +89,10 @@ don’t unless it’s a config variable …) from other profiles:
 There are a bunch of configuration variables. You should not overwrite those 
 manually, instead use the provided commands in the `_configuration` section!
 
+Basically all the settings are available using the `customize settings` prefix, 
+then saying `[enable;disable] <setting>` for on/off switches and `set <setting>` 
+for text variables.
+
 * `EDDI.quietMode` (boolean): whether or not to set EDDI to quite mode. Default: 
   true.
 * `EDDI.useEddiForVoice` (boolean): whether to use EDDI over VA’s builtin `say`