compatibility issues

doc/ngspice.texi

@@ -196,10 +196,6 @@ Alan's mail):
 
 * Output File Format Changes -
 
-Rawfile format changed to PSPICE Probe format (Usable with Demo 
-version of Microsim's Probe). (NOTE: Do not rely on this, we may 
-revert to the old format in the next release).
-
 Text mode .OP results even though "rawfile" written.
 
 Internal device nodes are not saved to "rawfile" (reduces file 
@@ -270,13 +266,12 @@ region, which means that when this jump allows the drain current to be
 calculated, Vdsat can already be well above zero. This leads to a 
 discontinuity of drain current with respect to gate voltage. The code 
 is now modified to use Vbin for the jump decision. It looks like the 
-code should actually use Vth as the threshold voltage, but since 
-PSPICE and HSPICE both follow the original Berkeley code, this was 
-left alone.
+code should actually use Vth as the threshold voltage, but since other 
+SPICE simulators follow the original Berkeley code, this was left alone.
 
 * New Model Parameters -
 
-A PSPICE/HSPICE-like "M" device parameter (i.e. M devices in parallel) 
+A device multiplier instance parameter "M" (i.e. M devices in parallel) 
 was added to the MOS1,2,3 and BSIM3 mosfet models.
 
 * Input Read-in and Checking -
@@ -10997,8 +10992,8 @@ region, which means that when this jump allows the drain current to be
 calculated, Vdsat can already be well above zero. This leads to a 
 discontinuity of drain current with respect to gate voltage. The code 
 is now modified to use Vbin for the jump decision. It looks like the 
-code should actually use Vth as the threshold voltage, but since 
-PSPICE and HSPICE both follow the original Berkeley code, this was 
+code should actually use Vth as the threshold voltage, but since other 
+SPICE simulators follow the original Berkeley code, this was 
 left alone. The affected code can be found in @code{MOS2load()}:
 
 @example