Apply suggestions from code review

Co-authored-by: Sergey B Kirpichev <[email protected]>

Author: picnixz

Doc/library/math.rst

@@ -256,7 +256,7 @@ Floating point arithmetic
    When both operands are (signed) NaNs or zeroes, return ``nan`` and ``0``
    respectively and the sign of the result is implementation-defined, that
    is, :func:`!fmax` is not required to be sensitive to the sign of such
-   operands (see ISO C11, Annexes F.10.0.3 and F.10.9.2).
+   operands (see Annex F of the C11 standard, §F.10.0.3 and §F.10.9.2).
 
    .. versionadded:: next
 
@@ -268,7 +268,7 @@ Floating point arithmetic
    When both operands are (signed) NaNs or zeroes, return ``nan`` and ``0``
    respectively and the sign of the result is implementation-defined, that
    is, :func:`!fmin` is not required to be sensitive to the sign of such
-   operands (see ISO C11, Annexes F.10.0.3 and F.10.9.3).
+   operands (see Annex F of the C11 standard, §F.10.0.3 and §F.10.9.3).
 
    .. versionadded:: next
 

Lib/test/test_math.py

@@ -629,7 +629,7 @@ def test_fmax(self):
         self.assertRaises(TypeError, math.fmax, 'x', 'y')
 
         self.assertEqual(math.fmax(0., 0.), 0.)
-        # fmax() does not need to be sensitive to the sign of 0 (F.10.9.2.3).
+        # fmax() does not need to be sensitive to the sign of 0 (§F.10.9.2).
         self.assertIn(math.fmax(0., -0.), {-0., 0.})
         self.assertIn(math.fmax(-0., 0.), {-0., 0.})
 
@@ -673,7 +673,7 @@ def test_fmin(self):
         self.assertRaises(TypeError, math.fmin, 'x', 'y')
 
         self.assertEqual(math.fmin(0., 0.), 0.)
-        # fmin() does not need to be sensitive to the sign of 0 (F.10.9.3.1).
+        # fmin() does not need to be sensitive to the sign of 0 (§F.10.9.3).
         self.assertIn(math.fmin(0., -0.), {-0., 0.})
         self.assertIn(math.fmin(-0., 0.), {-0., 0.})