diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/data_exchange_validation/test_steps/validate_no_notification_operational_intent.md b/monitoring/uss_qualifier/scenarios/astm/utm/data_exchange_validation/test_steps/validate_no_notification_operational_intent.md
index 38840bc23c..514870ec36 100644
--- a/monitoring/uss_qualifier/scenarios/astm/utm/data_exchange_validation/test_steps/validate_no_notification_operational_intent.md
+++ b/monitoring/uss_qualifier/scenarios/astm/utm/data_exchange_validation/test_steps/validate_no_notification_operational_intent.md
@@ -12,7 +12,7 @@ This step verifies when a flight is not created, it is also not notified by chec
 As per astm requirement, the notification should not be sent by a USS about an entity that could not be created in DSS
 to any USS. To verify that notification was indeed not sent, we need to wait and check up to a threshold to get confidence
 that USS did not send notification.
-The max duration for sending a notification is MaxRespondToSubscriptionNotification(5) seconds.
+The max duration for sending a notification in [SCD0085](../../../../../requirements/astm/f3548/v21.md) is MaxRespondToSubscriptionNotification(5) seconds.
 However, this duration is from time start - Receipt of subscription notification from DSS, which does not exist for this check.
 In this check we use time start when the test driver asked the USS to plan the failed flight.
 When checking noitification not sent, we should wait for the same duration that is used for when checking notification sent.