Updates to the release notes for 0.33

doc/development/deprecations.rst

@@ -9,7 +9,7 @@ Pending deprecations
 * ``qml.ExpvalCost`` has been deprecated, and usage will now raise a warning.
 
   - Deprecated in v0.24
-  - Will be removed in v0.32
+  - Will be removed in v0.34
 
   Instead, it is recommended to simply
   pass Hamiltonians to the ``qml.expval`` function inside QNodes:
@@ -21,27 +21,20 @@ Pending deprecations
         some_qfunc(params)
         return qml.expval(Hamiltonian)
 
-* The behaviour of ``Operator.__eq__`` and ``Operator.__hash__`` will be updated soon. Their documentation
-  has been updated to reflect the incoming changes.
-
-  The upcoming changes to operator equality will allow users to use operator equality the same way as
-  with ``qml.equal``. With the changes to hashing, unique operators that are equal will have the same
-  hash. These changes will allow behaviour such as the following:
-
-  >>> qml.RX(0.1, wires=0) == qml.RX(0.1, wires=0)
-  True
-  >>> {qml.PauliZ(0), qml.PauliZ(0)}
-  {PauliZ(wires=[0])}
+* The ``prep`` keyword argument in ``QuantumScript`` is deprecated and will be removed from ``QuantumScript``.
+  ``StatePrepBase`` operations should be placed at the beginning of the `ops` list instead.
 
-  Meanwhile, the current behaviour is shown below:
+  - Deprecated in v0.33
+  - Will be removed in v0.34
 
-  >>> qml.RX(0.1, wires=0) == qml.RX(0.1, wires=0)
-  False
-  >>> {qml.PauliZ(0), qml.PauliZ(0)}
-  {PauliZ(wires=[0]), PauliZ(wires=[0])}
+* `qml.gradients.pulse_generator` becomes `qml.gradients.pulse_odegen` to adhere to paper naming conventions. During v0.33, `pulse_generator`
+  is still available but raises a warning.
+
+  - Deprecated in v0.33
+  - Will be removed in v0.34
 
-  - Added in v0.32
-  - Behaviour will change in v0.33
+Completed deprecation cycles
+----------------------------
 
 * The public methods of ``DefaultQubit`` are pending changes to
   follow the new device API.
@@ -51,7 +44,7 @@ Pending deprecations
   will be abstracted away from the device class itself and provided by composition, rather than inheritance.
   Therefore, some public and private methods from ``DefaultQubit`` will no longer exist, though its behaviour
   in a workflow will remain the same.
-  
+
   If you directly interact with device methods, please consult
   :class:`pennylane.devices.Device` and
   :class:`pennylane.devices.DefaultQubit`
@@ -62,22 +55,29 @@ Pending deprecations
   `discussion forum <https://discuss.pennylane.ai/>`_.
 
   - Deprecated in v0.31
-
-* The ``prep`` keyword argument in ``QuantumScript`` is deprecated and will be removed from ``QuantumScript``.
-  ``StatePrepBase`` operations should be placed at the beginning of the `ops` list instead.
+  - Changed in v0.33
 
-  - Deprecated in v0.33
-  - Will be removed in v0.34
+* The behaviour of ``Operator.__eq__`` and ``Operator.__hash__`` will be updated soon. Their documentation
+  has been updated to reflect the incoming changes.
 
-* `qml.gradients.pulse_generator` becomes `qml.gradients.pulse_odegen` to adhere to paper naming conventions. During v0.33, `pulse_generator`
-  is still available but raises a warning.
-
-  - Deprecated in v0.33
-  - Will be removed in v0.34
+  The upcoming changes to operator equality will allow users to use operator equality the same way as
+  with ``qml.equal``. With the changes to hashing, unique operators that are equal will have the same
+  hash. These changes will allow behaviour such as the following:
 
+  >>> qml.RX(0.1, wires=0) == qml.RX(0.1, wires=0)
+  True
+  >>> {qml.PauliZ(0), qml.PauliZ(0)}
+  {PauliZ(wires=[0])}
 
-Completed deprecation cycles
-----------------------------
+  Meanwhile, the current behaviour is shown below:
+
+  >>> qml.RX(0.1, wires=0) == qml.RX(0.1, wires=0)
+  False
+  >>> {qml.PauliZ(0), qml.PauliZ(0)}
+  {PauliZ(wires=[0]), PauliZ(wires=[0])}
+
+  - Added in v0.32
+  - Behaviour changed in v0.33
 
 * ``qml.qchem.jordan_wigner`` had been removed.
   Use ``qml.jordan_wigner`` instead. List input to define the fermionic operator

doc/introduction/measurements.rst

@@ -391,7 +391,7 @@ statistics are :class:`~.pennylane.devices.DefaultQubit`, :class:`~.pennylane.de
 
 .. code-block:: python3
 
-    dev = qml.device("default.qubit", wires=2)
+    dev = qml.device("default.qubit")
 
     @qml.qnode(dev)
     def func(x, y):
@@ -406,6 +406,14 @@ Executing this QNode:
 (tensor([0.9267767, 0.0732233], requires_grad=True),
  tensor([0.5, 0.5], requires_grad=True))
 
+The deferred measurement principle provides a natural method to simulate the
+application of mid-circuit measurements and conditional operations in a
+differentiable and device-independent way. Performing true mid-circuit
+measurements and conditional operations is dependent on the
+quantum hardware and PennyLane device capabilities.
+
+For more examples on applying quantum functions conditionally, refer to the
+:func:`~.pennylane.cond` transform.
 .. warning::
 
     Currently, statistics can only be collected for single mid-circuit measurement values. Moreover, any