fix: update relative links

01_literature/estimation-in-agile.md

@@ -8,7 +8,7 @@ description: null
 
 **Estimation** (or **estimating**) is the process of finding an **estimate**, or approximation, which is a value that is usable for some purpose even if input data may be incomplete, uncertain, or unstable.
 
-The value is nonetheless usable because it is derived from the best information available. [[1]](https://piemapping.atlassian.net/wiki/spaces/EN/pages/37486626/Estimations#Estimations-source-1)
+The value is nonetheless usable because it is derived from the best information available. [1](https://piemapping.atlassian.net/wiki/spaces/EN/pages/37486626/Estimations#Estimations-source-1)
 
 ## Estimation units
 In our workflow we use two different units that are explained below.

01_literature/tech-canvas.md

@@ -56,10 +56,10 @@ Some of the problem spaces we face internally, we also share with our community.
 
 | Title                                                                                       | 💰 Bounty | Status | PIC                         | Function    |
 | ------------------------------------------------------------------------------------------- | --------- | ------ | --------------------------- | ----------- |
-| [Move internal notes to note.d.foundation](app://obsidian.md/careers/earn/obsidian-fork.md) | 🧊 75     | Doing  | monotykamary, hnh           | 🏗️ Chore   |
-| [$icy withdrawal](app://obsidian.md/careers/earn/withdrawl-icy.md)                          | 🧊 120    | Doing  | minhlq                      | 🛠️ Tooling |
-| [Rework Fortress Command](app://obsidian.md/careers/earn/rework-fortress-command.md)        | 🧊 100    | Open   | -                           | 🛠️ Tooling |
-| [$icy utility commands](app://obsidian.md/careers/earn/icy-utility-command.md)              | 🧊 50     | Doing  | bienvh, phucld              | 🛠️ Tooling |
-| [$icy store](app://obsidian.md/careers/earn/icy-store.md)                                   | 🧊 100    | Open   | minhlq                      | 🛠️ Tooling |
-| [$icy staking](app://obsidian.md/careers/earn/icy-staking.md)                               | 🧊 350    | Open   | phucld, minhlq, nam, bienvh | 🛠️ Tooling |
-| [Fortress Shanky Data](app://obsidian.md/careers/earn/fortress-shanky-data.md)              | 🧊 120    | Open   | nam                         | 🛠️ Tooling |
+| [Move internal notes to note.d.foundation](app://obsidian.md/earn/obsidian-fork.md) | 🧊 75     | Doing  | monotykamary, hnh           | 🏗️ Chore   |
+| [$icy withdrawal](app://obsidian.md/earn/withdrawl-icy.md)                          | 🧊 120    | Doing  | minhlq                      | 🛠️ Tooling |
+| [Rework Fortress Command](app://obsidian.md/earn/rework-fortress-command.md)        | 🧊 100    | Open   | -                           | 🛠️ Tooling |
+| [$icy utility commands](app://obsidian.md/earn/icy-utility-command.md)              | 🧊 50     | Doing  | bienvh, phucld              | 🛠️ Tooling |
+| [$icy store](app://obsidian.md/earn/icy-store.md)                                   | 🧊 100    | Open   | minhlq                      | 🛠️ Tooling |
+| [$icy staking](app://obsidian.md/earn/icy-staking.md)                               | 🧊 350    | Open   | phucld, minhlq, nam, bienvh | 🛠️ Tooling |
+| [Fortress Shanky Data](app://obsidian.md/earn/fortress-shanky-data.md)              | 🧊 120    | Open   | nam                         | 🛠️ Tooling |

01_literature/why-micro-frontend.md

@@ -31,15 +31,15 @@ In a lot of cases, this approach is fine, it works if you do it right and a lot
 
 There might be a need for a more efficient solution - by breaking it down:
 
-[[playground/_memo/assets/why-micro-frontend/149cb7501d21ad52e476f168b93085cc_MD5.jpeg]]
+![[playground/_memo/assets/why-micro-frontend/149cb7501d21ad52e476f168b93085cc_MD5.jpeg]]
 ![](assets/why-micro-frontend_149cb7501d21ad52e476f168b93085cc_md5.webp)
 
 We can see that the backend work has been broken into microservices - a term we are probably too familiar with at this point. However, front-end work is still one big chunk. This is where micro-frontend comes in.
 
 ### The Micro-Frontend Architecture
 Let’s take the previous monolithic example (The Shop Team), broken into micro-frontends:
 
-[[playground/_memo/assets/why-micro-frontend/8b4ce5b2e752b7bbc96be21b6d2f1349_MD5.jpeg]]
+![[playground/_memo/assets/why-micro-frontend/8b4ce5b2e752b7bbc96be21b6d2f1349_MD5.jpeg]]
 ![](assets/why-micro-frontend_8b4ce5b2e752b7bbc96be21b6d2f1349_md5.webp)
 ![[Pasted image 20231101050539.webp]]
 With micro-frontends, codebase, teams, and responsibilities are split vertically in a way that the coupling between them is very low. Each team owns a smaller codebase, and can individually test, deploy and scale according to the needs. Now the teams only need to coordinate the moving parts, which can be kept minimal with a good system design. The teams can easily manage their dependencies and even use a separate tech stack.

README.md

@@ -30,7 +30,7 @@ graph TB
 ```
 
 ### Contributing
-At Dwarves, we encourage our people to read, write, share what we learn with others, and [contributing to the Brainery](CONTRIBUTING.md) is an important part of our learning culture. For visitors, you are welcome to read them, contribute to them, and suggest additions. We maintain a monthly pool of $1500 to reward contributors who support our journey of lifelong growth in knowledge and network.
+At Dwarves, we encourage our people to read, write, share what we learn with others, and [contributing to the Brainery](../CONTRIBUTING.md) is an important part of our learning culture. For visitors, you are welcome to read them, contribute to them, and suggest additions. We maintain a monthly pool of $1500 to reward contributors who support our journey of lifelong growth in knowledge and network.
 
 ### Love what we are doing?
 - Check out our [products](https://superbits.co)