fix broken links

docs/advanced/dao/00-introduction.md

@@ -8,23 +8,23 @@ sidebar_position: 0
 
 In this section, you will learn about the core functionality of every Aragon OSx DAO.
 
-The `DAO` contract is the identity and basis of your 
-organization. It is the address carrying the DAO’s ENS name, metadata, 
+The `DAO` contract is the identity and basis of your
+organization. It is the address carrying the DAO’s ENS name, metadata,
 and holding the funds. Furthermore, it has **six base functionalities** being commonly found in other DAO frameworks in the ecosystem.
 
 ### 1. Execution of Arbitrary Actions
 
 The most important and basic functionality of your DAO is the **execution of arbitrary actions**,
- which allows you to execute the DAO's own functions as well as 
-interacting with the rest of the world, i.e., calling methods in other 
+which allows you to execute the DAO's own functions as well as
+interacting with the rest of the world, i.e., calling methods in other
 contracts and sending assets to other addresses.
 
 :::note
 
 Typically, actions are scheduled in a proposal in a governance [plugin installed to your DAO](/docs/advanced/plugin/index.md).
 :::
 
-Multiple `Action` structs can be put into one `Action[]` array and executed in a single transaction via the `execute` function. To learn more about actions and advanced features of the DAO executor, visit the [A Deep Dive Into Actions](/docs/1.3.0/osx/how-it-works/core/dao/actions) section.
+Multiple `Action` structs can be put into one `Action[]` array and executed in a single transaction via the `execute` function. To learn more about actions and advanced features of the DAO executor, visit the [A Deep Dive Into Actions](/1.3.0/osx/how-it-works/core/dao/actions) section.
 
 ### 2. Asset Management
 
@@ -40,10 +40,10 @@ In the future, more advanced asset management and finance functionality can be a
 
 ### 3. Upgradeability
 
-Your DAO contract has the ability to be upgraded to a newer version (see [Upgrade your DAO](/docs/1.3.0/osx/how-to-guides/dao/protocol-upgrades))
- if a new version of Aragon OSx is released in the future. These 
+Your DAO contract has the ability to be upgraded to a newer version (see [Upgrade your DAO](/1.3.0/osx/how-to-guides/dao/protocol-upgrades))
+if a new version of Aragon OSx is released in the future. These
 upgrades allow your DAO to smoothly transition to a new protocol version
- unlocking new features.
+unlocking new features.
 
 ### 4. Callback Handling
 
@@ -54,34 +54,34 @@ Our `CallbackHandler` allows to register the required callback responses dynamic
 ### 5. Signature Validation
 
 Currently,
- externally owned accounts (EOAs) can sign messages with their 
+externally owned accounts (EOAs) can sign messages with their
 associated private keys, but contracts cannot.
-An exemplary use case is a decentralized exchange with an off-chain 
+An exemplary use case is a decentralized exchange with an off-chain
 order book, where buy/sell orders are signed messages.
 To accept such a request, both, the external service provider and caller
- need to follow a standard with which the signed message of the caller 
+need to follow a standard with which the signed message of the caller
 can be validated.
 
 By supporting the [ERC-1271](https://eips.ethereum.org/EIPS/eip-1271) standard, your DAO can validate signatures via its `isValidSignature` function that forwards the call to a signature validator contract.
 
 ### 6. Permission Management
 
 Lastly,
- it is essential that only the right entities (e.g., the DAO itself or 
-trusted addresses) have permission to use the above-mentioned 
-functionalities. This is why Aragon OSx DAOs contain a flexible and 
-battle-tested **permission manager** being able to assign 
+it is essential that only the right entities (e.g., the DAO itself or
+trusted addresses) have permission to use the above-mentioned
+functionalities. This is why Aragon OSx DAOs contain a flexible and
+battle-tested **permission manager** being able to assign
 permissions for the above functionalities to specific addresses.
-Although possible, the permissions to execute arbitrary actions or 
-upgrade the DAO should not be given to EOAs as this poses a security 
-risk to the organization if the account is compromised or acts 
-adversarial. Instead, the permissions for the above-mentioned 
+Although possible, the permissions to execute arbitrary actions or
+upgrade the DAO should not be given to EOAs as this poses a security
+risk to the organization if the account is compromised or acts
+adversarial. Instead, the permissions for the above-mentioned
 functionalities are better restricted to the `DAO` contract itself and triggered through governance [plugins](/docs/advanced/plugin/index.md) that you can install on your DAO.
 
-To learn more, visit the [Permission Manager](/docs/1.3.0/osx/how-it-works/core/permissions/) section.
+To learn more, visit the [Permission Manager](/1.3.0/osx/how-it-works/core/permissions/) section.
 
-<!-- todo update links when all the documentation is migrated 
+<!-- todo update links when all the documentation is migrated
      todo  - A Deep Dive Into Actions link
      todo  - Upgrade your DAO link
      todo  - Permission Manager link
- -->
+ -->

docs/advanced/dao/01-creation.md

@@ -42,7 +42,7 @@ When calling `createDao` an array of `PluginSettings` are requested. A DAO canno
 - `Multisig`
 - `TokenVoting`
 
-If none of this options meet your requirements you can also build your own governance plugin, check our tutorial on ["How to build a plugin?"](/docs/1.3.0/osx/how-to-guides/plugin-development/) to get started.
+If none of this options meet your requirements you can also build your own governance plugin, check our tutorial on ["How to build a plugin?"](/1.3.0/osx/how-to-guides/plugin-development/) to get started.
 
 ## `DAORegistry`