Update CONTRIBUTING.md

Co-authored-by: Dushyant Behl <[email protected]>
Signed-off-by: Sukriti Sharma <[email protected]>

Author: Ssukriti

CONTRIBUTING.md

@@ -33,7 +33,7 @@ from Kubernetes.
 When your contribution is ready, you can create a pull request. Pull requests are often referred to as "PR". In general, we follow the standard [GitHub pull request](https://help.github.com/en/articles/about-pull-requests) process. Follow the template to provide details about your pull request to the maintainers. 
 1. It's best to break your contribution into smaller PRs with incremental changes, and include a good description of the changes. 
 2. We require new unit tests to be contributed with any new functionality added.
-3. For any new feature or capability, documentation is a MUST. Features will not be announced in releases without documentation on how to use them. This is common practice in any open-sourced repository.
+3. We require each feature to be documented as part of the PR. If certain feature is experimental and not documented it will be announced as a dev preview.
 
 Before sending pull requests, make sure your changes pass formatting, linting and unit tests. These checks will run with the pull request builds. Alternatively, you can run the checks manually on your local machine [as specified below](#development).