From 891f6675f8938ea539fa94bc80f4788835917d22 Mon Sep 17 00:00:00 2001 From: F18-Maverick Date: Tue, 4 Nov 2025 20:02:45 +0800 Subject: [PATCH] Docs: fix a form error and a grammatical error in float.rst --- Doc/c-api/float.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/c-api/float.rst b/Doc/c-api/float.rst index 489676caa3a16a..3a03a9bfedd0ad 100644 --- a/Doc/c-api/float.rst +++ b/Doc/c-api/float.rst @@ -96,7 +96,7 @@ NaNs (if such things exist on the platform) isn't handled correctly, and attempting to unpack a bytes string containing an IEEE INF or NaN will raise an exception. -Note that NaNs type may not be preserved on IEEE platforms (silent NaN become +Note that NaN types may not be preserved on IEEE platforms (silent NaN become quiet), for example on x86 systems in 32-bit mode. On non-IEEE platforms with more precision, or larger dynamic range, than IEEE @@ -111,7 +111,7 @@ Pack functions The pack routines write 2, 4 or 8 bytes, starting at *p*. *le* is an :c:expr:`int` argument, non-zero if you want the bytes string in little-endian -format (exponent last, at ``p+1``, ``p+3``, or ``p+6`` ``p+7``), zero if you +format (exponent last, at ``p+1``, ``p+3``, or ``p+6`` and ``p+7``), zero if you want big-endian format (exponent first, at *p*). The :c:macro:`PY_BIG_ENDIAN` constant can be used to use the native endian: it is equal to ``1`` on big endian processor, or ``0`` on little endian processor.