Index: trunk/doc/conf/groups.html
===================================================================
--- trunk/doc/conf/groups.html	(revision 8256)
+++ trunk/doc/conf/groups.html	(revision 8257)
@@ -95,8 +95,8 @@
 <p>
 The utils/ subtree is very similar in all aspects except that it is for
 external utility programs. Utils that are closely related to pcb-rnd, such
-as gsch2pcb-rnd, should work from the same configuration (e.g. to
-make sure the same footprint paths are searched). If they already load the
+as gsch2pcb-rnd, should work from the same configuration.
+If they already load the
 pcb-rnd config files it's easier to keep their settings in the same tree,
 in the same format.
 <p>
Index: trunk/doc/features/pcb-fp.html
===================================================================
--- trunk/doc/features/pcb-fp.html	(revision 8256)
+++ trunk/doc/features/pcb-fp.html	(revision 8257)
@@ -29,7 +29,7 @@
 	<li> parametric footprints: replace m4 with a generic, language-independent footprint generator framework
 	<ul>
 		<li> implement libpcb_fp, which centralizes searching and loading footprints
-		<li> fork gsch2pcb to gsch2pcb-rnd that uses libpcb_fp (and does not have any m4 references hardwired)
+		<li> fork gsch2pcb to gsch2pcb-rnd that does not have any m4 references hardwired
 		<li> fork gnet_gsch2pcb.scm (the gnetlist backend) to remove m4 heuristics
 	</ul>
 </ul>
Index: trunk/doc/user/08_util/01_gsch2pcb-rnd.htm
===================================================================
--- trunk/doc/user/08_util/01_gsch2pcb-rnd.htm	(revision 8256)
+++ trunk/doc/user/08_util/01_gsch2pcb-rnd.htm	(revision 8257)
@@ -28,14 +28,6 @@
 		<td> method name
 		<td> description
 	<tr>
-		<td> pcb
-		<td> The classic approach: load the existing extract elements from
-		     the .sch file, load the .pcb file, compare element lists, load
-		     footprint libraries and create .new.pcb and .net and .cmd and let
-		     the user handle the rest. Does <b>not</b> work with anything else
-		     than the .pcb format. This method is <b>deprecated</b> and is
-		     provided only for compatibility with some old workflows.
-	<tr>
 		<td> import
 		<td> Runs the same gnetlist backend as the import_sch plugin. A single
 		     action command file generated with .cmd suffix. When executed
@@ -49,6 +41,10 @@
 		     separate .net netlist file that can be imported the same way as the
 		     .net of the pcb method. Pro: the user can update elements-only or
 		     nets-only. Con: requires two user actions to get a full impoty.
+	<tr>
+		<td> <strike>pcb</strike>
+		<td> The classic approach that tried to edit the .pcb file.
+		     <b>No longer supported</b>.
 </table>
 </body>
 </html>