Index: work/fem/TODO.export.txt
===================================================================
--- work/fem/TODO.export.txt	(revision 22816)
+++ work/fem/TODO.export.txt	(revision 22817)
@@ -22,11 +22,12 @@
      or if you need new fields, make that explicit. We need: what
      _exactly_ is needed from pcb-rnd's side.
   -> right now users enter 3 different mesh line densities (resolutions)
-     for copper, gap, and min spacing. if you user selects this feature these
-     densities would instead be calculated as fractions of lambda. Using
+     for copper, gap, and etc. if you user selects this feature these
+     densities would instead be calculated as fractions of lambda selected by
+     the user.
      c0 = speed of light ( 299792458 m/s )
      lambda_frac = what fraction of lambda they want to use for each of the
-     three densities. So the equation is used once for each density.
+     densities. So the equation is used once for each density.
      and ether
      f0 = center frequency of the pulse
      fc = 20dB cutoff frequency --> bandwidth is 2*fc
@@ -40,8 +41,10 @@
      FDTD = SetGaussExcite( FDTD, f0, fc );
      please note that in ether case it is encouraged to just put in the values
      for f0, fc, or f_max and not assign a variable name and etc.
+     we know from http://openems.de/index.php/FDTD_Mesh.html
+     that there are even some reasonable base settings for what the
+     lambda_frac values should be.
 
-
 ? optionally the ability to replace the bounds with the equation
  AirBox = c0/(f0+fc)/unit/25;
   -> no idea wat c0, f0, fc and unit are; please use pcb-rnd terms,