Index: index.html
===================================================================
--- index.html (revision 16626)
+++ index.html (revision 16627)
@@ -27,7 +27,7 @@
... there are arrays and lists
... a config file can overwrite a list or prepend/append to it (e.g. design-level config prepending an extra library path keeping system set paths as well)
there are different sources of configuration, e.g. system-wise, user-wise, project-wise, etc.
- the user has the power to change default config priority per setting; e.g. normally design config overrides user config, but it's possible to mark a setting from user config so strong that it overrides even the setting read from the .pcb file
+ the user has the power to change default config priority per setting; e.g. normally design config overrides user config, but it's possible to mark a setting from user config so strong that it overrides even the setting read from the board file
the way settings are stored is flexible and extensible so that a plugin can define their subtree of settings
... since the API even makes it easier to access such settings (vs. parsing your own config file), plugins will tend to use the unified config format/system instead of inventing their own
... the GUI (gtk's preferences dialog) thus can automatically handle the new settings