fix: use the proper links

docs/the-new-architecture/pillars-turbomodule.md

@@ -107,7 +107,7 @@ We are writing JavaScript files importing types from libraries, without setting
 
 ## 3. Module Configuration
 
-Next, you need to add some configuration for [**Codegen**](/docs/pillars-codegen.md) and auto-linking.
+Next, you need to add some configuration for [**Codegen**](pillars-codegen.md) and auto-linking.
 
 Some of these configuration files are shared between iOS and Android, while the others are platform-specific.
 
@@ -346,7 +346,7 @@ For the final step in getting your TurboModule ready to go, you'll need to write
 
 When developing a React Native app that uses a TurboModule, it is responsibility of the app to actually generate the code using **Codegen**. However, when developing a TurboModule as a library, we need to reference the generated code, and it is therefore useful to see what the app will generate.
 
-As first step for both iOS and Android, this guide shows how to execute manually the scripts used by **Codegen** to generate the required code. Further information on **Codegen** can be found [here](/docs/pillars-codegen.md)
+As first step for both iOS and Android, this guide shows how to execute manually the scripts used by **Codegen** to generate the required code. Further information on **Codegen** can be found [here](pillars-codegen.md)
 
 :::caution
 The code generated by **Codegen** in this step should not be committed to the versioning system. React Native apps are able to generate the code when the app is built. This allows an app to ensure that all libraries have code generated for the correct version of React Native.