fix inaccuracies in int_fp_mv.mdwn

diff --git a/openpower/sv/int_fp_mv.mdwn b/openpower/sv/int_fp_mv.mdwn
index 7e97e2c5a14ec97e6831898fad1ffd08382e1198..1778e9400ba67cf7ff99c41c600f4a1cade1777d 100644 (file)
--- a/openpower/sv/int_fp_mv.mdwn
+++ b/openpower/sv/int_fp_mv.mdwn
@@ -432,21 +432,15 @@ operations.
 
 <div id="fpr-to-gpr-conversion-mode"></div>
 
-Different programming languages turn out to have completely different
-semantics for FP to Integer conversion.  Below is an overview
+IEEE 754 doesn't specify what results are obtained when converting a NaN or out-of-range floating-point value to integer, so different programming languages and ISAs have made different choices.  Below is an overview
 of the different variants, listing the languages and hardware that
 implements each variant.
 
-**Standard IEEE754 conversion**
-
-This conversion is outlined in the IEEE754 specification.  It is used
-by nearly all programming languages and CPUs.  In the case of OpenPOWER,
-the rounding mode is read from FPSCR
+For convenience, we will give those different conversion semantics names based on which common ISA or programming language uses them, since there may not be an established name for them:
 
 **Standard OpenPower conversion**
 
-This conversion, instead of exact IEEE754 Compliance, performs
-"saturation with NaN converted to minimum valid integer". This
+This conversion performs "saturation with NaN converted to minimum valid integer". This
 is also exactly the same as the x86 ISA conversion semantics.
 OpenPOWER however has instructions for both: