Update documentation according to internal requirements (#497)

* Add files via upload

* Update README.md

* Delete build_spec.yaml

Author: spavlusieva

README.md

@@ -65,6 +65,12 @@ request, please [review our contribution guide](./CONTRIBUTING.md).
 Please consult the [security guide](./SECURITY.md) for our responsible security
 vulnerability disclosure process.
 
+## License
+
+Copyright (c) 2020, 2023 Oracle and/or its affiliates.
+
+Released under the Universal Permissive License v1.0 as shown at
+<https://oss.oracle.com/licenses/upl/>.
 
 ## Feedback
 

SECURITY.md

@@ -6,10 +6,10 @@ and privacy of all our users.
 
 Please do NOT raise a GitHub Issue to report a security vulnerability. If you
 believe you have found a security vulnerability, please submit a report to
-<mailto:[email protected]> preferably with a proof of concept. Please review
-some additional information on [how to report security vulnerabilities to Oracle][1].
+[[email protected]][1] preferably with a proof of concept. Please review
+some additional information on [how to report security vulnerabilities to Oracle][2].
 We encourage people who contact Oracle Security to use email encryption using
-[our encryption key][2].
+[our encryption key][3].
 
 We ask that you do not use other channels or contact the project maintainers
 directly.
@@ -21,10 +21,8 @@ security features are welcome on GitHub Issues.
 
 Security updates will be released on a regular cadence. Many of our projects
 will typically release security fixes in conjunction with the
-[Oracle Critical Patch Update][3] program. Security updates are released on the
-Tuesday closest to the 17th day of January, April, July and October. A pre-release
-announcement will be published on the Thursday preceding each release. Additional
-information, including past advisories, is available on our [security alerts][3]
+Oracle Critical Patch Update program. Additional
+information, including past advisories, is available on our [security alerts][4]
 page.
 
 ## Security-related information
@@ -34,6 +32,7 @@ for secure use, or any known security issues in our documentation. Please note
 that labs and sample code are intended to demonstrate a concept and may not be
 sufficiently hardened for production use.
 
-[1]: https://www.oracle.com/corporate/security-practices/assurance/vulnerability/reporting.html
-[2]: https://www.oracle.com/security-alerts/encryptionkey.html
-[3]: https://www.oracle.com/security-alerts/
+[1]: mailto:[email protected]
+[2]: https://www.oracle.com/corporate/security-practices/assurance/vulnerability/reporting.html
+[3]: https://www.oracle.com/security-alerts/encryptionkey.html
+[4]: https://www.oracle.com/security-alerts/