clarifications added, typos fixed [ci skip]

Signed-off-by: Alexander Piskun <bigcat88@icloud.com>

Author: bigcat88

.github/SECURITY.md

@@ -4,23 +4,32 @@
 
 Only the latest non beta release version of `nc_py_api` are currently being supported with security updates.
 
-## Reporting a Vulnerability
+## Reporting a Vulnerability about nc_py_api
 
-Security is very important to us. If you have discovered a security issue with Nextcloud,
+Officially, Nextcloud is not responsible for this project; the project is developed in the community’s free time.
+
+Please report security vulnerabilities to bigcat88@icloud.com with `nc-py-api` in the subject line.
+If there is no response within 24 hours, then create an Issue,
+without technical details, to report on the previously sent mail.
+
+## Reporting a Vulnerability about Nextcloud
+
+Transparency and Security are vital.
+If you have discovered a security issue with Nextcloud,
 please read our responsible disclosure guidelines and contact us at [hackerone.com/nextcloud](https://hackerone.com/nextcloud).
 Your report should include:
 
 - Product version
 - A vulnerability description
 - Reproduction steps
 
-If in scope of the project a member of the security team will confirm the vulnerability, determine its impact, and develop a fix.
+If in the scope of the project, a member of the security team confirms the vulnerability, determines its impact, and develops a fix.
 Otherwise, the team will contact the maintainer and make sure the issue gets fixed.
 The fix will be applied to the main branch, tested, and packaged in the next security release.
 The vulnerability will be publicly announced after the release.
 
 Finally, your name will be added to the [hall of fame](https://hackerone.com/nextcloud/thanks)
-as a thank you from the entire Nextcloud community.
+as a thank-you from the entire Nextcloud community.
 
 Note our [threat model](https://nextcloud.com/security/threat-model) to know what is expected behavior.