Update links in Turbo Module documentation for Codegen

- Changed references to the Codegen documentation from relative links to the new structure for better navigation.
- Ensured consistency across multiple versions of the Turbo Module documentation by updating the links to point to the correct resources.

Author: sunnylqm

cndocs/new-architecture-turbo-module.md

@@ -111,7 +111,7 @@ Finally, we invoke `TurboModuleRegistry.get`, passing the module's name, which w
 
 ## 3. Module Configuration
 
-Next, you need to add some configuration for [**Codegen**](./codegen.md) and auto-linking.
+Next, you need to add some configuration for [**Codegen**](the-new-architecture/using-codegen) and auto-linking.
 
 Some configuration files are shared between iOS and Android, while the others are platform-specific.
 
@@ -374,7 +374,7 @@ For the final step in getting your Turbo Native Module ready to go, you'll need
 
 When developing a React Native app that uses a Turbo Native Module, it is the 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 the 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](./codegen.md).
+As the 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](the-new-architecture/using-codegen).
 
 > [!Warning]
 > 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.
@@ -429,7 +429,7 @@ generated
 
 The relevant path for the Turbo Native Module interface is `generated/build/generated/ios/RTNCalculatorSpec`.
 
-See the [Codegen](./codegen.md) section for further details on the generated files.
+See the [Codegen](the-new-architecture/using-codegen) section for further details on the generated files.
 
 > [!Note]
 > When generating the scaffolding code using **Codegen**, iOS does not clean the `build` folder automatically. If you changed the Spec name, for example, and then run **Codegen** again, the old files would be retained.

cnwebsite/versioned_docs/version-0.74/new-architecture-turbo-module.md

@@ -111,7 +111,7 @@ Finally, we invoke `TurboModuleRegistry.get`, passing the module's name, which w
 
 ## 3. Module Configuration
 
-Next, you need to add some configuration for [**Codegen**](./codegen.md) and auto-linking.
+Next, you need to add some configuration for [**Codegen**](the-new-architecture/using-codegen) and auto-linking.
 
 Some configuration files are shared between iOS and Android, while the others are platform-specific.
 
@@ -374,7 +374,7 @@ For the final step in getting your Turbo Native Module ready to go, you'll need
 
 When developing a React Native app that uses a Turbo Native Module, it is the 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 the 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](./codegen.md).
+As the 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](the-new-architecture/using-codegen).
 
 > [!Warning]
 > 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.
@@ -429,7 +429,7 @@ generated
 
 The relevant path for the Turbo Native Module interface is `generated/build/generated/ios/RTNCalculatorSpec`.
 
-See the [Codegen](./codegen.md) section for further details on the generated files.
+See the [Codegen](the-new-architecture/using-codegen) section for further details on the generated files.
 
 > [!Note]
 > When generating the scaffolding code using **Codegen**, iOS does not clean the `build` folder automatically. If you changed the Spec name, for example, and then run **Codegen** again, the old files would be retained.

cnwebsite/versioned_docs/version-0.75/new-architecture-turbo-module.md

@@ -111,7 +111,7 @@ Finally, we invoke `TurboModuleRegistry.get`, passing the module's name, which w
 
 ## 3. Module Configuration
 
-Next, you need to add some configuration for [**Codegen**](./codegen.md) and auto-linking.
+Next, you need to add some configuration for [**Codegen**](the-new-architecture/using-codegen) and auto-linking.
 
 Some configuration files are shared between iOS and Android, while the others are platform-specific.
 
@@ -374,7 +374,7 @@ For the final step in getting your Turbo Native Module ready to go, you'll need
 
 When developing a React Native app that uses a Turbo Native Module, it is the 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 the 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](./codegen.md).
+As the 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](the-new-architecture/using-codegen).
 
 > [!Warning]
 > 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.
@@ -429,7 +429,7 @@ generated
 
 The relevant path for the Turbo Native Module interface is `generated/build/generated/ios/RTNCalculatorSpec`.
 
-See the [Codegen](./codegen.md) section for further details on the generated files.
+See the [Codegen](the-new-architecture/using-codegen) section for further details on the generated files.
 
 > [!Note]
 > When generating the scaffolding code using **Codegen**, iOS does not clean the `build` folder automatically. If you changed the Spec name, for example, and then run **Codegen** again, the old files would be retained.

