docs: update CONTRIBUTING.md (#18)

CONTRIBUTING.md

@@ -1,24 +1,6 @@
 # Contributing Guidelines
 
-Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional
-documentation, we greatly value feedback and contributions from our community.
-
-Please read through this document before submitting any issues or pull requests to ensure we have all the necessary
-information to effectively respond to your bug report or contribution.
-
-
-## Reporting Bugs/Feature Requests
-
-We welcome you to use the GitHub issue tracker to report bugs or suggest features.
-
-When filing an issue, please check existing open, or recently closed, issues to make sure somebody else hasn't already
-reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
-
-* A reproducible test case or series of steps
-* The version of our code being used
-* Any modifications you've made relevant to the bug
-* Anything unusual about your environment or deployment
-
+Thank you for your interest in contributing to our project. We appreciate your interest but our intention is not for customers to send PRs back to the service for feature requests. The most interesting pieces about this release will be the project and code structure, architectural choices and operational rigor applied to various parts of our service. If you have a valuable contribution to an issue that affects multiple customers, please submit a pull request following the guidelines below.
 
 ## Contributing via Pull Requests
 Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that: