diff --git a/docs/run/configure-runtime-compilation.mdx b/docs/run/configure-runtime-compilation.mdx
index f4da6c8360..672c12dd2b 100644
--- a/docs/run/configure-runtime-compilation.mdx
+++ b/docs/run/configure-runtime-compilation.mdx
@@ -8,9 +8,9 @@ description: How to configure runtime compilation in Qiskit Runtime.
 
 Runtime compilation techniques optimize and transform your circuit to minimize errors. Runtime compilation adds some classical pre-processing overhead to your overall runtime. Therefore, it is important to achieve a balance between perfecting your results and ensuring that your job completes in a reasonable amount of time.
 
-Primitives let you employ runtime compilation by setting the optimization level (`optimization_level` option) and by choosing advanced runtime compilation options.
+Primitives let you employ runtime compilation by by choosing advanced runtime compilation options and, for Estimator V2, by setting the optimization level (`optimization_level`) option.
 
-<admonition type="note">V2 primitives support optimization levels 0 and 1 only.</admonition>
+<admonition type="note">Estimator V2 supports optimization levels 0 and 1 only. Sampler V2 does not support setting the optimization level.</admonition>
 
 <Admonition type="caution" title="Important">
 To ensure faster and more efficient results, as of 1 March 2024, circuits and observables need to be transformed to only use instructions supported by the system (referred to as *instruction set architecture (ISA)* circuits and observables) before being submitted to the Qiskit Runtime primitives.  See the [transpilation documentation](../transpile) for instructions to transform circuits.  Due to this change, the primitives will no longer perform layout or routing operations.  Consequently, transpilation options referring to those tasks will no longer have any effect. By default, all primitives except Sampler V2 still optimize the input circuits. To bypass all optimization, set `optimization_level=0`.
@@ -27,15 +27,14 @@ service = QiskitRuntimeService(channel="ibm_cloud", channel_strategy="q-ctrl")
 The `optimization_level` setting specifies how much optimization to perform on the circuits. Higher levels generate more optimized circuits, at the expense of longer compile times.
 
 <Admonition>
-  In primitive version 1, optimization levels 2 and 3 behave identically to level 1.  V2 primitives do not accept levels higher than 1. 
+  In primitive version 1, optimization levels 2 and 3 behave identically to level 1.  Estimator V2 does not accept levels higher than 1.
 </Admonition>
 
-
 <Table>
   <thead>
     <Tr>
       <Th>Optimization Level</Th>
-      <Th>Estimator & Sampler</Th>
+      <Th>Estimator & Sampler (V1)</Th>
     </Tr>
   </thead>
   <tbody>
@@ -43,10 +42,6 @@ The `optimization_level` setting specifies how much optimization to perform on t
       <Td>0</Td>
       <Td>
         No optimization: typically used for hardware characterization or debugging
-
-        - Basis translation
-        - Layout (as specified)
-        - Routing (stochastic swaps)
       </Td>
     </Tr>
     <Tr>