Docs: use more standard terminology "round-to-nearest-even" instead of "round-to...

Per suggestion from Tom Lane.
Discussion: https://postgr.es/m/flat/20191230.093451.1762483750956466101.t-ishii%40sraoss.co.jp

diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index 01a9ab76aa90b4ae4918b60aeb9762689495d76d..d1d033178ffcd2e4a3c92c3ad12a77b947caac46 100644 (file)
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -731,7 +731,7 @@ FROM generate_series(-3.5, 3.5, 1) as x;
      representable in the same binary precision. (However, the output value is
      currently never <emphasis>exactly</emphasis> midway between two
      representable values, in order to avoid a widespread bug where input
-     routines do not properly respect the round-to-even rule.) This value will
+     routines do not properly respect the round-to-nearest-even rule.) This value will
      use at most 17 significant decimal digits for <type>float8</type>
      values, and at most 9 digits for <type>float4</type> values.
     </para>