Removing unreferenced file and description per PR review

monitoring/uss_qualifier/scenarios/astm/utm/data_exchange_validation/get_op_data_validation.md

@@ -40,26 +40,26 @@ Both USSs are requested to remove all flights from the area under test.
 
 ## Successfully plan flight near an existing flight test case
 ### [Control_uss plans flight 2 test step](../../../flight_planning/plan_flight_intent.md)
-Flight 2 on time range A should be successfully planned by the control USS.
+Flight 2 should be successfully planned by the control USS.
 
 ### [Validate flight 2 sharing test step](../validate_shared_operational_intent.md)
 Validate that flight 2 is planned
 
-### [Validate no notification pushed for flight 2](../validate_not_shared_operational_intent.md)
+### [Validate no notification pushed for flight 2](test_steps/validate_no_notification_operational_intent.md)
 There should be no subscription by tested_uss to trigger notification of flight 2.
 This will ensure that while planning a nearby flight tested_uss will need to make a GET request to control_uss for flight 2 details.
 If this notification was pushed, the GET operational intent data validation test cannot be done.
 
 ### [Tested_uss plans flight 1 test step](../../../flight_planning/plan_flight_intent.md)
-The test driver attempts to plan flight 1 on time range A via the tested USS. It checks if any conflicts with flight 2
+The test driver attempts to plan flight 1 via the tested USS. It checks if any conflicts with flight 2
 which is of equal priority and came first.
 
 ### [Validate flight 1 sharing test step](../validate_shared_operational_intent.md)
 Validate flight 1 is planned.
 
 ### [Validate flight2 GET interaction test step](test_steps/validate_get_operational_intent.md)
 Tested_uss needs to make GET request for obtaining details of flight 2.
-In a previous step, we checked there was no notification of flight 2 to tested_uss.
+In a previous step(Validate no notification pushed for flight 2), we checked there was no notification of flight 2 to tested_uss.
 
 ### [Validate flight1 Notification sent to Control_uss test step](test_steps/validate_notification_operational_intent.md)
 Tested_uss notifies flight 1 to Control_uss, due to its subscription through flight 2.
@@ -72,27 +72,27 @@ Teardown
 
 ## Flight planning prevented due to invalid data sharing test case
 ### [Control_uss plans flight 2, sharing invalid operational intent data test step](../../../flight_planning/plan_flight_intent.md)
-Flight 2 on time range A should be successfully planned by the control_uss.
+Flight 2 should be successfully planned by the control_uss.
 The control_uss, which is mock_uss is instructed to share invalid data with other USS, for negative test.
 
 ### [Validate flight 2 shared operational intent with invalid data test step](test_steps/validate_sharing_operational_intent_but_with_invalid_interuss_data.md)
 Validate that flight 2 is shared with invalid data as a modified behavior is injected by uss_qualifier for a negative test.
 
-### [Validate no notification pushed for flight 2](../validate_not_shared_operational_intent.md)
+### [Validate no notification pushed for flight 2](test_steps/validate_no_notification_operational_intent.md)
 There should be no subscription by tested_uss to trigger notification of flight 2.
 This will ensure that while planning a nearby flight tested_uss will need to make a GET request to control_uss for flight 2 details.
 If this notification was pushed, the GET operational intent data validation test cannot be carried out.
 
 ### [Test_uss attempts to plan flight 1, expect failure test step](test_steps/plan_flight_intent_expect_failed.md)
-The test driver attempts to plan the flight 1 on time range A via the tested_uss. It checks if any conflicts with flight 2
+The test driver attempts to plan the flight 1 via the tested_uss. It checks if any conflicts with flight 2
 which is of equal priority and came first.
 
 ### [Validate flight 1 not shared by tested_uss test step](../validate_not_shared_operational_intent.md)
 Validate flight 1 is not shared with DSS, as plan failed.
 
 ### [Validate flight 2 GET interaction test step](test_steps/validate_get_operational_intent.md)
 Tested_uss needs to make GET request for obtaining details of flight 2 from control_uss.
-In a previous step, we checked there was no notification of flight 2 to tested_uss.
+In a previous step(Validate no notification pushed for flight 2), we checked there was no notification of flight 2 to tested_uss.
 Hence USS will have to obtain details using GET request.
 
 ### [Validate flight 1 Notification not sent to Control_uss test step](test_steps/validate_no_notification_operational_intent.md)