diff --git a/docs/guides/represent-quantum-computers.ipynb b/docs/guides/represent-quantum-computers.ipynb
index 71b1b201c55..93c2904c84e 100644
--- a/docs/guides/represent-quantum-computers.ipynb
+++ b/docs/guides/represent-quantum-computers.ipynb
@@ -27,7 +27,7 @@
     "Import the necessary libraries and instantiate the system or simulator:\n",
     "In order to convert an abstract circuit to an ISA circuit that can run on a specific system, the transpiler needs certain information about the system.  Typically, this information is stored in the [`Backend`](/api/qiskit/qiskit.providers.Backend#backend) or [`Target`](/api/qiskit/qiskit.transpiler.Target#target) provided to the transpiler, and no further information is needed. However, you can also explicitly provide information for the transpiler to use, for example, if you have a specific use case, or if you believe this information will help the transpiler generate a more optimized circuit.\n",
     "\n",
-    "On this page, we show several examples of passing system information to the transpiler. For our examples, we'll use the target from the [`FakeSherbrooke`](/api/qiskit-ibm-runtime/qiskit_ibm_runtime.fake_provider.FakeSherbrooke#fakesherbrooke) mock backend."
+    "This topic shows several examples of passing system information to the transpiler. These examples use the target from the [`FakeSherbrooke`](/api/qiskit-ibm-runtime/qiskit_ibm_runtime.fake_provider.FakeSherbrooke#fakesherbrooke) mock backend."
    ]
   },
   {
@@ -48,8 +48,8 @@
    "id": "4064b5ad-8a3a-462b-ae30-29576230c084",
    "metadata": {},
    "source": [
-    "For our example circuit, we'll use an instance of [`EfficientSU2`](/api/qiskit/qiskit.circuit.library.EfficientSU2#efficientsu2) from Qiskit's circuit library.\n",
-    "In the following cell, we decompose the circuit before drawing it to show its gate structure."
+    "The example circuit uses an instance of [`EfficientSU2`](/api/qiskit/qiskit.circuit.library.EfficientSU2#efficientsu2) from Qiskit's circuit library.\n",
+    "The following cell decomposes the circuit before drawing it to show its gate structure."
    ]
   },
   {
@@ -86,10 +86,7 @@
    "id": "b133229c-0146-4feb-a366-548d175b858e",
    "metadata": {},
    "source": [
-    "<span id=\"default-config\"></span>\n",
-    "## Default configuration\n",
-    "\n",
-    "This example uses the default `optimization_level=1` to transpile to the `backend`'s `target`, which provides all the information needed to convert the circuit to one that will run on the system.  (Note that if a `target` is specified in the `transpile` function, this will override the target from the `backend`.)"
+    "This example uses default settings to transpile to the `backend`'s `target`, which provides all the information needed to convert the circuit to one that will run on the system. "
    ]
   },
   {
@@ -116,7 +113,7 @@
     "from qiskit.transpiler.preset_passmanagers import generate_preset_pass_manager\n",
     "\n",
     "pass_manager = generate_preset_pass_manager(\n",
-    "    optimization_level=1, target=target, seed_transpiler=12345\n",
+    "    target=target, seed_transpiler=12345\n",
     ")\n",
     "qc_t_target = pass_manager.run(qc)\n",
     "qc_t_target.draw(\"mpl\", idle_wires=False, fold=-1)"
@@ -142,7 +139,7 @@
     "The qubits from our abstract circuits are called _virtual qubits_ and those on the coupling map are _physical qubits_. The transpiler provides a mapping between virtual and physical qubits. One of the first steps in transpilation, the _layout_ stage, performs this mapping.\n",
     "\n",
     "<Admonition type=\"note\">\n",
-    "Although the routing stage is intertwined with the _layout_ stage — which selects the actual qubits — by default, we will consider them as separate stages for simplicity. The combination of routing and layout is called _qubit mapping_.  Learn more about these stages in the [Transpiler stages](transpiler-stages) topic.\n",
+    "Although the routing stage is intertwined with the _layout_ stage — which selects the actual qubits — by default, this topic treats as separate stages for simplicity. The combination of routing and layout is called _qubit mapping_.  Learn more about these stages in the [Transpiler stages](transpiler-stages) topic.\n",
     "</Admonition>\n",
     "\n",
     "Pass the `coupling_map` keyword argument to see its effect on the transpiler:"
@@ -407,7 +404,7 @@
    "id": "90cca3a8-ca25-4795-a22f-57ba6d8cfcaa",
    "metadata": {},
    "source": [
-    "The output displays the duration of the gate (in seconds) and its error rate. To reveal error information to the transpiler, we will build our own target model with the `basis_gates` and `coupling_map` from above and populate it with error values from the backend `FakeSherbrooke`."
+    "The output displays the duration of the gate (in seconds) and its error rate. To reveal error information to the transpiler, build a target model with the `basis_gates` and `coupling_map` from above and populate it with error values from the backend `FakeSherbrooke`."
    ]
   },
   {
@@ -473,7 +470,7 @@
    "id": "f8b516be-805d-4d0b-92f9-44d3fbe3b51f",
    "metadata": {},
    "source": [
-    "Because we included error information, the `VF2PostLayout` pass tries to find the optimal qubits to use, resulting in the same circuit that we found originally with the same physical qubits."
+    "Because error information was included, the `VF2PostLayout` pass tries to find the optimal qubits to use, resulting in the same circuit that was found originally with the same physical qubits."
    ]
   },
   {