editorial

docs/build/guides/tokens/custom-sac-admin.mdx

@@ -8,11 +8,11 @@ The [Stellar Asset Contract (SAC)](../../../tokens/stellar-asset-contract.mdx) i
 
 ## Considerations
 
-The effectively utilize the SAC admin functionality, you should be aware of a few things first:
+To effectively utilize the SAC admin functionality, you should be aware of a few things first:
 
 - When a SAC is initially enabled for an issued asset, the `Admin` address on the contract defaults to the issuer account.
 - A SAC `Admin` address can be either a "regular" `G...` address, or it can be a smart contract `C...` address. This opens up the possibility of programatizing the minting and other administrative tasks of an asset by way of a smart contract invocation.
-- Changing a SAC `Admin` address (initially) requires authorization from the asset's issuer account. After the `Admin` address has been set a first time, subsequent changes will require authorization from the _current_ `Admin` address.
+- Changing a SAC `Admin` address (initially) requires authorization from the asset's issuer account. After the `Admin` address has been set the first time, subsequent changes will require authorization from the _current_ `Admin` address.
 - If an asset's issuer account is locked while the SAC `Admin` address has not been changed, it will _never_ be possible to change the SAC `Admin` address.
 - If an asset's issuer account is locked after the SAC `Admin` address has been changed, tokens will still be mint-able from the SAC as long as it's authorized by the _current_ `Admin` address.
 
@@ -22,7 +22,7 @@ The following example will create a new Stellar asset, `STAR:GCS5NEHKJALCSVJAKIO
 
 ### Enable the built-in SAC contract
 
-First, we'll enable teh SAC contract, using the Stellar CLI:
+First, we'll enable the SAC contract using the Stellar CLI:
 
 ```shell
 stellar contract asset deploy \
@@ -41,7 +41,7 @@ We're using the asset's issuer account here to enable the SAC on the Testnet net
 
 ### Check the initial `Admin` address
 
-Now that we have the SAC deployed to the network, we can invoke the `admin` function to find out what it's current `Admin` address is:
+Now that we have the SAC deployed to the network, we can invoke the `admin` function to find out what its current `Admin` address is:
 
 ```shell
 stellar contract invoke \
@@ -56,7 +56,7 @@ Unsurprisingly, it's set to the issuer's `GCS5...` account. Let's change that.
 
 ### Set the `Admin` address to a new `G...` account
 
-We can set this `Admin` address to any account that we want. Including an account that's un-funded on the network. As long as you're able to provide a valid signature for the account, which would take into consideration any multisig or signature weights that have been setup, you can use this event for future administration of the asset from within the contract.
+We can set this `Admin` address to any account that we want. Including an account that's un-funded on the network. As long as you're able to provide a valid signature for the account, which would take into consideration any multisig or signature weights that have been set up, you can use this event for future administration of the asset from within the contract.
 
 :::info
 
@@ -72,7 +72,7 @@ stellar contract invoke \
     set_admin --new_admin GBL3IQ6KA3I7CS7C5ABTCU7CJJA7X76SBZKTTQVJ4APW5646DXEIQKHB
 ```
 
-Now, invoking the `admin` function of the contract, will return this new `GBL3...` address, rather than the original issuer of the asset.
+Now, invoking the `admin` function of the contract will return this new `GBL3...` address, rather than the original issuer of the asset.
 
 ```shell
 stellar contract invoke \