diff --git a/monitoring/uss_qualifier/scenarios/astm/utm/dss/synchronization/subscription_synchronization.md b/monitoring/uss_qualifier/scenarios/astm/utm/dss/synchronization/subscription_synchronization.md
index c813041ef4..a41e3424bd 100644
--- a/monitoring/uss_qualifier/scenarios/astm/utm/dss/synchronization/subscription_synchronization.md
+++ b/monitoring/uss_qualifier/scenarios/astm/utm/dss/synchronization/subscription_synchronization.md
@@ -28,16 +28,13 @@ A `resources.communications.AuthAdapterResource` containing a second set of vali
 
 This second set of credentials is required to validate that the DSS properly synchronizes the manager of a subscription to other DSS instances.
 
-The participant under test is responsible for providing this second set of credentials along the primary ones used in most other scenarios.
+The test designer should provide this second set of credentials when full testing of manager synchronization behavior is desired.
 
 #### Credential requirements
 
 In general, these test credentials may be in all points equal to the ones used by the `AuthAdapterResource` that is
 provided to the `dss` resources above, except for the value contained in the `sub` claim of the token.
 
-For the purpose of this scenario, these credentials must be allowed to create, modify and delete subscriptions on the DSS,
-as well as querying them.
-
 Note that most checks in this scenario will work if the second set of credentials is not provided.
 
 ##### Required scope
@@ -46,7 +43,7 @@ For the purpose of this scenario, the `second_utm_auth` resource must provide ac
 
 * `utm.strategic_coordination`
 
-##### Separate subscription
+##### Separate subject
 
 Note that the subject (or 'sub' claim) of the token that will be obtained for this resource
 MUST be different from the one of the `dss` resources mentioned above:
@@ -290,7 +287,7 @@ As a result, the DSS pool under test is failing to meet **[astm.f3548.v21.DSS002
 
 ## [Cleanup](../clean_workspace.md)
 
-This step ensures that no subscriptions with the known test IDs exists in the DSS.
+This step ensures that no subscriptions with the known test IDs remain in the DSS by deleting them at this point if they do exist.
 
 This includes the main test subscription used in this test, as well as the extra subscription
 used for testing the `manager` field sync, if the test is configured to test for it.