diff --git a/releasenotes/notes/fix-missing-pulse-lib-c370f5b9393d0df6.yaml b/releasenotes/notes/fix-missing-pulse-lib-c370f5b9393d0df6.yaml
index 96984181fb42..1e67e9c73bbe 100644
--- a/releasenotes/notes/fix-missing-pulse-lib-c370f5b9393d0df6.yaml
+++ b/releasenotes/notes/fix-missing-pulse-lib-c370f5b9393d0df6.yaml
@@ -3,9 +3,10 @@ fixes:
   - |
     Fixed a bug that results in an error when a user tries to load .calibration
     data of a gate in :class:`.Target` in a particular situation.
-    This occurs when the backend doesn't support pulse waveform payload, while
-    Qiskit doesn't have corresponding parametric pulse definition.
-    In this situation, Qiskit pulse object cannot be built, resulting in the failure in
-    parsing PulseQobj and the user encounters a meaningless error.
-    This error was suppressed, and the .calibration now returns None value instead,
-    which implies the calibration data is not properly supplied.
+    This occurs when the backend reports only partial calibration data, for
+    example referencing a waveform pulse in a command definition but not
+    including that waveform pulse in the pulse library. In this situation, the
+    Qiskit pulse object cannot be built, resulting in a failure to build the pulse
+    schedule for the calibration. Now when calibration data is incomplete
+    the :class:`.Target` treats it as equivalent to no calibration being reported
+    at all and does not raise an exception.