expland the explanation with an example and reword

Author: keenan-simpson

cuda_bindings/docs/source/tips_and_tricks.rst

@@ -12,4 +12,22 @@ There is an important distinction between the ``getPtr()`` method and the behavi
 Getting and setting attributes of extension types
 =================================================
 
-While the bindings outwardly presents the attributes of extension types in a Pythonic way, they can't always be interacted with in a Pythonic style. Often the getters/setters (__getitem__(), __setitem__()) are actually a translation step to convert values between Python and C. For example, in some cases, attempting to modify an attribute in place, will lead to unexpected behavior due to the constraints of the underlying implementation. For this reason, users should use the getters and setters directly when interacting with extension types.
+While the bindings outwardly presents the attributes of extension types in a Pythonic way, they can't always be interacted with in a Pythonic style. Often the getters/setters (__getitem__(), __setitem__()) are actually a translation step to convert values between Python and C. For example, in some cases, attempting to modify an attribute in place, will lead to unexpected behavior due to the design of the underlying implementation. For this reason, users should use the getters and setters directly when interacting with extension types. 
+
+An example of this is the :class:`~cuda.bindings.driver.CULaunchConfig` type. 
+
+.. code-block:: python
+
+    cfg = cuda.CUlaunchConfig()
+
+    cfg.numAttrs += 1
+    attr = cuda.CUlaunchAttribute()
+    
+    ...
+
+    # This works. We are passing the attribute to the setter
+    drv_cfg.attrs = [attr]
+
+    # This does not work. We are trying to modify the attribute in place
+    drv_cfg.attrs.append(attr)
+