From a4dfa35f936b4c80ee2f58247b9fb3cd03ec41af Mon Sep 17 00:00:00 2001 From: Ilija Tovilo Date: Sun, 18 Feb 2024 20:31:54 +0100 Subject: [PATCH] Fix docs typo --- docs/source/core/data-structures/zval.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/source/core/data-structures/zval.rst b/docs/source/core/data-structures/zval.rst index 3fba7e7d237..512abfdf219 100644 --- a/docs/source/core/data-structures/zval.rst +++ b/docs/source/core/data-structures/zval.rst @@ -115,9 +115,9 @@ intimidating at first. We'll go over it step by step. ``zval.value`` reserves space for the actual variable data, as discussed above. ``zval.u1`` stores the variable type, the given ``IS_*`` constant, along with some other flags. It's -definition looks a bit complicated. You can think of the entire field as a 4 bit integer, split into -3 parts. ``v.type`` stores the actual variable type, ``v.type_flags`` is used for some `reference -counting `__ flags, and ``v.u.extra`` is pretty much unused. +definition looks a bit complicated. You can think of the entire field as a 4 byte integer, split +into 3 parts. ``v.type`` stores the actual variable type, ``v.type_flags`` is used for some +`reference counting `__ flags, and ``v.u.extra`` is pretty much unused. ``zval.u2`` defines some more storage for various contexts that is often unoccupied. It's there because the memory would otherwise be wasted due to padding, so we may as well make use of it. We'll