cnwebsite/versioned_docs/version-0.76/new-architecture-turbo-module.md

@@ -111,7 +111,7 @@ Finally, we invoke `TurboModuleRegistry.get`, passing the module's name, which w
 
 ## 3. Module Configuration
 
-Next, you need to add some configuration for [**Codegen**](./codegen.md) and auto-linking.
+Next, you need to add some configuration for [**Codegen**](the-new-architecture/using-codegen) and auto-linking.
 
 Some configuration files are shared between iOS and Android, while the others are platform-specific.
 
@@ -374,7 +374,7 @@ For the final step in getting your Turbo Native Module ready to go, you'll need
 
 When developing a React Native app that uses a Turbo Native Module, it is the 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 the 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](./codegen.md).
+As the 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](the-new-architecture/using-codegen).
 
 > [!Warning]
 > 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.
@@ -429,7 +429,7 @@ generated
 
 The relevant path for the Turbo Native Module interface is `generated/build/generated/ios/RTNCalculatorSpec`.
 
-See the [Codegen](./codegen.md) section for further details on the generated files.
+See the [Codegen](the-new-architecture/using-codegen) section for further details on the generated files.
 
 > [!Note]
 > When generating the scaffolding code using **Codegen**, iOS does not clean the `build` folder automatically. If you changed the Spec name, for example, and then run **Codegen** again, the old files would be retained.

cnwebsite/versioned_docs/version-0.77/new-architecture-turbo-module.md

@@ -111,7 +111,7 @@ Finally, we invoke `TurboModuleRegistry.get`, passing the module's name, which w
 
 ## 3. Module Configuration
 
-Next, you need to add some configuration for [**Codegen**](./codegen.md) and auto-linking.
+Next, you need to add some configuration for [**Codegen**](the-new-architecture/using-codegen) and auto-linking.
 
 Some configuration files are shared between iOS and Android, while the others are platform-specific.
 
@@ -374,7 +374,7 @@ For the final step in getting your Turbo Native Module ready to go, you'll need
 
 When developing a React Native app that uses a Turbo Native Module, it is the 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 the 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](./codegen.md).
+As the 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](the-new-architecture/using-codegen).
 
 > [!Warning]
 > 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.
@@ -429,7 +429,7 @@ generated
 
 The relevant path for the Turbo Native Module interface is `generated/build/generated/ios/RTNCalculatorSpec`.
 
-See the [Codegen](./codegen.md) section for further details on the generated files.
+See the [Codegen](the-new-architecture/using-codegen) section for further details on the generated files.
 
 > [!Note]
 > When generating the scaffolding code using **Codegen**, iOS does not clean the `build` folder automatically. If you changed the Spec name, for example, and then run **Codegen** again, the old files would be retained.

cnwebsite/versioned_docs/version-0.78/new-architecture-turbo-module.md

@@ -111,7 +111,7 @@ Finally, we invoke `TurboModuleRegistry.get`, passing the module's name, which w
 
 ## 3. Module Configuration
 
-Next, you need to add some configuration for [**Codegen**](./codegen.md) and auto-linking.
+Next, you need to add some configuration for [**Codegen**](the-new-architecture/using-codegen) and auto-linking.
 
 Some configuration files are shared between iOS and Android, while the others are platform-specific.
 
@@ -374,7 +374,7 @@ For the final step in getting your Turbo Native Module ready to go, you'll need
 
 When developing a React Native app that uses a Turbo Native Module, it is the 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 the 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](./codegen.md).
+As the 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](the-new-architecture/using-codegen).
 
 > [!Warning]
 > 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.
@@ -429,7 +429,7 @@ generated
 
 The relevant path for the Turbo Native Module interface is `generated/build/generated/ios/RTNCalculatorSpec`.
 
-See the [Codegen](./codegen.md) section for further details on the generated files.
+See the [Codegen](the-new-architecture/using-codegen) section for further details on the generated files.
 
 > [!Note]
 > When generating the scaffolding code using **Codegen**, iOS does not clean the `build` folder automatically. If you changed the Spec name, for example, and then run **Codegen** again, the old files would be retained.

