Restructure usage page

Author: beckykd

docs/guides/_toc.json

@@ -408,7 +408,7 @@
               "url": "/guides/monitor-job"
             },
             {
-              "title": "Estimate job run time",
+              "title": "Workload usage",
               "url": "/guides/estimate-job-run-time"
             },
             {

docs/guides/choose-execution-mode.mdx

@@ -72,5 +72,5 @@ In this case, all jobs (which are related but independant) are available at the
 <Admonition type="tip" title="Recommendations">
     - [Run a job in batch mode.](/guides/run-jobs-batch/)
     - [Run a job in session mode.](/guides/run-jobs-session)
-    - [Estimate job run time.](/guides/estimate-job-run-time)
+    - [Workload usage.](/guides/estimate-job-run-time)
 </Admonition>

docs/guides/estimate-job-run-time.mdx

@@ -1,10 +1,43 @@
 ---
-title: Estimate job run time
-description: Estimate how long a job that uses a primitive will take to run
+title: Workload usage
+description: Explains what usage is and how to estimeate how long a job that uses a primitive will take to run
 
 ---
 
-# Estimate job run time
+<span id="usage"></span>
+# Workload usage
+
+Usage is a measurement of the amount of time the QPU is locked for your workload, and it is calculated differently, depending on which execution mode you're using.
+
+* Session usage is the time from when the first job starts until the session goes inactive, is closed, or when its last job completes, whichever happens last. It includes both classical and quantum time.
+* Batch usage is the sum of quantum time of all jobs in the batch.
+* Single job usage is the quantum time the job uses in processing.
+
+The usage reported on the dashboard or by using the API is the time a QPU is locked for your workload. Failed or canceled jobs count toward your usage in certain circumstances - see the [Failed and canceled jobs](#failed-job) section for details.
+
+Your usage has different impacts, depending on which channel you're using:
+
+- For Qiskit Runtime on IBM Cloud users, the usage determines how much the job costs.  See [Manage cost](/guides/manage-cost#manage-cost) for details.
+- For IBM Quantum Platform users, this translates to shares. The [fair-share scheduler](/guides/fair-share-scheduler) prioritizes instances with the most shares left. Thus, the higher your usage, the longer your next job stays in the queue.
+
+<span id="failed-job"></span>
+## Usage for failed and canceled jobs
+
+When a job is failed or canceled, the reported usage is as follows:
+
+* Job or batch mode: The reported usage is the time the QPU was locked for executing your workload until the time it failed or was canceled. Therefore, if the failure or cancellation occurred before the lock, the reported usage is zero. Otherwise, the workload's reported usage is the value that Qiskit Runtime returns as `consumed`. Thus, some failed jobs do not appear in your reported usage and others do.
+
+* Session mode: The reported usage is the wall-clock time from the when the first job started executing in the session until the session terminates, regardless of the number of jobs that fail or are canceled.
+
+## Determine a workload's actual usage
+
+After a workload has completed, there are several ways to view its actual usage:
+
+- On the IBM Quantum Platform [Workloads table](https://quantum.ibm.com/workloads) in the Usage column.  From the Home page, click *View all* on the Recent workloads table.  The Usage column shows actual usage for completed workloads.
+- Run [`batch.usage()`](/api/qiskit-ibm-runtime/batch#usage) or [`session.usage()`](/api/qiskit-ibm-runtime/session#usage) in `qiskit-ibm-runtime` 0.30 or later.  If using an older version of `qiskit-ibm-runtime` (>= 0.23 and < 0.30), the usage can be still be found in `session.details()["usage_time"]` and `batch.details()["usage_time"]`.
+- Call the [GET usage](/api/runtime/tags/usage#tags__usage) REST API directly. The reported usage is the `elapsed_time` value returned by the `GET /sessions/{id}` endpoint, for both batch and session workloads.
+
+## Estimate workload usage
 
 After submitting a job to the IBM Quantum&trade; channel, you can see an estimation for how much _quantum time_ the job will take to run by using `job.usage_estimation`.  Alternatively, you can [view this information on the IBM Quantum Platform user interface](#view-usage).
 
@@ -59,47 +92,6 @@ Output:
 {'quantum_seconds': 4.1058720028432445}
 ```
 
-<span id="usage"></span>
-## Workload usage
-
-Usage is a measurement of the amount of time the QPU is locked for your workload, and it is calculated differently, depending on which execution mode you're using.
-
-* Session usage is the time from when the first job starts until the session goes inactive, is closed, or when its last job completes, whichever happens last. It includes both classical and quantum time.
-* Batch usage is the sum of quantum time of all jobs in the batch.
-* Single job usage is the quantum time the job uses in processing.
-
-The usage reported on the dashboard or by using the API is the time a QPU is locked for your workload. Failed or canceled jobs count toward your usage in certain circumstances - see the [Failed and canceled jobs](#failed-job) section for details.
-
-Your usage has different impacts, depending on which channel you're using:
-
-- For Qiskit Runtime on IBM Cloud users, the usage determines how much the job costs.  See [Manage cost](/guides/manage-cost#manage-cost) for details.
-- For IBM Quantum Platform users, this translates to shares. The [fair-share scheduler](/guides/fair-share-scheduler) prioritizes instances with the most shares left. Thus, the higher your usage, the longer your next job stays in the queue.
-
-<span id="failed-job"></span>
-### Usage for failed and canceled jobs
-
-When a job is failed or canceled, the reported usage is as follows:
-
-* Job or batch mode: The reported usage is the time the QPU was locked for executing your workload until the time it failed or was canceled. Therefore, if the failure or cancellation occurred before the lock, the reported usage is zero. Otherwise, the workload's reported usage is the value that Qiskit Runtime returns as `consumed`. Thus, some failed jobs do not appear in your reported usage and others do.
-
-* Session mode: The reported usage is the wall-clock time from the when the first job started executing in the session until the session terminates, regardless of the number of jobs that fail or are canceled.
-
-### Determine a workload's actual usage
-
-After a workload has completed, there are several ways to view its actual usage:
-
-- On the IBM Quantum Platform [Workloads table](https://quantum.ibm.com/workloads) in the Usage column.  From the Home page, click *View all* on the Recent workloads table.  The Usage column shows actual usage for completed workloads.
-- Run [`batch.usage()`](/api/qiskit-ibm-runtime/batch#usage) or [`session.usage()`](/api/qiskit-ibm-runtime/session#usage) in `qiskit-ibm-runtime` 0.30 or later.  If using an older version of `qiskit-ibm-runtime` (>= 0.23 and < 0.30), the usage can be still be found in `session.details()["usage_time"]` and `batch.details()["usage_time"]`.
-- Call the [GET usage](/api/runtime/tags/usage#tags__usage) REST API directly. The reported usage is the `elapsed_time` value returned by the `GET /sessions/{id}` endpoint, for both batch and session workloads.
-
-<span id="view-usage"></span>
-### View the estimated workload (job) usage
-
-After a workload is submitted but before it completes, you can view its estimated usage (how much quantum time the workload will take to run) in two places on IBM Quantum Platform:
-
-- On the [Workloads table](https://quantum.ibm.com/workloads) in the Usage column.  From the Home page, click *View all* on the Recent workloads table.  The Usage column shows the estimated usage for pending workloads.
-- On the workload's details page. From the [Dashboard](https://quantum.ibm.com/) or [Workloads table](https://quantum.ibm.com/workloads), click the ID to open its details page.  The estimated usage is shown in the Status timeline.
-
 ## Next steps
 
 <Admonition type="tip" title="Recommendations">

docs/guides/execute-on-hardware.mdx

@@ -50,7 +50,7 @@ expectation values of observables corresponding to physical quantities or cost f
 
 ### Manage jobs
 * [Monitor or cancel a job](./monitor-job)
-* [Estimate job run time](./estimate-job-run-time)
+* [Workload usage](./estimate-job-run-time)
 * [Minimize job run time](./minimize-time)
 * [Maximum execution time](./max-execution-time)
 * [Job limits](./job-limits)

docs/guides/manage-cost.mdx

@@ -60,7 +60,7 @@ These are the columns relevant to cost:
 
 ## Estimate the cost
 
-You can estimate how long a job will run, and therefore its cost, by estimating the job run time.  For details, see the [Estimate job run time](estimate-job-run-time) topic.
+You can estimate how long a job will run, and therefore its cost, by estimating the job run time.  For details, see the [Workload usage](estimate-job-run-time) topic.
 
 ## Set up spending notifications
 

docs/guides/max-execution-time.mdx

@@ -76,6 +76,6 @@ For instructions to work with these values, see [Run jobs in a session.](./run-j
 ## Next steps
 
 <Admonition type="tip" title="Recommendations">
-    - [Estimate job run time](estimate-job-run-time).
+    - [Workload usage](estimate-job-run-time).
     - Review these tips: [Minimize job run time](minimize-time).
 </Admonition>

docs/guides/minimize-time.mdx

@@ -17,6 +17,6 @@ There are several ways you can limit the amount of quantum time spent processing
 ## Next steps
 
 <Admonition type="tip" title="Recommendations">
-    - [Estimate job run time](estimate-job-run-time).
+    - [Workload usage](estimate-job-run-time).
     - Explore error mitigation in the  [Cost functions](https://learning.quantum.ibm.com/course/variational-algorithm-design/cost-functions) course.
 </Admonition>