Fix some links in docs

Author: chmanie

docs/.templates/onetxpayment.md

@@ -1,6 +1,6 @@
 # One Transaction Payment Extension (`OneTxPayment`)
 
-Ordinarily payments require more than one transaction, because the payment lifecycle requires more than one permissioned [role](../tldr/permissions).
+Ordinarily payments require more than one transaction, because the payment lifecycle requires more than one permissioned [role](../../tldr/permissions.md).
 
 In some use cases, there might be a need for one authorized individual to be able to create, funds, and finalize a payment within a single transaction.
 

docs/index.md

@@ -58,7 +58,7 @@ Using the Colony SDK, all of the functions of a colony can be imported and calle
 
 Things like parsing returned parameters from a transaction, and signing transactions with a wallet provider are all handled by this library while providing a small API with sane defaults.
 
-To learn more about how to use the Colony SDK with your dapp, or to get specific info about the Colony SDK API, see its [docs](/docs/colonysdk).
+To learn more about how to use the Colony SDK with your dapp, or to get specific info about the Colony SDK API, see its [docs](https://docs.colony.io/colonysdk).
 
 ### Developer Portal
 

docs/interfaces/extensions/onetxpayment.md

@@ -1,6 +1,6 @@
 # One Transaction Payment Extension (`OneTxPayment`)
 
-Ordinarily payments require more than one transaction, because the payment lifecycle requires more than one permissioned [role](../tldr/permissions).
+Ordinarily payments require more than one transaction, because the payment lifecycle requires more than one permissioned [role](../../tldr/permissions.md).
 
 In some use cases, there might be a need for one authorized individual to be able to create, funds, and finalize a payment within a single transaction.
 

docs/tldr/domains-skills.md

@@ -35,7 +35,7 @@ Even though the global set of Skills is shared by all colonies, reputation earne
 
 Skill tags are meant to provide a more fine-grained categorization of work than domains, allowing for tasks within the same domain to be further differentiated.
 
-See the [ColonyJS](/docs/colonyjs) `colonyClient` API for implementation details.
+See the [ColonyJS](https://docs.colony.io/colonyjs) `colonyClient` API for implementation details.
 
 ## Disputes
 

docs/tldr/metacolony.md

@@ -33,4 +33,4 @@ The Meta Colony also curates a global list of skill tags, used by _all colonies_
 
 Even though the skill hierarchy is universal, reputation earned in the skill hierarchy is unique to each colony. Earning reputation in a skill in one colony has no effect on the user’s reputation in that skill in any other colonies.
 
-For information about querying skills and specific implementation details, see the [ColonyJS `colonyNetworkClient`](/docs/colonyjs/api/interfaces/ColonyNetworkClient) API.
+For information about querying skills and specific implementation details, see the [ColonyJS `colonyNetworkClient`](https://docs.colony.io/colonyjs/api/interfaces/ColonyNetworkClient) API.

docs/tldr/pots.md

@@ -9,7 +9,7 @@ All funding within a colony resides in pots. To each pot, a colony can associate
 
 Assigning funding to pots is purely a bookkeeping mechanism for a colony. From the perspective of the blockchain, ether and tokens are held by the colony contract until they are paid out when a task is completed.
 
-A colony's internal token, chosen at the time of creation, has a special role within colony funding. When paid to a user through the task mechanism, the token confers reputation to that user, which can influence rewards payouts. See the [ColonyJS `tokenClient`](/docs/colonyjs/api/interfaces/ColonyTokenClient) API for information about the internal token and related administration.
+A colony's internal token, chosen at the time of creation, has a special role within colony funding. When paid to a user through the task mechanism, the token confers reputation to that user, which can influence rewards payouts. See the [ColonyJS `tokenClient`](https://docs.colony.io/colonyjs/api/interfaces/ColonyTokenClient) API for information about the internal token and related administration.
 
 ## Types of Pots
 

docs/tldr/tasks.md

@@ -15,7 +15,7 @@ There is intentionally no further prescription for how tasks or payments are mea
 
 ### Task structure
 
-This is a general description of the Task as it functions in the current Colony Network implementation, with some aspects suppressed for legibility. For a more exact description, please refer to the [ColonyJS](/docs/colonyjs/api) API or [IColony.sol](../interfaces/icolony).
+This is a general description of the Task as it functions in the current Colony Network implementation, with some aspects suppressed for legibility. For a more exact description, please refer to the [ColonyJS](https://docs.colony.io/colonyjs/api) API or [IColony.sol](../interfaces/icolony).
 
 | component              | description                                                                                             |
 | ---------------------- | ------------------------------------------------------------------------------------------------------- |