Typos

Author: serramatutu

docs/source/format/CanonicalExtensions.rst

@@ -575,11 +575,11 @@ This extension type is intended to be compatible with ANSI SQL's ``TIMESTAMP WIT
 
    It is also *permissible* for ``timestamp`` and ``offset_minutes`` to be nullable, even though it is not preferred.
 
-   If ``timestamp`` is nullable and a value is found to be null, then the whole ``TimestampWithOffset`` value should be interpreted as null. One way of achieving this is to drop ``timestamp``'s validity buffer (V1) and replace the top-level struct validity buffer (V2) with the result of ``V1 AND V2``.
+   If ``timestamp`` is nullable and a value is found to be null, then the whole ``TimestampWithOffset`` value should be interpreted as null. One way of achieving this is to drop ``timestamp``'s validity buffer (V1) and replace the top-level struct's validity buffer (V2) with the result of ``V1 AND V2``.
 
-   If ``offset`` is nullable and a value is found to be null, then this value should be interpreted as if the offset value were were zero.
+   If ``offset_minutes`` is nullable and a value is found to be null, then this value should be interpreted as if the offset value were were zero.
 
-   It is *recommended* that implementations normalize this type's representation by dropping the inner validity buffers and applying the aforementioned transformations, only keeping the top-level struct validity buffer.
+   It is *recommended* that implementations normalize this type's representation by dropping the inner validity buffers and applying the aforementioned transformations, only keeping the top-level struct's validity buffer.
 
 .. note::