Apply suggestions from code review

Co-authored-by: Elena Peña Tapia <[email protected]>
Qiskit · Jul 26, 2024 · 891ade7 · 891ade7
1 parent 0b5b5b9
commit 891ade7
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/qiskit/circuit/gate.py b/qiskit/circuit/gate.py
@@ -118,7 +118,7 @@ def control(
             ctrl_state: the control state in decimal or as a bitstring
                 (e.g. ``'111'``). If ``None``, use ``2**num_ctrl_qubits-1``.
             annotated: indicates whether the controlled gate is implemented
-                as an annotated gate. If ``None``, this is set to ``False``,
+                as an annotated gate. If ``None``, this is set to ``False``
                 if the controlled gate can directly be constructed, and otherwise
                 set to ``True``. This allows defering the construction process in case the
                 synthesis of the controlled gate requires more information (e.g.

diff --git a/releasenotes/notes/annotated-params-116288d5628f7ee8.yaml b/releasenotes/notes/annotated-params-116288d5628f7ee8.yaml
@@ -25,6 +25,6 @@ upgrade_circuits:
   - |
     The ``annotated`` argument of the :meth:`.Gate.control` method is now 
     ``None``, which allows Qiskit to choose whether to annotate a controlled operation.
-    Generally, the concrete implementation (``annotated=False``) is returned, if it
-    is available, otherwise we set ``annotated=True``. This allows, for example, to 
-    defer the synthesis of controlled, parameterized gates.
+    If the concrete implementation (``annotated=False``) is available, it will be returned by
+    default. Otherwise, the annotated implementation will be returned (``annotated=True``). 
+    This allows, for example, to defer the synthesis of controlled, parameterized gates.