fix tagging

Qiskit · Jan 10, 2025 · de3bc28 · de3bc28
1 parent 2b23b15
commit de3bc28
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/guides/execution-modes.mdx b/docs/guides/execution-modes.mdx
@@ -73,7 +73,7 @@ Test table:
 |                                             |         |   |   |   |
 |                                             |         |   |   |   |
 
-
+<span id="best-practices"></span>
 ### Recommendations and best practices
 
 Generally, you can use batch mode unless you have workloads that don’t have all inputs ready at the outset.
@@ -88,7 +88,7 @@ To ensure the most efficient use of the execution modes, the following practices
 
     A job's QPU time is listed in the **Usage** column on the IBM Quantum Platform [Workloads](https://quantum.ibm.com/workloads) page, or you can  query it by running this command: `job.metrics()["usage"]["quantum_seconds"]` in `qiskit-ibm-runtime`.
 
-- If each of your jobs consumes more than one minute of QPU time, or if combining jobs is not practical, you can still run multiple jobs in parallel. Every job goes through both classical and quantum processing. While a QPU can process only one job at a time, up to five classical jobs can be processed in parallel. You can take advantage of this by submitting multiple jobs in [batch](/guides/run-jobs-batch#partition) or [session](/guides//guides/run-jobs-session#two-vqe) execution mode.
+- If each of your jobs consumes more than one minute of QPU time, or if combining jobs is not practical, you can still run multiple jobs in parallel. Every job goes through both classical and quantum processing. While a QPU can process only one job at a time, up to five classical jobs can be processed in parallel. You can take advantage of this by submitting multiple jobs in [batch](/guides/run-jobs-batch#partition) or [session](/guides/run-jobs-session#two-vqe) execution mode.
 
 The above are general guidelines, and you should tune your workload to find the optimal ratio, especially when using sessions. For example, if you are using a session to get exclusive access to a backend, consider breaking up large jobs into smaller ones and running them in parallel. This might be more cost-effective because it can reduce wall clock time.