Update docs (#20)

* Update SECURITY.md

* Delete build_spec.yaml

* Update LICENSE.txt

* Update LICENSE.txt

* Update README.md

LICENSE.txt

@@ -1,4 +1,4 @@
-Copyright (c) 2022 Oracle and/or its affiliates.
+Copyright (c) 2023 Oracle and/or its affiliates.
 
 The Universal Permissive License (UPL), Version 1.0
 

README.md

@@ -25,5 +25,5 @@ vulnerability disclosure process.
 
 ## License
 
-Copyright (c) 2022 Oracle and/or its affiliates.
-Released under the Universal Permissive License v1.0 as shown at <https://oss.oracle.com/licenses/upl/>.
+Copyright (c) 2023 Oracle and/or its affiliates.
+Released under the Universal Permissive License v1.0 as shown at <https://oss.oracle.com/licenses/upl/>.

SECURITY.md

@@ -21,7 +21,7 @@ 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
+Oracle Critical Patch Update 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][4]
@@ -37,4 +37,4 @@ 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/
+[4]: https://www.oracle.com/security-alerts/