diff --git a/proposals/0012-introduce-reactNativeMetadata.md b/proposals/0012-introduce-reactNativeMetadata.md
index e848764..af8b388 100644
--- a/proposals/0012-introduce-reactNativeMetadata.md
+++ b/proposals/0012-introduce-reactNativeMetadata.md
@@ -25,7 +25,7 @@ This new section will allow developers to follow a declarative approach to expre
 
 ## Rationale
 
-The need to specify **capabilities and metadata** for a react-native library is inherent to the React Native ecosystem. This need is so evident that various frameworks provided their own ways to specify those values. Look at `react-native.config.js` for the CLI or `expo.config.js` for Expo.
+The need to specify **capabilities and metadata** for a react-native library is inherent to the React Native ecosystem. This need is so evident that various frameworks provided their own ways to specify those values. Look at `react-native.config.js` for the CLI or `app.json` for Expo.
 
 Another issue is that, as of today, there is no simple programmatic way to know if a NPM package is a React Native library.
 We have some heuristics, though:
@@ -388,6 +388,8 @@ Once the v1.0.0 version of the shape is finalised, we can start integrating it a
 
 After adding this first wave of support, and related documentation, we could more broadly communicate to the community and the maintainers how adding this section would benefit them too.
 
+Furthermore, we will provide validation scripts to verify that the new field do respect the schema described by its version.
+
 ### Documentation update needed
 
 If we agree on this proposal, we'll have to: