Add documentation for simplified flow deps add syntax

docs/tools/flow-cli/dependency-manager.md

@@ -15,8 +15,13 @@ If you know the address and name of the contract you want to install (this can u
 
 `flow dependencies add testnet://7e60df042a9c0868.FlowToken`
 
+For core contracts, you can add them to your project using a simplified syntax using only the contract name (learn more about core contracts [here](../../build/core-contracts/index.md)), for example:
+
+`flow dependencies add FlowToken`
+
+Th command will default to using Flow Mainnet as the source network (i.e. this command is functionally equivalent to `flow dependencies add mainnet://1654653399040a61.FlowToken`).
+
 > Note: You can also use the shorthand `deps`
-> 
 
 In this command, the string that will be used as the `source` in the `flow.json` after installation is `testnet://7e60df042a9c0868.FlowToken`. This can be broken down into three sections for formatting it yourself for another contract:
 
@@ -69,4 +74,4 @@ This will look at all the dependencies you have in your `flow.json`, install the
 - After installation, you will have a local folder named `imports` that you should add to `.gitignore`. This folder is where your dependencies will be stored locally.
 - If your contracts change on the network, the Dependency Manager will ask if you want to update the local dependencies in your `imports` folder. The hash saved in the dependency object is used for this check, so don't remove it.
 - Dependencies will function just like contracts. For instance, you can add them to [`deployments` in your `flow.json`](./deployment/deploy-project-contracts.md) and run `flow project deploy`, as well as import them in your scripts, transactions, and contracts just as you would with a contract you added yourself (e.g., `import "FlowToken"`).
-- Core contract aliases will be automatically added for you across all networks.
+- Core contract aliases will be automatically added for you across all networks.