Merge pull request #81 from CodinMaster/update-outdated-urls

Update outdated links in Vault Integration Guide. Closes #80

vault/vault-integration-guide/vault-integration-guide.md

@@ -111,7 +111,7 @@ We can recommend one tool over another according to our experience, however you
 
 Another way to interact with Vaults is through the Maker smart contracts.
 
-CDP Manager is our public facing interface contract that allows anyone to easily interact with the MCD system. This is the recommended way to interact with the Maker protocol. You can find some examples that show a simple Vault lifecycle with CDP Manager [here](https://github.com/makerdao/developerguides/blob/master/mcd/mcd-seth/mcd-seth-01.md). Or dive deep in the [CDP Manager Guide](../cdp-manager-guide.md).
+CDP Manager is our public facing interface contract that allows anyone to easily interact with the MCD system. This is the recommended way to interact with the Maker protocol. You can find some examples that show a simple Vault lifecycle with CDP Manager [here](https://github.com/makerdao/developerguides/blob/master/mcd/mcd-seth/mcd-seth.md). Or dive deep in the [CDP Manager Guide](../cdp-manager-guide/cdp-manager-guide.md).
 
 If you want to abstract many individual contract calls into one, then you can use our [proxy contract](https://github.com/makerdao/dss-proxy-actions) that uses the CDP Manager to interact with the system. In the proxy contract, the owner of the Vault is the proxy address and not the user's address. Clearly, the user's address is the owner of the proxy, so there's a link between the two addresses. Please refer to the [Working with DSProxy](https://github.com/makerdao/developerguides/blob/master/devtools/working-with-dsproxy/working-with-dsproxy.md) guide to understand how proxy contracts are used to interact with the core system. Here's an example of a Single Vault User Flow when using the DSProxy design pattern: