Update SECURITY.md

Author: spavlusieva

SECURITY.md

@@ -6,11 +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
-[secalert_us@oracle.com](mailto:secalert_us@oracle.com) preferably with a proof of concept. 
-Please review some additional information on 
-[how to report security vulnerabilities to Oracle](https://www.oracle.com/corporate/security-practices/assurance/vulnerability/reporting.html).
+[secalert_us@oracle.com][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](https://www.oracle.com/security-alerts/encryptionkey.html).
+[our encryption key][3].
 
 We ask that you do not use other channels or contact the project maintainers
 directly.
@@ -22,15 +21,18 @@ 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](https://www.oracle.com/security-alerts/encryptionkey.html) 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](https://www.oracle.com/security-alerts/) page.
+[Oracle Critical Patch Update][3] program. Additional
+information, including past advisories, is available on our [security alerts][4]
+page.
 
 ## Security-related information
 
 We will provide security related information such as a threat model, considerations
 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]: mailto:secalert_us@oracle.com
+[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/