Merge branch 'main' into double-slice-span

.github/workflows/neko.yml

@@ -0,0 +1,18 @@
+name: Qiskit Neko Integration Tests
+on:
+  push:
+  pull_request:
+    branches: ['main', 'stable/*']
+concurrency:
+  group: ${{ github.repository }}-${{ github.ref }}-${{ github.head_ref }}-${{ github.workflow }}
+  # Only cancel in PR mode.  In push mode, don't cancel so we don't see spurious test "failures".
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
+jobs:
+  neko:
+    if: github.repository_owner == 'Qiskit'
+    name: Qiskit Neko Integration Tests
+    runs-on: ubuntu-latest
+    steps:
+      - uses: Qiskit/qiskit-neko@main
+        with:
+          test_selection: backend

qiskit_ibm_runtime/options/zne_options.py

@@ -65,7 +65,7 @@ class ZneOptions:
         Technical note: for single observables with multiple basis terms it might turn out that
         multiple extrapolation methods are used in *the same* expectation value, for example, ``XX``
         gets linearly extrapolated but ``XY`` gets exponentially extrapolated in the observable
-        ``{"XX": 0.5, "XY": 0.5}``. Let's call this a *hetergeneous fit*. The data from (2) is
+        ``{"XX": 0.5, "XY": 0.5}``. Let's call this a *heterogeneous fit*. The data from (2) is
         evaluated from heterogeneous fits by selecting the best fit for every individual distinct
         term, whereas data from (1) is evaluated from forced homogenous fits, one for each provided
         extrapolator. If your work requires a nuanced distinction in this regard, we presently