Change qpu complex wording

docs/faqs/max_execution_time.rst

@@ -86,6 +86,4 @@ Other limitations
 
 - Programs cannot exceed 750KB in size.
 - Inputs to jobs cannot exceed 64MB in size.
-- Open plan users are limited to 10 minutes of job execution time per month.  This is the time that the QPU
-   complex (including control software, control electronics, QPU, and so on) is engaged in
-   processing the job. Open plan users can track current progress toward the limit on the `Platform dashboard, <https://quantum-computing.ibm.com/>`__ `Jobs, <https://quantum-computing.ibm.com/jobs>`__ and `Account, <https://quantum-computing.ibm.com/account>`__ pages.
+- Open plan users can use up to 10 minutes of job execution time per month (reset on the first day of the month, UTC).  Job execution time is the amount of time that the system is dedicated to processing your job. You can track your monthly usage on the `Platform dashboard, <https://quantum-computing.ibm.com/>`__ `Jobs, <https://quantum-computing.ibm.com/jobs>`__ and `Account, <https://quantum-computing.ibm.com/account>`__ pages.

qiskit_ibm_runtime/options/options.py

@@ -62,10 +62,10 @@ class Options:
             for more information about the error mitigation methods used at each level.
 
         max_execution_time: Maximum execution time in seconds, which is based
-            on quantum time (not wall clock time). Quantum time is the time that
-            the QPU complex (including control software, control electronics, QPU, and so on)
-            is engaged in processing the job. If a job exceeds this time limit, it is forcibly cancelled.
-            Simulator jobs continue to use wall clock time because they do not have quantum time.
+            on job execution time (not wall clock time). Job execution time is 
+            the amount of time that the system is dedicated to processing your job. 
+            If a job exceeds this time limit, it is forcibly cancelled.
+            Simulator jobs continue to use wall clock time.
 
             Refer to the
             `Max execution time documentation

qiskit_ibm_runtime/runtime_job.py

@@ -664,9 +664,9 @@ def usage_estimation(self) -> Dict[str, Any]:
         """Return the usage estimation infromation for this job.
 
         Returns:
-            ``quantum_seconds`` which is the estimated quantum time
+            ``quantum_seconds`` which is the estimated job execution time
             of the job in seconds. Quantum time represents the time that
-            the QPU complex is occupied exclusively by the job.
+            the system is dedicated to processing your job.
         """
         if not self._usage_estimation:
             response = self._api_client.job_get(job_id=self.job_id())

qiskit_ibm_runtime/runtime_options.py

@@ -59,11 +59,9 @@ def __init__(
             job_tags: Tags to be assigned to the job. The tags can subsequently be used
                 as a filter in the :meth:`jobs()` function call.
             max_execution_time: Maximum execution time in seconds, which is based
-                on quantum time (not wall clock time). Quantum time is the time that
-                the QPU complex (including control software, control electronics, QPU, and so on)
-                is engaged in processing the job. If a job exceeds this time limit, it is forcibly
-                cancelled. Simulator jobs continue to use wall clock time because they do not have
-                quantum time.
+                on job execution time (not wall clock time). Job execution time is the amount of time that
+                the system is dedicated to processing your job. If a job exceeds this time limit, it is forcibly
+                cancelled. Simulator jobs continue to use wall clock time.
             session_time: Length of session in seconds.
         """
         self.backend = backend

releasenotes/notes/0.11/job-cost-estimation-d0ba83dbc95c3f67.yaml

@@ -2,5 +2,5 @@
 features:
   - |
     Added a new property, :meth:`~qiskit_ibm_runtime.RuntimeJob.usage_estimation`
-    that returns the estimated running time, ``quantum_seconds``. Quantum time 
-    represents the time that the QPU complex is occupied exclusively by the job.
+    that returns the estimated job execution time, ``quantum_seconds``. Job execution time 
+    represents the amount of time that the system is dedicated to processing your job.

releasenotes/notes/0.12/max-execution-time-definition-196cb6297693c0f2.yaml

@@ -1,8 +1,7 @@
 ---
 fixes:
   - |
-    The `max_execution_time` option is now based on quantum time instead of wall clock time. 
-    Quantum time is the time that the QPU complex 
-    (including control software, control electronics, QPU, and so on) 
-    is engaged in processing the job. If a job exceeds this time limit, it is forcibly cancelled.
-    Simulator jobs continue to use wall clock time because they do not have quantum time.
+    The `max_execution_time` option is now based on job execution time instead of wall clock time. 
+    Job execution time is the amount of time that the system is dedicated to processing your job. 
+    If a job exceeds this time limit, it is forcibly cancelled.
+    Simulator jobs continue to use wall clock time.