From 960b1e3bb947d5c57fa60954785124c0849d588d Mon Sep 17 00:00:00 2001
From: "mergify[bot]" <37929162+mergify[bot]@users.noreply.github.com>
Date: Fri, 20 Sep 2024 22:47:31 +0000
Subject: [PATCH] Update qiskit/circuit/__init__.py (typo corrected) (#13203)
 (#13204)

* typo corrected

* Update __init__.py (typo corrected)

(cherry picked from commit 79a99a1ca46c742a1d5ecfc6a84dbef5a467a430)

Co-authored-by: Shivansh Mittal <88429611+Shivansh20128@users.noreply.github.com>
---
 qiskit/circuit/__init__.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/qiskit/circuit/__init__.py b/qiskit/circuit/__init__.py
index 180ea2c9462a..835371443bf0 100644
--- a/qiskit/circuit/__init__.py
+++ b/qiskit/circuit/__init__.py
@@ -455,7 +455,7 @@
 :class:`Instruction`\ s can be related to other circuits to provide a decompositions by using
 their :attr:`Instruction.definition` attribute, which provides a local, one-off decomposition.  This
 can be in whatever basis set of operations is most convenient to you, as long as the definitions of
-all contained gates have some topological order; that is, you cannot use a gate in a definition it
+all contained gates have some topological order; that is, you cannot use a gate in a definition if
 its own definition depends on the parent.  If the :class:`Instruction` should be considered entirely
 opaque to optimizers, its :attr:`~Instruction.definition` can be ``None``.  See
 :ref:`circuit-custom-gates` for more detail.