Additions to info on Fees based on Jason's text.
@@ -453,8 +453,20 @@ Here are three example scenarios and how the round range may be calculated for e
Last Valid Round = 6018382 + 1000 = 6019382
```
-# Determining the Suggested Fee
-The minimum fee to send a transaction on Algorand is 1000 microAlgos. If blocks are not full, this fee is generally sufficient for the transaction to be prioritized into a block. The SDKs provide `suggestedFee` methods to help determine a fee likely to be accepted and committed.
+# Fees
+
+There are two primary ways to set the fee for a transaction.
+
+## Suggested Fee
+
+The SDK provides a method to get the [**suggested fee** per byte (`fee`)](../../reference/rest-apis/algod.md#transactionfee) which can be used to set the total fee for a transaction. This value is multiplied by the estimated size of the transaction in bytes to determine the total transaction fee. If the result is less than the minimum fee, the minimum fee is used instead.
+
+For larger transactions (> 1 KB in size), the resulting total fee will be greater than the network minimum, which in certain network conditions, may be more than you need to pay to get the transaction processed into the blockchain quickly. In particular, when blocks have enough room for all transactions, the minimum transaction fee will generally suffice. In this network scenario, set the fee (per byte) to 0 if you want to ensure that the minimum fee is chosen instead.
+
+In the future as more transactions are added to the network (and blocks are full), the minimum transaction fee may not guarantee that your transaction is processed as quickly as other transactions with higher fees set. In this case, using the returned suggested fee, which is based on the current transaction load, is the preferred method.
+
+## Flat Fee
+You can also manually set a **flat fee**. If you choose this method, make sure that your fee covers at least the [minimum transaction fee (`minFee`)](../../reference/rest-apis/algod/#transactionparams), which can be obtained from the suggested parameters method call in each of the SDKs. Flat fees may be useful for applications that want to guarantee showing a specific rounded fee to users or for a transaction that is meant to be sent in the future where the network traffic conditions are unknown.
# Setting First and Last Valid
