update docs and newsfrag

docs/web3.contract.rst

@@ -969,7 +969,7 @@ For example:
 
 .. _process_receipt:
 
-.. py:method:: ContractEvents.myEvent(*args, **kwargs).process_receipt(transaction_receipt, errors=WARN, abi_decode_strict=True)
+.. py:method:: ContractEvents.myEvent(*args, **kwargs).process_receipt(transaction_receipt, errors=WARN)
    :noindex:
 
    Extracts the pertinent logs from a transaction receipt.
@@ -1038,10 +1038,19 @@ For example:
        >>> assert processed_logs == ()
        True
        
-   In the case of an ``InsufficientDataBytes`` error, it may be possible to decode the log by passing ``abi_decode_strict=False``.
-   This will attempt to decode the log by reading only the data size specified in the ABI. This is useful when the log data is
-   not padded to the correct size, but the data is still valid. Because any data past the specified size is ignored, this may
-   result in data loss. It is not recommended for general use, but may be useful in some cases.
+   In the case of an ``InsufficientDataBytes`` error, it may be possible to decode the
+   log by setting the ``strict_bytes_type_checking`` flag to ``False`` on the Web3
+   instance.
+
+    .. code-block:: python
+  
+        >>> w3.strict_bytes_type_checking = False
+        
+  
+   This will attempt to decode the log by reading only the data size specified in the
+   ABI. This is useful when the log data is not padded to the correct size, but the data
+   is still valid. Because any data past the specified size is ignored, this may result
+   in data loss. It is not recommended for general use, but may be useful in some cases.
 
 .. py:method:: ContractEvents.myEvent(*args, **kwargs).process_log(log)
 

newsfragments/3256.feature.rst

@@ -1 +1 @@
-Catch ``InsufficientDataBytes`` errors and add ``abi_decode_strict`` flag to log receipt processing
+Catch ``InsufficientDataBytes`` errors and respect ``w3.strict_bytes_type_checking`` flag in log receipt processing