docs(subscriptions): tighten prose into leads + bullets

Author: dev-jodee

apps/docs/content/docs/en/payments/subscriptions/close-subscription-authority.mdx

@@ -8,15 +8,11 @@ delegate for a user's token account. Close it when the user no longer has active
 fixed delegations, recurring delegations, or subscription delegations for that
 mint.
 
-Closing the account returns its rent to the account's lamport funder. The funder
-is usually the user, but it can be any payer that funded the Subscription
-Authority account. If any active delegation still depends on the authority,
-close those delegations first.
-
-Closing does not clear the SPL Token delegate approval on the user's token
-account. Once the Subscription Authority PDA is gone that approval is inert —
-nothing can move funds with it — but it stays recorded on the token account
-until the user revokes it explicitly. See
+Closing returns the account's rent to its funder (the user, or whichever payer
+funded it). Close any active delegations first.
+
+Closing does **not** clear the SPL Token delegate approval. Once the PDA is gone
+the approval is inert, but it stays on the token account until revoked — see
 [Revoke The Delegate Approval](#revoke-the-delegate-approval).
 
 ## Close The Authority
@@ -83,13 +79,10 @@ until the user revokes it explicitly. See
 
 ## Revoke The Delegate Approval
 
-Closing the Subscription Authority leaves the delegate approval on the user's
-token account. That approval is harmless once the PDA is closed, but the user
-can clear it — returning the token account to a clean state — with
-`RevokeSubscriptionAuthority`. It calls the token program's `Revoke` and is
-signed by the user, so it works whether or not the Subscription Authority still
-exists. Send it on its own, or in the same transaction as
-`CloseSubscriptionAuthority`.
+`RevokeSubscriptionAuthority` clears the leftover delegate approval from the
+user's token account. It calls the token program's `Revoke`, signed by the user,
+so it works whether or not the Subscription Authority still exists. Send it
+standalone or alongside `CloseSubscriptionAuthority`.
 
 <Tabs items={["TypeScript", "Rust"]}>
   <Tab value="TypeScript">

apps/docs/content/docs/en/payments/subscriptions/overview.mdx

@@ -46,18 +46,17 @@ The program supports three authorization models:
 
 ## Supported Tokens
 
-The program supports tokens created with both SPL Token and Token-2022,
-including Token-2022 mints that configure a `TransferHook` (for example, PYUSD).
-On each delegated transfer the program forwards the mint's hook accounts — the
-hook program, its `ExtraAccountMetaList` validation PDA, and any extra accounts
-the hook requires — into the Token-2022 `TransferChecked` CPI, so the hook's
-policy is always enforced.
-
-When you build a transfer with the SDK these hook accounts are resolved for you.
-The TypeScript plugin client (`transferFixed`, `transferRecurring`,
-`transferSubscription`) reads them from the mint and appends them automatically.
-If you build the instruction another way, resolve them with
-`resolveTransferHookAccounts` and pass the result as `transferHookAccounts`.
+Supports SPL Token and Token-2022, including Token-2022 mints with a configured
+`TransferHook` (e.g. PYUSD).
+
+On each delegated transfer the program forwards the mint's hook accounts (hook
+program, `ExtraAccountMetaList` PDA, extras) into the `TransferChecked` CPI, so
+the hook policy is enforced. The SDK resolves them for you:
+
+- Plugin client (`transferFixed`, `transferRecurring`, `transferSubscription`) —
+  appended automatically.
+- Building manually — call `resolveTransferHookAccounts`, pass
+  `transferHookAccounts`.
 
 ## On-Chain Events
 

apps/docs/content/docs/en/payments/subscriptions/revoke-abandoned-delegation.mdx

@@ -6,28 +6,25 @@ description:
 ---
 
 A fixed or recurring delegation holds rent that normally returns to its recorded
-payer when the delegation is revoked. If a sponsor funded the delegation and the
-user later closes or replaces their Subscription Authority, that delegation is
-left permanently unusable and its rent would otherwise be stuck.
-`RevokeAbandonedDelegation` lets the recorded payer reclaim that rent.
+payer on revoke. If a sponsor funded it and the user later closes or replaces
+their Subscription Authority, the delegation is stranded and its rent stuck.
+`RevokeAbandonedDelegation` lets the recorded payer reclaim it.
 
 ## When It Applies
 
-The program only allows this when the delegation is provably dead — its recorded
-Subscription Authority has been closed, or it has been closed and recreated so
-the authority's `init_id` no longer matches the delegation. Both states are
-irreversible, so a live delegation can never be closed this way.
+Allowed only when the delegation is provably dead — its Subscription Authority
+was closed, or closed and recreated (so `init_id` no longer matches). A live
+delegation can never be closed this way.
 
-This is also the only recovery path for a never-expiring delegation
-(`expiry_ts == 0`). Ordinary
+It's the only recovery path for a never-expiring delegation (`expiry_ts == 0`):
+ordinary
 [revoke](/docs/payments/subscriptions/recurring-delegation#revoke-the-delegation)
-closes a delegation on expiry, which a never-expiring delegation never reaches.
+only fires on expiry, which never arrives.
 
 ## Reclaim The Rent
 
-The recorded payer signs. Pass the abandoned delegation PDA and the Subscription
-Authority recorded on it (the account may already be closed). Rent returns to
-the payer.
+The recorded payer signs. Pass the dead delegation PDA and its recorded
+Subscription Authority (which may already be closed). Rent returns to the payer.
 
 <Tabs items={["TypeScript", "Rust"]}>
   <Tab value="TypeScript">