Merge branch 'token-wayfinding' of https://github.com/stellar/stellar…

…-docs into token-wayfinding

docs/smart-contracts/tokens/wayfinding.mdx

@@ -50,21 +50,21 @@ Learn how to deploy a Stellar Asset Contract for an asset in [this How-To Guide]
 - Compatibility: the SAC benefits from Stellar assets' existing interoperability.
 - Cost and resource efficiency: the SAC is built into the protocol instead of being a contract that runs in a virtual machine. Each function within the SAC will be more resource-efficient than its custom-coded counterpart.
 - Less work: you don’t have to write an entirely new contract. A Stellar asset’s SAC already exists on the network and just needs to be deployed to be used.
-- Customization: asset issuers can set a different smart contract as an admin for their asset’s SAC. Making this admin another smart contract means that that address can add a bit of customization and logic to how the asset will authorize balances and trustlines, mint tokens, etc. Admin addresses can be contracts.
+- Customization:  Admin addresses can be contracts. Asset issuers can set a different smart contract as an admin for their asset’s SAC. Making the admin another smart contract allows the addition of custom and decentralized logic for the assets admin capabilities, such as authorizing balances and trust lines, minting tokens, etc.
 
 **Downside of the SAC:**
 
 - Other than the customization noted above, it is not possible to modify the behavior of Stellar assets or their SAC. If you’re looking to use assets in a way not supported by Stellar assets, you can create your own custom smart contract token using the token interface and all applications that interact with tokens using the token interface will be able to interact with the custom token.
 
 ## Custom tokens
 
-If you have a unique use case where the SAC's capabilities are not sufficient, you can create a custom token that implements the [token interface](./token-interface.mdx). The token interface specifies the functions and events a contract must implement to be compatible with applications that use tokens.
+If you have a unique use case where the capabilities Stellar Assets are not sufficient, you can create a custom token that implements the [token interface](./token-interface.mdx). The token interface specifies the functions and events a contract must implement to be compatible with applications that use tokens.
 
 The SAC also implements the token interface and applications that interoperate with the token interface can seamlessly interact with Stellar assets and custom tokens.
 
 :::note
 
-Smart contracts cannot use Stellar assets unless that Stellar asset has a deployed SAC.
+Smart contracts cannot use Stellar assets unless that Stellar asset has a deployed SAC. Anyone can deploy the SAC for a Stellar asset to its reserved address.
 
 :::