remove email mention; add sec. issue example

Author: kikofernandez

_news/172.md

@@ -26,8 +26,8 @@ There is not any hard and fast rule to determine if a bug is worth reporting as
 
 All security bugs in the Erlang/OTP distribution should be reported to [https://github.com/erlang/otp/security](https://github.com/erlang/otp/security). Your report will be handled by a small security team at the OTP team.
 
-Please use a descriptive email title for your report. After the initial response to your report, the security team will keep you updated on the progress and decision being made towards a fix and release announcement.
+Please use a descriptive title for your report. After the initial response to your report, the security team will keep you updated on the progress and decision being made towards a fix and release announcement.
 
 ## Flagging Existing Issues as Security-related
 
-If you believe that an existing public issue on [https://github.com/erlang/otp/issues](https://github.com/erlang/otp/issues) is security-related, we ask that you report it via [https://github.com/erlang/otp/security](https://github.com/erlang/otp/security). The title should contain the issue ID on [https://github.com/erlang/otp/issues](https://github.com/erlang/otp/issues) (e.g. Flagging security issue ERL-001). Please include a short description to motivate why it should be handled according to the security policy.
+If you believe that an existing public issue on [https://github.com/erlang/otp/issues](https://github.com/erlang/otp/issues) is security-related, we ask that you report it via [https://github.com/erlang/otp/security](https://github.com/erlang/otp/security). The title should contain the issue ID from [https://github.com/erlang/otp/issues](https://github.com/erlang/otp/issues) (e.g., flagging security issue [#7539](https://github.com/erlang/otp/issues/7539)). Please include a short description to motivate why it should be handled according to the security policy.