Merge pull request #295480 from prashantsaini4/docs-editor/ea-transfers-1740720283

Update EA transfers doc to remove incorrect information

Author: prmerger-automator[bot]

articles/cost-management-billing/manage/ea-transfers.md

@@ -62,7 +62,7 @@ When you request to transfer an old enterprise enrollment to a new enrollment, t
     - All APIs use either the old enrollment or the new one, not both, for reporting purposes. If you need reports from APIs for the old and new enrollments, you must create your own reports.
 - All Azure services, subscriptions, accounts, departments, and the entire enrollment structure, including all EA department administrators, transfer to a new target enrollment.
 - The enrollment status is set to `Transferred` for the old enrollment. The old enrollment that was transferred is available for historic usage reporting purposes only.
-- You can't add roles or subscriptions to the old enrollment that was transferred. `Transferred` status prevents any new usage against the old enrollment.
+- You cannot create new subscriptions under the old enrollment that was transferred. `Transferred` status prevents any new usage against the old enrollment.
 - Any remaining Azure Prepayment balance in the agreement is lost, including future terms.
 - If the old enrollment that you're transferring from has any reservation purchases, the historic (past) reservation purchasing fee remains in the old source enrollment. All future purchasing fees transfer to the new enrollment. Additionally, all reservation benefits are transferred across for use in the new enrollment.
 - The historic marketplace one-time purchase fee and any monthly fixed fees already incurred on the old enrollment aren't transferred to the new enrollment. Consumption-based marketplace charges are transferred.