some typos in 0.45 release notes (backport #11100)

releasenotes/notes/0.45/h_basic_aer-3fc5e6776f0de9c1.yaml

@@ -1,5 +1,5 @@
 ---
 upgrade:
   - |
-    The `QasmSimulator` python-based simulator included in :class:`qiskit.providers.basicaer` 
-    now includes `h` (:class:`.HGate`), `p` (:class:`.PhaseGate`), and `u` (:class:`.UGate`) in its basis gate set.
+    The ``QasmSimulator`` python-based simulator included in :class:`qiskit.providers.basicaer` 
+    now includes ``'h'`` (:class:`.HGate`), ``'p'`` (:class:`.PhaseGate`), and ``'u'`` (:class:`.UGate`) in its basis gate set.

releasenotes/notes/0.45/remove-deprecated-code-in-0.22-128475199e6f3cc2.yaml

@@ -2,11 +2,11 @@
 upgrade:
   - |
     The method :meth:`qiskit.quantum_info.pauli_basis`
-    does not accept `pauli_list` argument any more.
+    does not accept ``pauli_list`` argument any more.
     It was deprecated in Qiskit 0.39 (with Terra 0.22), released on Oct 2022.
 
   - |
     The function ``random_stabilizer_table`` 
     in the class :class:`qiskit.quantum_info.random` is removed. 
     It was deprecated in Qiskit 0.39 (with Terra 0.22), released on Oct 2022.
-    Instead, use :func:``qiskit.quantum_info.random.random_pauli_list``.
+    Instead, use :func:`qiskit.quantum_info.random.random_pauli_list`.

releasenotes/notes/0.45/remove-deprecated-code-in-0.22.0-139fa09ee0cc6df9.yaml

@@ -5,7 +5,7 @@ upgrade:
   - |
     Replaced the argument ``qobj[Qobj]`` in :meth:`qiskit.providers.aer.QasmSimulator.run()` with ``run_input[QuantumCircuit or Schedule or list]``
 
-    Here is an example to migrate yor code::
+    Here is an example to migrate your code::
 
       # Importing necessary Qiskit libraries
       from qiskit import transpile, QuantumCircuit

releasenotes/notes/0.45/remove-deprecated-in-quantum-info-0f9bd2b0c093307d.yaml

@@ -1,7 +1,7 @@
 ---
 upgrade:
   - |
-    The classes ``qiskit.quantum_info.PauliTable`` and `qiskit.quantum_info.StabilizerTable`
+    The classes ``qiskit.quantum_info.PauliTable`` and ``qiskit.quantum_info.StabilizerTable``
     are removed. The function ``random_pauli_table`` is also removed.
     They were deprecated in Qiskit 0.43 (with Terra 0.24), released in May 2023.
     Instead, you should use :class:`.PauliList` and :func:`.random_pauli_list`.

releasenotes/notes/0.45/single-pulse-rx-cal-347aadcee7bfe60b.yaml

@@ -4,7 +4,7 @@ features:
     Two new transpiler passes are added to generate single-pulse RX gate calibrations on the fly.
     These single-pulse RX calibrations will reduce the gate time in half, as described in 
     P.Gokhale et al, Optimized Quantum Compilation for Near-Term Algorithms with OpenPulse 
-    (2020), `arXiv:2004.11205 <https://arxiv.org/abs/2004.11205>`.
+    (2020), `arXiv:2004.11205 <https://arxiv.org/abs/2004.11205>`__.
 
     To reduce the amount of RX calibration data that needs to be generated,
     :class:`~qiskit.transpiler.passes.optimization.normalize_rx_angle.NormalizeRXAngle`
@@ -22,4 +22,4 @@ features:
 
     Such single-pulse calibrations reduces the RX gate time in half, compared to the 
     conventional sequence that consists of two SX pulses.
-    There could be an improvement in fidelity due to this reduction in gate time.
+    There could be an improvement in fidelity due to this reduction in gate time.

releasenotes/notes/0.45/singletons-83782de8bd062cbc.yaml

@@ -30,23 +30,23 @@ features:
     The following standard library gates are now instances of
     :class:`~.SingletonGate`:
 
-        * :class:`~.DCXGate`
-        * :class:`~.ECRGate`
-        * :class:`~.HGate`
-        * :class:`~.IGate`
-        * :class:`~.iSwapGate`
-        * :class:`~.SGate`
-        * :class:`~.SdgGate`
-        * :class:`~.SwapGate`
-        * :class:`~.SXGate`
-        * :class:`~.SXdgGate`
-        * :class:`~.TGate`
-        * :class:`~.TdgGate`
-        * :class:`~.XGate`
-        * :class:`~.RCCXGate`
-        * :class:`~.RC3XGate`
-        * :class:`~.YGate`
-        * :class:`~.ZGate`
+     * :class:`~.DCXGate`
+     * :class:`~.ECRGate`
+     * :class:`~.HGate`
+     * :class:`~.IGate`
+     * :class:`~.iSwapGate`
+     * :class:`~.SGate`
+     * :class:`~.SdgGate`
+     * :class:`~.SwapGate`
+     * :class:`~.SXGate`
+     * :class:`~.SXdgGate`
+     * :class:`~.TGate`
+     * :class:`~.TdgGate`
+     * :class:`~.XGate`
+     * :class:`~.RCCXGate`
+     * :class:`~.RC3XGate`
+     * :class:`~.YGate`
+     * :class:`~.ZGate`
 
     This means that if these classes are instantiated as (e.g.) ``XGate()`` using
     all the constructor defaults, they will all share a single global
@@ -81,25 +81,25 @@ features:
     The following standard library gates are now instances of
     :class:`~.SingletonControlledGate`:
 
-        * :class:`~.CHGate`
-        * :class:`~.CSGate`
-        * :class:`~.CSdgGate`
-        * :class:`~.CSwapGate`
-        * :class:`~.CSXGate`
-        * :class:`~.CXGate`
-        * :class:`~.CCXGate`
-        * :class:`~.C3SXGate`
-        * :class:`~.C3XGate`
-        * :class:`~.C4XGate`
-        * :class:`~.CYGate`
-        * :class:`~.CZGate`
+     * :class:`~.CHGate`
+     * :class:`~.CSGate`
+     * :class:`~.CSdgGate`
+     * :class:`~.CSwapGate`
+     * :class:`~.CSXGate`
+     * :class:`~.CXGate`
+     * :class:`~.CCXGate`
+     * :class:`~.C3SXGate`
+     * :class:`~.C3XGate`
+     * :class:`~.C4XGate`
+     * :class:`~.CYGate`
+     * :class:`~.CZGate`
 
     This means that unless a ``label``, ``condition``, ``duration``, ``unit``, or
     ``ctrl_state`` are set on the instance at creation time they will all share a
     single global instance whenever a new gate object is created. This results in large
     reduction in the memory overhead for > 1 object of these types.
   - |
-    Added a new method :meth`.Instruction.to_mutable` and attribute
+    Added a new method :meth:`.Instruction.to_mutable` and attribute
     :attr:`.Instruction.mutable` which is used to get a mutable copy and check whether
     an :class:`~.circuit.Instruction` object is mutable. With the introduction
     of :class:`~.SingletonGate` these methods can be used to have a unified interface
@@ -155,7 +155,7 @@ upgrade:
     instead of the original object.  ``label``, ``duration`` and ``unit`` can
     be given as keyword arguments to these gates at construction time, and a
     mutable instance will be returned automatically.
-    This change was necssary as part of converting
+    This change was necessary as part of converting
     these classes to be :class:`~.SingletonGate` and :class:`~.SingletonControlledGate`
     types which greatly reduces the memory footprint of repeated instances of these gates.
   - |
@@ -164,7 +164,7 @@ upgrade:
     :class:`~.QuantumCircuit` or :class:`~.DAGCircuit` classes it is important
     to note that the use of shared references for instances is much more common
     now. Previously, it was possible to reuse and share an instance of a
-    a circuit operation it wasn't very commonly used and a copy would generate
+    circuit operation it wasn't very commonly used and a copy would generate
     a unique instance. This has changed starting in this release because of
     :class:`~.SingletonInstruction` and :class:`.SingletonGate` being made available (and a large
     number of standard library gates now built off of it). If your usage of these objects is

releasenotes/notes/0.45/sparse-pauli-op-apply-layout-43149125d29ad015.yaml

@@ -2,9 +2,9 @@
 features:
   - |
     Added a new method, :meth:`~.SparsePauliOp.apply_layout`,
-    to the :class:~.SparsePauliOp` class. This method is used to apply
+    to the :class:`~.SparsePauliOp` class. This method is used to apply
     a :class:`~.TranspileLayout` layout from the transpiler
-    to a :class:~.SparsePauliOp` observable that was built for an
+    to a :class:`~.SparsePauliOp` observable that was built for an
     input circuit to the transpiler. This enables working with
     :class:`~.BaseEstimator` implementations and local transpilation more
     easily. For example::

releasenotes/notes/0.45/transpile-layout-improvements-118dd902d93e5b96.yaml

@@ -28,7 +28,7 @@ features:
     (the mapping of input circuit qubits to the final position in the output). This is distinct
     from the :attr:`~.TranspileLayout.final_layout` attribute which is the permutation caused by
     routing as a :class:`.Layout` object. The :meth:`~.TranspileLayout.final_index_layout` method
-    returns a list to showthe output position for each qubit in the input circuit to the transpiler.
+    returns a list to show the output position for each qubit in the input circuit to the transpiler.
     For example, with an original circuit::
 
         qc = QuantumCircuit(3)