diff --git a/docs/appendix.md b/docs/appendix.md
index e5a61b3..d8ead43 100644
--- a/docs/appendix.md
+++ b/docs/appendix.md
@@ -257,8 +257,8 @@ node node_modules/react-native/scripts/generate-specs-cli.js \
 ```
 
 > [!Note]
-> The output artifacts of the Codegen are inside the build folder and should not be committed.
-> They should be considered only for reference.
+> By default, the output artifacts of the Codegen are written to the build folder and should not be committed. They should be considered only for reference.
+> It is also possible to include the codegen output into your library. [Read more](./codegen.md#including-generated-code-into-libraries).
 
 ##### Example
 
diff --git a/docs/turbo-modules.md b/docs/turbo-modules.md
index eeeede3..98f96d5 100644
--- a/docs/turbo-modules.md
+++ b/docs/turbo-modules.md
@@ -374,7 +374,8 @@ When developing a React Native app that uses a Turbo Native Module, it is the re
 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).
 
 > [!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.
+> 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. It is also possible to [include the codegen output into your library](./codegen.md#including-generated-code-into-libraries).
+
 
 ### iOS