--- a/flys-artifacts/ChangeLog	Fri Apr 22 09:57:27 2011 +0000
+++ b/flys-artifacts/ChangeLog	Fri Apr 22 15:49:35 2011 +0000
@@ -1,3 +1,8 @@
+2011-04-22	Sascha L. Teichmann	<sascha.teichmann@intevation.de>
+
+	* src/main/java/de/intevation/flys/artifacts/model/WstValueTable.java:
+	  Corrected a silly c&p mistake.
+
 2011-04-22	Sascha L. Teichmann	<sascha.teichmann@intevation.de>
 
 	* src/main/java/de/intevation/flys/artifacts/math/BackJumpCorrector.java:
@@ -11,16 +16,16 @@
 
 	  a - What should happend when you cannot find point 2 because
 	      you cannot step back one quarter from point 3 because there
-		  is no data there any more (river too short in this direction)?
-		  The implemented algorithm raises point 3' only to an
-		  according factor. E.g. If you can step back the whole quarter
-		  distance the elevation is the full quarter. If you can
-		  step back only the half of the quarter the elevation is
-		  only an eighth.
+	      is no data there any more (river too short in this direction)?
+	      The implemented algorithm raises point 3' only to an
+	      according factor. E.g. If you can step back the whole quarter
+	      distance the elevation is the full quarter. If you can
+	      step back only the half of the quarter the elevation is
+	      only an eighth.
 
 	  b - If the water heights between point 2 and 3 are constant then
 	      the algorithm will produce a spline interpolation that
-		  lowers those values. Is this intended?
+	      lowers those values. Is this intended?
 
 	  For real data the back jumps are expected to be more in the middle
 	  of the distance ranges so the corner cases are maybe not so