Changes in Contributing, Readme and Security files

CONTRIBUTING.md

@@ -10,8 +10,7 @@ For bugs or enhancement requests, please file a GitHub issue unless it's securit
 
 We welcome your code contributions. To get started, you will need to sign the [Oracle Contributor Agreement](https://www.oracle.com/technetwork/community/oca-486395.html) (OCA).
 
-For pull requests to be accepted, the bottom of your commit message must have
-the following line using the name and e-mail address you used for the OCA.
+For pull requests to be accepted, the bottom of your commit message must have the following line using the name and e-mail address you used for the OCA.
 
 ```text
 Signed-off-by: Your Name <you@example.org>
@@ -29,16 +28,13 @@ signed the OCA can be accepted.
 ### Pull request process
 
 1. Fork this repository
-1. Create a branch in your fork to implement the changes. We recommend using
-the issue number as part of your branch name, e.g. `1234-fixes`
-1. Ensure that any documentation is updated with the changes that are required
-by your fix.
-1. Ensure that any samples are updated if the base image has been changed.
-1. Submit the pull request. *Do not leave the pull request blank*. Explain exactly
-what your changes are meant to do and provide simple steps on how to validate
-your changes. Ensure that you reference the issue you created as well.
-1. We will assign the pull request to 2-3 people for review before it is merged.
+2. Create a branch in your fork to implement the changes. We recommend using the issue number as part of your branch name, e.g. `1234-fixes`
+3. Ensure that any documentation is updated with the changes that are required by your fix.
+4. Ensure that any samples are updated if the base image has been changed.
+5. Submit the pull request. *Do not leave the pull request blank*. Explain exactly
+what your changes are meant to do and provide simple steps on how to validate your changes. Ensure that you reference the issue you created as well.
+6. We will assign the pull request to 2-3 people for review before it is merged.
 
 ## Code of Conduct
 
-Follow the [Golden Rule](https://en.wikipedia.org/wiki/Golden_Rule). If you'd like more specific guidelines see the [Contributor Covenant Code of Conduct](https://www.contributor-covenant.org/version/1/4/code-of-conduct/)
+Follow the [Golden Rule](https://en.wikipedia.org/wiki/Golden_Rule). If you'd like more specific guidelines see the [Contributor Covenant Code of Conduct](https://www.contributor-covenant.org/version/1/4/code-of-conduct/)

README.md

@@ -4,7 +4,7 @@
 # Prerequisite
   - Git
   - Ant 1.9.9 or above
-  - JDK-8 (to build nb-javac)
+  - JDK 8 or above (to build nb-javac)
 
 # Building nb-javac jar files
 1.Obtain the code with the following command
@@ -56,4 +56,4 @@ Subscribe or mail the dev@netbeans.apache.org list - Join development discussion
 See the  [Contributing Policy](./CONTRIBUTING.md)
 
 # Security
-See the  [Security Policy](./SECURITY.md)
+See the  [Security Policy](./SECURITY.md)

SECURITY.md

@@ -2,10 +2,10 @@
 Oracle values the independent security research community and believes that responsible disclosure of security vulnerabilities helps us ensure the security 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 preferably with a proof of concept. We provide additional information on how to report security vulnerabilities to Oracle which includes public encryption keys for secure email.
 We ask that you do not use other channels or contact project contributors directly.
-Non-vulnerability related security issues such as new great new ideas for security features are welcome on GitHub Issues.
+Non-vulnerability related security issues such as great new ideas for security features are welcome on GitHub Issues.
 
 # Security Updates, Alerts and Bulletins
 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 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 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.
+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 sample code (if any) are intended to demonstrate a concept and may not be sufficiently hardened for production use.