followup fixes to QESEM pr: remove latin abbreviations (#2607)

Co-authored-by: Arnau Casau I Playa <[email protected]>

docs/guides/qedma-qesem.ipynb

@@ -241,8 +241,8 @@
     "<Admonition type=\"note\">QESEM will end its run when it reaches the target precision or when it reaches `max_execution_time`, whichever comes first. </Admonition>\n",
     "\n",
     "- `estimate_time_only` - This flag enables users to obtain an estimate for the QPU time required to execute the circuit with QESEM.\n",
-    "    - If set to `\"analytical\"`, an upper bound of the QPU time is calculated without consuming any QPU usage. This estimation has a 30-minute resolution (e.g., 30 minutes, 60 minutes, 90 minutes, etc.). It is typically pessimistic, and can only be obtained for single Pauli observables or sums of Paulis without intersecting supports (e.g. Z0+Z1). It is primarily useful for comparing the complexity levels of different parameters provided by the user (circuit, accuracy, etc.).\n",
-    "    - To obtain a more accurate QPU time estimation, set this flag to `\"empirical\"`. Although this option requires running a small number of circuits, it provides a significantly more accurate QPU time estimation. This estimation has a 5-minute resolution (e.g., 20 minutes, 25 minutes, 30 minutes, etc.). The user may choose to run the empirical time estimation in either batch or session mode. For more details, please see the `execution_mode` description. For example, in batch mode, empirical time estimation will consume less than 10 minutes of QPU time.\n",
+    "    - If set to `\"analytical\"`, an upper bound of the QPU time is calculated without consuming any QPU usage. This estimation has a 30-minute resolution (for example, 30 minutes, 60 minutes, 90 minutes, and so forth). It is typically pessimistic, and can only be obtained for single Pauli observables or sums of Paulis without intersecting supports (for example, Z0+Z1). It is primarily useful for comparing the complexity levels of different parameters provided by the user (circuit, accuracy, and so on).\n",
+    "    - To obtain a more accurate QPU time estimation, set this flag to `\"empirical\"`. Although this option requires running a small number of circuits, it provides a significantly more accurate QPU time estimation. This estimation has a 5-minute resolution (for example, 20 minutes, 25 minutes, 30 minutes, and so on). The user may choose to run the empirical time estimation in either batch or session mode. For more details, please see the `execution_mode` description. For example, in batch mode, empirical time estimation will consume less than 10 minutes of QPU time.\n",
     "\n",
     "- `max_execution_time`: Allows you to limit the QPU time, specified in seconds, to be used for the entire QESEM process. Since the final QPU time required to reach the target accuracy is determined dynamically during the QESEM job, this parameter enables you to limit the cost of the experiment. If the dynamically-determined QPU time is shorter than the time allocated by the user, this parameter will not affect the experiment. The `max_execution_time` parameter is particularly useful in cases where the analytical time estimate provided by QESEM before the job starts is too pessimistic and the user wants to initiate a mitigation job anyway. After the time limit it reached, QESEM stops sending new circuits. Circuits that have already been sent continue running (so the total time may surpass the limit by up to 30 minutes), and the user receives the processed results from the circuits that ran up to that point. If you want to apply a QPU time limit shorter than the analytical time estimate, consult with Qedma to obtain an estimate for the accuracy achievable within the time limit.\n",
     "\n",