cnwebsite/versioned_docs/version-0.79/new-architecture-turbo-module.md

@@ -111,7 +111,7 @@ Finally, we invoke `TurboModuleRegistry.get`, passing the module's name, which w
 
 ## 3. Module Configuration
 
-Next, you need to add some configuration for [**Codegen**](./codegen.md) and auto-linking.
+Next, you need to add some configuration for [**Codegen**](the-new-architecture/using-codegen) and auto-linking.
 
 Some configuration files are shared between iOS and Android, while the others are platform-specific.
 
@@ -374,7 +374,7 @@ For the final step in getting your Turbo Native Module ready to go, you'll need
 
 When developing a React Native app that uses a Turbo Native Module, it is the 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 the 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](./codegen.md).
+As the 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](the-new-architecture/using-codegen).
 
 > [!Warning]
 > 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.
@@ -429,7 +429,7 @@ generated
 
 The relevant path for the Turbo Native Module interface is `generated/build/generated/ios/RTNCalculatorSpec`.
 
-See the [Codegen](./codegen.md) section for further details on the generated files.
+See the [Codegen](the-new-architecture/using-codegen) section for further details on the generated files.
 
 > [!Note]
 > When generating the scaffolding code using **Codegen**, iOS does not clean the `build` folder automatically. If you changed the Spec name, for example, and then run **Codegen** again, the old files would be retained.

cnwebsite/versioned_docs/version-0.80/new-architecture-turbo-module.md

@@ -111,7 +111,7 @@ Finally, we invoke `TurboModuleRegistry.get`, passing the module's name, which w
 
 ## 3. Module Configuration
 
-Next, you need to add some configuration for [**Codegen**](./codegen.md) and auto-linking.
+Next, you need to add some configuration for [**Codegen**](the-new-architecture/using-codegen) and auto-linking.
 
 Some configuration files are shared between iOS and Android, while the others are platform-specific.
 
@@ -374,7 +374,7 @@ For the final step in getting your Turbo Native Module ready to go, you'll need
 
 When developing a React Native app that uses a Turbo Native Module, it is the 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 the 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](./codegen.md).
+As the 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](the-new-architecture/using-codegen).
 
 > [!Warning]
 > 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.
@@ -429,7 +429,7 @@ generated
 
 The relevant path for the Turbo Native Module interface is `generated/build/generated/ios/RTNCalculatorSpec`.
 
-See the [Codegen](./codegen.md) section for further details on the generated files.
+See the [Codegen](the-new-architecture/using-codegen) section for further details on the generated files.
 
 > [!Note]
 > When generating the scaffolding code using **Codegen**, iOS does not clean the `build` folder automatically. If you changed the Spec name, for example, and then run **Codegen** again, the old files would be retained.

cnwebsite/versioned_docs/version-0.81/new-architecture-turbo-module.md

@@ -111,7 +111,7 @@ Finally, we invoke `TurboModuleRegistry.get`, passing the module's name, which w
 
 ## 3. Module Configuration
 
-Next, you need to add some configuration for [**Codegen**](./codegen.md) and auto-linking.
+Next, you need to add some configuration for [**Codegen**](the-new-architecture/using-codegen) and auto-linking.
 
 Some configuration files are shared between iOS and Android, while the others are platform-specific.
 
@@ -374,7 +374,7 @@ For the final step in getting your Turbo Native Module ready to go, you'll need
 
 When developing a React Native app that uses a Turbo Native Module, it is the 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 the 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](./codegen.md).
+As the 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](the-new-architecture/using-codegen).
 
 > [!Warning]
 > 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.
@@ -429,7 +429,7 @@ generated
 
 The relevant path for the Turbo Native Module interface is `generated/build/generated/ios/RTNCalculatorSpec`.
 
-See the [Codegen](./codegen.md) section for further details on the generated files.
+See the [Codegen](the-new-architecture/using-codegen) section for further details on the generated files.
 
 > [!Note]
 > When generating the scaffolding code using **Codegen**, iOS does not clean the `build` folder automatically. If you changed the Spec name, for example, and then run **Codegen** again, the old files would be retained.