Fix docs typo

Author: iluuu1994

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 <todo>`__ 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 <todo>`__ 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