From c7ab5e1eb6546573fc7ee8809163013a339e2aa9 Mon Sep 17 00:00:00 2001 From: ABBY CROSS Date: Fri, 19 Dec 2025 15:11:11 -0500 Subject: [PATCH 1/2] include matplotlib.pyplot as plt --- docs/guides/quick-start.ipynb | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/guides/quick-start.ipynb b/docs/guides/quick-start.ipynb index 2834e236c40..e51c76fc1aa 100644 --- a/docs/guides/quick-start.ipynb +++ b/docs/guides/quick-start.ipynb @@ -200,12 +200,13 @@ } ], "source": [ + "# Include the two commented-out lines if you are not using Python in a Jupyter notebook\n", + "# import matplotlib.pyplot as plt\n", "from qiskit.visualization import plot_histogram\n", "\n", "counts = result[0].data.meas.get_counts()\n", "plot_histogram(counts)\n", "\n", - "# Include the next line if you are not using Python in a Jupyter notebook\n", "# plt.show()" ] }, From 5126fce202ac389d446b0e822efa3846e3e8bf90 Mon Sep 17 00:00:00 2001 From: Emmanuel Osalotioman Osazuwa <109004799+Osalotioman@users.noreply.github.com> Date: Fri, 19 Dec 2025 21:31:43 +0100 Subject: [PATCH 2/2] chore: update comments to fix translation problems in documentation (#4421) In the documentation, multiple objects of a class were sometimes referred to using the style "`MyClass`s". This PR updates these references to "`MyClass` objects" to fix translation problems in documentation. This addresses the part of #2067 for `/guides`. --------- Co-authored-by: abbycross --- .../classical-feedforward-and-control-flow.ipynb | 2 +- docs/guides/custom-transpiler-pass.ipynb | 2 +- docs/guides/dynamical-decoupling-pass-manager.ipynb | 6 +++--- docs/guides/fractional-gates.ipynb | 2 +- docs/guides/functions.ipynb | 2 +- docs/guides/ibm-circuit-function.ipynb | 2 +- docs/guides/monitor-job.ipynb | 2 +- docs/guides/primitive-input-output.ipynb | 10 +++++----- docs/guides/qiskit-addons-cutting-gates.ipynb | 2 +- docs/guides/qiskit-addons-cutting-wires.ipynb | 2 +- docs/guides/qiskit-addons-cutting.mdx | 2 +- docs/guides/qiskit-addons-utils.ipynb | 4 ++-- docs/guides/represent-quantum-computers.ipynb | 2 +- docs/guides/simulate-with-qiskit-sdk-primitives.ipynb | 2 +- docs/guides/transpile.mdx | 2 +- 15 files changed, 22 insertions(+), 22 deletions(-) diff --git a/docs/guides/classical-feedforward-and-control-flow.ipynb b/docs/guides/classical-feedforward-and-control-flow.ipynb index 8f6d55ebe53..d920728ff2e 100644 --- a/docs/guides/classical-feedforward-and-control-flow.ipynb +++ b/docs/guides/classical-feedforward-and-control-flow.ipynb @@ -360,7 +360,7 @@ " with circuit.if_test((c0, 3)) ...\n", " with circuit.if_test((c1[2], 1)) ...\n", " ```\n", - " In the previous code example, the first two `if_test`s on `c0` are considered one broadcast because the content of `c0` did not change, and thus does not need to be re-broadcasted. The `if_test` on `c1` is a second broadcast. The first one broadcasts all three bits in `c0` and the second broadcasts just one bit, making a total of four broadcasted bits.\n", + " In the previous code example, the first two `if_test` objects on `c0` are considered one broadcast because the content of `c0` did not change, and thus does not need to be re-broadcasted. The `if_test` on `c1` is a second broadcast. The first one broadcasts all three bits in `c0` and the second broadcasts just one bit, making a total of four broadcasted bits.\n", "\n", " Currently, if you broadcast 60 bits each time, then the job can have approximately 300 broadcasts. If you broadcast just one bit each time, however, then the job can have 2400 broadcasts.\n", "\n", diff --git a/docs/guides/custom-transpiler-pass.ipynb b/docs/guides/custom-transpiler-pass.ipynb index c7309d6f54c..b9665371a0e 100644 --- a/docs/guides/custom-transpiler-pass.ipynb +++ b/docs/guides/custom-transpiler-pass.ipynb @@ -220,7 +220,7 @@ "source": [ "## Use the `PauliTwirl` transpiler pass\n", "\n", - "The following code uses the pass created above to transpile a circuit. Consider a simple circuit with `cx`s and `ecr`s." + "The following code uses the pass created above to transpile a circuit. Consider a simple circuit with `cx` and `ecr` gates." ] }, { diff --git a/docs/guides/dynamical-decoupling-pass-manager.ipynb b/docs/guides/dynamical-decoupling-pass-manager.ipynb index 5894659d33e..2bc6fdf6444 100644 --- a/docs/guides/dynamical-decoupling-pass-manager.ipynb +++ b/docs/guides/dynamical-decoupling-pass-manager.ipynb @@ -123,7 +123,7 @@ "id": "9d735702-4b06-4979-a0c1-2004a3c95d28", "metadata": {}, "source": [ - "Because of the regular timing of dynamical decoupling sequences, information about the `YGate` must be added to the `target` because it is *not* a basis gate, whereas the `XGate` is. We know *a priori* that the `YGate` has the same duration and error as the `XGate`, however, so we can just retrieve those properties from the `target` and add them back for the `YGate`s. This is also why the `basis_gates` were saved separately, since we are adding the `YGate` instruction to the `target` although it is not an actual basis gate of `ibm_fez`." + "Because of the regular timing of dynamical decoupling sequences, information about the `YGate` must be added to the `target` because it is *not* a basis gate, whereas the `XGate` is. We know *a priori* that the `YGate` has the same duration and error as the `XGate`, however, so we can just retrieve those properties from the `target` and add them back for the `YGate` objects. This is also why the `basis_gates` were saved separately, since we are adding the `YGate` instruction to the `target` although it is not an actual basis gate of `ibm_fez`." ] }, { @@ -207,7 +207,7 @@ "id": "5d418164-acbd-4694-8864-8c3100886157", "metadata": {}, "source": [ - "Use the visualization tool [`timeline_drawer`](/docs/api/qiskit/qiskit.visualization.timeline_drawer) to see the circuit's timing and confirm that a regularly-spaced sequence of `XGate`s and `YGate`s appear in the circuit." + "Use the visualization tool [`timeline_drawer`](/docs/api/qiskit/qiskit.visualization.timeline_drawer) to see the circuit's timing and confirm that a regularly-spaced sequence of `XGate` objects and `YGate` objects appear in the circuit." ] }, { @@ -273,7 +273,7 @@ "id": "69c77b6c-1f38-4adc-9249-0039ecd2c3c1", "metadata": {}, "source": [ - "Now, `YGate`s are absent from our circuit, and there is explicit timing information in the form of `Delay` gates. This transpiled circuit with dynamical decoupling is now ready to be sent to the backend." + "Now, `YGate` objects are absent from our circuit, and there is explicit timing information in the form of `Delay` gates. This transpiled circuit with dynamical decoupling is now ready to be sent to the backend." ] }, { diff --git a/docs/guides/fractional-gates.ipynb b/docs/guides/fractional-gates.ipynb index acc747f67c3..a8268041522 100644 --- a/docs/guides/fractional-gates.ipynb +++ b/docs/guides/fractional-gates.ipynb @@ -49,7 +49,7 @@ "source": [ "## How to use fractional gates\n", "\n", - "Internally, these fractional gates work by directly executing an $R_{ZZ}(\\theta)$ and $R_X(\\theta)$ rotation for an arbitrary angle. Use of the $R_X(\\theta)$ gate can reduce the duration and error for single-qubit rotations of arbitrary angle by up to a factor of two. The direct execution of the $R_{ZZ}(\\theta)$ gate rotation avoids decomposition into multiple `CZGate`s, similarly reducing a circuit's duration and error. This is especially useful for circuits that contain many single- and two-qubit rotations, such as when simulating the dynamics of a quantum system or when using a variational ansatz with many parameters.\n", + "Internally, these fractional gates work by directly executing an $R_{ZZ}(\\theta)$ and $R_X(\\theta)$ rotation for an arbitrary angle. Use of the $R_X(\\theta)$ gate can reduce the duration and error for single-qubit rotations of arbitrary angle by up to a factor of two. The direct execution of the $R_{ZZ}(\\theta)$ gate rotation avoids decomposition into multiple `CZGate` objects, similarly reducing a circuit's duration and error. This is especially useful for circuits that contain many single- and two-qubit rotations, such as when simulating the dynamics of a quantum system or when using a variational ansatz with many parameters.\n", "\n", "\n", "While these types of gates are in the [library of standard gates](./circuit-library) which a `QuantumCircuit` can possess, they can only be used on specific IBM Quantum QPUs, and which must be loaded with the flag `use_fractional_gates` set to `True` (shown below). This flag will ensure that fractional gates are included in the backend's `Target` for the transpiler.\n", diff --git a/docs/guides/functions.ipynb b/docs/guides/functions.ipynb index 1eb0b248d88..b8d863ea1c5 100644 --- a/docs/guides/functions.ipynb +++ b/docs/guides/functions.ipynb @@ -46,7 +46,7 @@ "\n", "| Type | What does it do? | Example inputs and outputs | Who is it for? |\n", "| - | - | - | - |\n", - "| Circuit function | Simplified interface for running circuits. Abstracts transpilation, error suppression, error mitigation | **Input**: Abstract `PUB`s
**Output**: Mitigated expectation values | Researchers using Qiskit to discover new algorithms and applications, without needing to focus on optimizing for hardware or handling error. Circuit functions can be used to build custom application functions. |\n", + "| Circuit function | Simplified interface for running circuits. Abstracts transpilation, error suppression, error mitigation | **Input**: Abstract `PUB` objects
**Output**: Mitigated expectation values | Researchers using Qiskit to discover new algorithms and applications, without needing to focus on optimizing for hardware or handling error. Circuit functions can be used to build custom application functions. |\n", "| Application function | Covers higher-level tasks, like exploring algorithms and domain-specific use cases. Abstracts quantum workflow to solve tasks, with classical inputs and outputs | **Input**: Molecules, graphs
**Output**: Ground + excited state energy, optimal values for cost function | Researchers in non-quantum domains, integrating quantum into existing large-scale classical workflows, without needing to map classical data to quantum circuits. |" ] }, diff --git a/docs/guides/ibm-circuit-function.ipynb b/docs/guides/ibm-circuit-function.ipynb index e1308565e25..ae2b21ea9c3 100644 --- a/docs/guides/ibm-circuit-function.ipynb +++ b/docs/guides/ibm-circuit-function.ipynb @@ -274,7 +274,7 @@ "| | zne_mitigation | | Whether to turn on Zero Noise Extrapolation error mitigation method. Refer to [Error suppression and mitigation techniques](/docs/guides/error-mitigation-and-suppression-techniques#zero-noise-extrapolation-zne) for the explanation of the method. | True/False | False |\n", "| | zne | amplifier | Which technique to use for amplifying noise. One of:
- `gate_folding` (default) uses 2-qubit gate folding to amplify noise. If the noise factor requires amplifying only a subset of the gates, then these gates are chosen randomly.

- `gate_folding_front` uses 2-qubit gate folding to amplify noise. If the noise factor requires amplifying only a subset of the gates, then these gates are selected from the front of the topologically ordered DAG circuit.

- `gate_folding_back` uses 2-qubit gate folding to amplify noise. If the noise factor requires amplifying only a subset of the gates, then these gates are selected from the back of the topologically ordered DAG circuit.

- `pea` uses a technique called Probabilistic error amplification (PEA) to amplify noise. Refer to [Error suppression and mitigation techniques](/docs/guides/error-mitigation-and-suppression-techniques#probabilistic-error-amplification-pea) for the explanation of the method. | gate_folding / gate_folding_front / gate_folding_back / pea | gate_folding |\n", "| | | noise_factors | Noise factors to use for noise amplification. | list of floats; each float >= 1 | (1, 1.5, 2) for PEA, and (1, 3, 5) otherwise. |\n", - "| | | extrapolator | Noise factors to evaluate the fit extrapolation models at. This option does not affect execution or model fitting in any way; it only determines the points at which the `extrapolator`s are evaluated to be returned in the data fields called `evs_extrapolated` and `stds_extrapolated`. | one or more of `exponential`,`linear`, `double_exponential`,`polynomial_degree_(1 <= k <= 7)` | (`exponential`, `linear`) |\n", + "| | | extrapolator | Noise factors to evaluate the fit extrapolation models at. This option does not affect execution or model fitting in any way; it only determines the points at which the `extrapolator` objects are evaluated to be returned in the data fields called `evs_extrapolated` and `stds_extrapolated`. | one or more of `exponential`,`linear`, `double_exponential`,`polynomial_degree_(1 <= k <= 7)` | (`exponential`, `linear`) |\n", "| | pec_mitigation | | Whether to turn on Probabilistic Error Cancellation error mitigation method. Refer to [Error suppression and mitigation techniques](/docs/guides/error-mitigation-and-suppression-techniques#probabilistic-error-cancellation-pec) for the explanation of the method. | True/False | False |\n", "| | pec | max_overhead | The maximum circuit sampling overhead allowed, or `None` for no maximum. | None/ integer >1 | 100 |\n", "\n", diff --git a/docs/guides/monitor-job.ipynb b/docs/guides/monitor-job.ipynb index 0570de5cfd9..fa5577937e3 100644 --- a/docs/guides/monitor-job.ipynb +++ b/docs/guides/monitor-job.ipynb @@ -230,7 +230,7 @@ "id": "ae2820bc-c762-4d2e-944c-58cbc253acbe", "metadata": {}, "source": [ - "To view execution span information, review the metadata of the result returned by `SamplerV2`, which comes in the form of an `ExecutionSpans` object. This object is a list-like container containing subclass instances of `ExecutionSpan`s such as `SliceSpan`:" + "To view execution span information, review the metadata of the result returned by `SamplerV2`, which comes in the form of an `ExecutionSpans` object. This object is a list-like container containing instances of subclasses of `ExecutionSpan`, such as `SliceSpan`:" ] }, { diff --git a/docs/guides/primitive-input-output.ipynb b/docs/guides/primitive-input-output.ipynb index b380e33297c..87d56525492 100644 --- a/docs/guides/primitive-input-output.ipynb +++ b/docs/guides/primitive-input-output.ipynb @@ -355,7 +355,7 @@ " \n", "\n", "\n", - "Put simply, a single job returns a `PrimitiveResult` object and contains a list of one or more `PubResult`s. These `PubResult` objects then store the measurement data for each PUB that was submitted to the job.\n", + "Put simply, a single job returns a `PrimitiveResult` object and contains a list of one or more `PubResult` objects. These `PubResult` objects then store the measurement data for each PUB that was submitted to the job.\n", "\n", "Each `PubResult` possesses different formats and attributes based on the type of primitive that was used for the job. The specifics are explained below.\n", "\n", @@ -487,7 +487,7 @@ "source": [ "### Sampler output\n", "\n", - "When a Sampler job is completed successfully, the returned [`PrimitiveResult`](/docs/api/qiskit/qiskit.primitives.PrimitiveResult) object contains a list of [`SamplerPubResult`](/docs/api/qiskit/qiskit.primitives.SamplerPubResult)s, one per PUB. The data bins of these `SamplerPubResult`s are dict-like objects that contain one `BitArray` per `ClassicalRegister` in the circuit.\n", + "When a Sampler job is completed successfully, the returned [`PrimitiveResult`](/docs/api/qiskit/qiskit.primitives.PrimitiveResult) object contains a list of [`SamplerPubResult`](/docs/api/qiskit/qiskit.primitives.SamplerPubResult)s, one per PUB. The data bins of these `SamplerPubResult` objects are dict-like objects that contain one `BitArray` per `ClassicalRegister` in the circuit.\n", "\n", "The `BitArray` class is a container for ordered shot data. In more detail, it stores the sampled bitstrings as bytes inside a two-dimensional array. The left-most axis of this array runs over ordered shots, while the right-most axis runs over bytes.\n", "\n", @@ -584,7 +584,7 @@ "id": "514e0ac0-b42e-4f26-b608-c223dfed7915", "metadata": {}, "source": [ - "When a circuit contains more than one classical register, the results are stored in different `BitArray`s. The following example modifies the previous snippet by splitting the classical register into two distinct registers:" + "When a circuit contains more than one classical register, the results are stored in different `BitArray` objects. The following example modifies the previous snippet by splitting the classical register into two distinct registers:" ] }, { @@ -636,9 +636,9 @@ "id": "a65c6078-c5c2-4087-b57a-5680148ce333", "metadata": {}, "source": [ - "#### Leveraging `BitArray`s for performant post-processing\n", + "#### Leveraging `BitArray` objects for performant post-processing\n", "\n", - "Since arrays generally offer better performance compared to dictionaries, it is advisable to perform any post-processing directly on the `BitArray`s rather than on dictionaries of counts. The `BitArray` class offers a range of methods to perform some common post-processing operations:" + "Since arrays generally offer better performance compared to dictionaries, it is advisable to perform any post-processing directly on the `BitArray` objects rather than on dictionaries of counts. The `BitArray` class offers a range of methods to perform some common post-processing operations:" ] }, { diff --git a/docs/guides/qiskit-addons-cutting-gates.ipynb b/docs/guides/qiskit-addons-cutting-gates.ipynb index 48085abe97c..c060c885aa5 100644 --- a/docs/guides/qiskit-addons-cutting-gates.ipynb +++ b/docs/guides/qiskit-addons-cutting-gates.ipynb @@ -108,7 +108,7 @@ "id": "87b8819b-75d7-4a9e-b91a-00b6155fda9a", "metadata": {}, "source": [ - "Each of the [`CNOT`](/docs/api/qiskit/qiskit.circuit.library.CXGate) gates between qubits $q_0$ and $q_3$ introduce two SWAP gates after transpilation (assuming the qubits are connected in a straight line). To avoid this increase in depth, you can replace these distant gates with [`TwoQubitQPDGate`s](/docs/api/qiskit-addon-cutting/qpd-two-qubit-qpd-gate) using the [`cut_gates()`](/docs/api/qiskit-addon-cutting/qiskit-addon-cutting#cut_gates) method. This function also returns a list of [`QPDBasis`](../api/qiskit-addon-cutting/qpd-qpd-basis) instances - one for each decomposition." + "Each of the [`CNOT`](/docs/api/qiskit/qiskit.circuit.library.CXGate) gates between qubits $q_0$ and $q_3$ introduce two SWAP gates after transpilation (assuming the qubits are connected in a straight line). To avoid this increase in depth, you can replace these distant gates with [`TwoQubitQPDGate`](/docs/api/qiskit-addon-cutting/qpd-two-qubit-qpd-gate) objects using the [`cut_gates()`](/docs/api/qiskit-addon-cutting/qiskit-addon-cutting#cut_gates) method. This function also returns a list of [`QPDBasis`](../api/qiskit-addon-cutting/qpd-qpd-basis) instances - one for each decomposition." ] }, { diff --git a/docs/guides/qiskit-addons-cutting-wires.ipynb b/docs/guides/qiskit-addons-cutting-wires.ipynb index a8d995b4f60..8616d3697a4 100644 --- a/docs/guides/qiskit-addons-cutting-wires.ipynb +++ b/docs/guides/qiskit-addons-cutting-wires.ipynb @@ -156,7 +156,7 @@ "metadata": {}, "source": [ "\n", - " When a circuit is expanded through one or more wire cuts, the observable needs to be updated to account for the extra qubits that are introduced. The `qiskit-addon-cutting` package has a convenience function [`expand_observables()`](/docs/api/qiskit-addon-cutting/qiskit-addon-cutting#expand_observables), which takes `PauliList`s and the original and expanded circuits as arguments, and returns a new `PauliList`.\n", + " When a circuit is expanded through one or more wire cuts, the observable needs to be updated to account for the extra qubits that are introduced. The `qiskit-addon-cutting` package has a convenience function [`expand_observables()`](/docs/api/qiskit-addon-cutting/qiskit-addon-cutting#expand_observables), which takes `PauliList` objects and the original and expanded circuits as arguments, and returns a new `PauliList`.\n", "\n", " This returned `PauliList` will not contain any information about the original observable's coefficients, but these can be ignored until reconstruction of the final expectation value.\n", "" diff --git a/docs/guides/qiskit-addons-cutting.mdx b/docs/guides/qiskit-addons-cutting.mdx index cec17eab4e1..da8c024400d 100644 --- a/docs/guides/qiskit-addons-cutting.mdx +++ b/docs/guides/qiskit-addons-cutting.mdx @@ -11,7 +11,7 @@ Circuit cutting is a technique to increase the size of circuits that can run on ## Important terms -- **Subcircuits**: The set of circuits resulting from cutting gates in a `QuantumCircuit` and then separating the disconnected qubit subsets into smaller circuits. These circuits contain [`SingleQubitQPDGate`s](/docs/api/qiskit-addon-cutting/qpd-single-qubit-qpd-gate) and are used to instantiate each subexperiment. +- **Subcircuits**: The set of circuits resulting from cutting gates in a `QuantumCircuit` and then separating the disconnected qubit subsets into smaller circuits. These circuits contain [`SingleQubitQPDGate`](/docs/api/qiskit-addon-cutting/qpd-single-qubit-qpd-gate) objects and are used to instantiate each subexperiment. - **Subexperiment**: A term used to describe the unique circuit samples associated with a subcircuit, which are sent to a QPU for execution. diff --git a/docs/guides/qiskit-addons-utils.ipynb b/docs/guides/qiskit-addons-utils.ipynb index db29f24c563..62563ce7a61 100644 --- a/docs/guides/qiskit-addons-utils.ipynb +++ b/docs/guides/qiskit-addons-utils.ipynb @@ -81,7 +81,7 @@ "\n", "$$H = \\sum_{(j,k)\\in E} \\left(J_x X_jX_k + J_yY_jY_k + J_zZ_jZ_k\\right) + \\sum_{j\\in V} \\left(h_x X_j + h_y Y_j + h_z Z_j\\right) $$\n", "- A [`generate_time_evolution_circuit()`](../api/qiskit-addon-utils/problem-generators#generate_time_evolution_circuit) function, which constructs a circuit modeling the time evolution of a given operator.\n", - "- Three different [`PauliOrderStrategy`s](../api/qiskit-addon-utils/problem-generators#pauliorderstrategy) for enumerating between different Pauli string orderings. This is mostly helpful when used alongside graph coloring and can be used as arguments in both the `generate_xyz_hamiltonian()` and `generate_time_evolution_circuit()` functions.\n", + "- Three different [`PauliOrderStrategy`](../api/qiskit-addon-utils/problem-generators#pauliorderstrategy) objects for enumerating between different Pauli string orderings. This is mostly helpful when used alongside graph coloring and can be used as arguments in both the `generate_xyz_hamiltonian()` and `generate_time_evolution_circuit()` functions.\n", "\n", "\n", "\n", @@ -150,7 +150,7 @@ "source": [ "### Slicing\n", "\n", - "Lastly, the [`qiskit-addon-utils.slicing`](../api/qiskit-addon-utils/slicing) module contains functions and transpiler passes to work with creating circuit \"slices\", time-like partitions of a [`QuantumCircuit`](../api/qiskit/qiskit.circuit.QuantumCircuit) spanning across all qubits. These slices are primarily used for [operator backpropagation](/docs/guides/qiskit-addons-obp-get-started). The main four ways a circuit can be sliced are by gate type, depth, coloring, or [`Barrier`](../api/qiskit/circuit#barrier) instructions. The output of these slicing functions returns a list of [`QuantumCircuit`s](../api/qiskit/qiskit.circuit.QuantumCircuit). Sliced circuits can also be recombined using the [`combine_slices()`](../api/qiskit-addon-utils/slicing#combine_slices) function. Read the module's [API reference](../api/qiskit-addon-utils/slicing) for more information.\n", + "Lastly, the [`qiskit-addon-utils.slicing`](../api/qiskit-addon-utils/slicing) module contains functions and transpiler passes to work with creating circuit \"slices\", time-like partitions of a [`QuantumCircuit`](../api/qiskit/qiskit.circuit.QuantumCircuit) spanning across all qubits. These slices are primarily used for [operator backpropagation](/docs/guides/qiskit-addons-obp-get-started). The main four ways a circuit can be sliced are by gate type, depth, coloring, or [`Barrier`](../api/qiskit/circuit#barrier) instructions. The output of these slicing functions returns a list of [`QuantumCircuit`](../api/qiskit/qiskit.circuit.QuantumCircuit) objects. Sliced circuits can also be recombined using the [`combine_slices()`](../api/qiskit-addon-utils/slicing#combine_slices) function. Read the module's [API reference](../api/qiskit-addon-utils/slicing) for more information.\n", "\n", "Below are a few examples of how to create these slices using the following circuit:" ] diff --git a/docs/guides/represent-quantum-computers.ipynb b/docs/guides/represent-quantum-computers.ipynb index 03872f463bc..8bc7ec89412 100644 --- a/docs/guides/represent-quantum-computers.ipynb +++ b/docs/guides/represent-quantum-computers.ipynb @@ -375,7 +375,7 @@ "id": "b0195ba6", "metadata": {}, "source": [ - "Note that the `CXGate`s have been decomposed to `ecr` gates and single-qubit basis gates." + "Note that the `CXGate` objects have been decomposed to `ecr` gates and single-qubit basis gates." ] }, { diff --git a/docs/guides/simulate-with-qiskit-sdk-primitives.ipynb b/docs/guides/simulate-with-qiskit-sdk-primitives.ipynb index bf2b238f875..f078c91a584 100644 --- a/docs/guides/simulate-with-qiskit-sdk-primitives.ipynb +++ b/docs/guides/simulate-with-qiskit-sdk-primitives.ipynb @@ -180,7 +180,7 @@ "source": [ "#### Get the expected value from the result\n", "\n", - "The primitives result outputs an array of [`PubResult`s](/docs/api/qiskit/qiskit.primitives.PubResult#pubresult), where each item of the array is a `PubResult` object that contains in its data the array of evaluations corresponding to every circuit-observable combination in the PUB.\n", + "The primitives result outputs an array of [`PubResult`](/docs/api/qiskit/qiskit.primitives.PubResult#pubresult) objects, where each item of the array is a `PubResult` object that contains in its data the array of evaluations corresponding to every circuit-observable combination in the PUB.\n", "\n", "To retrieve the expectation values and metadata for the first (and in this case, only) circuit evaluation, we must access the evaluation [`data`](/docs/api/qiskit/qiskit.primitives.PubResult#data) for PUB 0:" ] diff --git a/docs/guides/transpile.mdx b/docs/guides/transpile.mdx index f9d9e9f1268..52773d59722 100644 --- a/docs/guides/transpile.mdx +++ b/docs/guides/transpile.mdx @@ -53,7 +53,7 @@ For an overview of transpiling using pass managers, see [Transpile with pass man ## Default transpilation -For a simpler, but less customizable, "out-of-the-box" way to use the transpiler, use the [`qiskit.compiler.transpile`](/docs/api/qiskit/compiler#qiskit.compiler.transpile) function. This generates and runs one of the preset `StagedPassManager`s based on, among other options, an `optimization_level` flag that can be set to 0, 1, 2, or 3. Higher levels generate more optimized circuits at the expense of longer transpilation times. +For a simpler, but less customizable, "out-of-the-box" way to use the transpiler, use the [`qiskit.compiler.transpile`](/docs/api/qiskit/compiler#qiskit.compiler.transpile) function. This generates and runs one of the preset `StagedPassManager` objects based on, among other options, an `optimization_level` flag that can be set to 0, 1, 2, or 3. Higher levels generate more optimized circuits at the expense of longer transpilation times. ## Next steps