Index: groups.html
===================================================================
--- groups.html	(revision 16626)
+++ groups.html	(revision 16627)
@@ -30,7 +30,7 @@
 <h2> pcb-rnd config tree </h2>
 The config tree, the full tree is, something that exists in memory. Actual
 config files often contain only a subset of the tree. Multiple config files
-(e.g. system level, user level, settings from the .pcb file) are loaded and
+(e.g. system level, user level, settings from the board file) are loaded and
 merged to form the final config tree. The hierarchy of the tree is represented
 by setting groups, which are like directories on a file system. Actual settings
 are always leaves of the tree, placed in a specific group at any level (just
Index: index.html
===================================================================
--- index.html	(revision 16626)
+++ index.html	(revision 16627)
@@ -27,7 +27,7 @@
 	<li> ... there are <a href="lists.html">arrays and lists</a>
 	<li> ... a config file can overwrite a list or <a href="lists.html">prepend/append</a> to it (e.g. design-level config prepending an extra library path keeping system set paths as well)
 	<li> there are different <a href="sources.html"> sources </a> of configuration, e.g. system-wise, user-wise, project-wise, etc.
-	<li> the user has the power to change default config <a href="prio.html">priority per setting</a>; 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
+	<li> the user has the power to change default config <a href="prio.html">priority per setting</a>; 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
 	<li> the way settings are stored is flexible and extensible so that a plugin can define their subtree of settings
 	<li> ... 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
 	<li> ... the GUI (gtk's preferences dialog) thus can automatically handle the new settings
Index: index_user.html
===================================================================
--- index_user.html	(revision 16626)
+++ index_user.html	(revision 16627)
@@ -47,7 +47,7 @@
 the user to change settings. Such a change is always fed back (blue arrow)
 to the design role tree directly, from where the new value is again merged
 and dispatched along the red arrows. Changes in the design role are saved
-with the .pcb file (thus the bidirectional black arrow between the source and
+with the board file (thus the bidirectional black arrow between the source and
 the in-memory tree for the design role). Occasionally the user wants to
 save parts of the setting as a <a href="sources.html"> project setting or
 as an user setting</a> - in this case, along the dashed blue lines, the
Index: sources.html
===================================================================
--- sources.html	(revision 16626)
+++ sources.html	(revision 16627)
@@ -28,7 +28,7 @@
 
 <tr><td> default board
     <td> 300
-    <td> /usr/share/pcb-rnd/default4.pcb<a href="#footnote1"><sup>1</sup></a>
+    <td> /usr/share/pcb-rnd/default4.lht<a href="#footnote1"><sup>1</sup></a>
     <td> deprecated<a href="#footnote2"><sup>2</sup></a>
     <td> pcb editable defaults
 
@@ -48,11 +48,11 @@
     <td> 600
     <td> project.lht in the project directory
     <td> optional
-    <td> local project settings - useful for large projects with multiple design (.pcb) files
+    <td> local project settings - useful for large projects with multiple board (.lht) files
 
 <tr><td> design
     <td> 700
-    <td> saved in the design (.pcb) file
+    <td> saved in the board (.lht) file
     <td> optional, common
     <td> per design deviation from the user+system config