gio's comments

application/20221219-ft-v2.md

@@ -204,7 +204,11 @@ so there is no performance requirements to enforce with the methods.
 
 ### Dependencies
 
-* Adds no new dependencies
+* Adds the `Burner` contract.
+  * Contracts won't have to import the `Burner` contract
+    directly because the conformance is handled by
+    `FungibleToken.Vault`, so it isn't a direct dependency,
+    but important to be aware of
 * Dependent projects
     * All fungible tokens on Flow and some projects that utilize them,
     including but not limited to:
@@ -227,7 +231,8 @@ within resources, avoiding public fields, and giving developers flexibility to w
 
 ### Tutorials and Examples
 
-* Coming soon once the proposal reaches a more final state
+* Check out the Cadence 1.0 migration guide for instructions on how to update contracts to the new standards:
+  * https://cadence-lang.org/docs/cadence_migration_guide/
 
 ### Compatibility
 
@@ -250,7 +255,7 @@ to create scoped providers.
 
 This feature is out of the scope of this proposal, but should definitely be a standard
 that lives alongside the main fungible token standard.
-We hope to shepard a proposal for these soon.
+We hope to shepherd a proposal for these soon.
 
 ## Prior Art