MD Formatting of security processes mk. III
Signed-off-by: Chris Walker <chris@webtide.com>
diff --git a/content/en_security_processes.php b/content/en_security_processes.php
index 15ee9c6..0e8d910 100644
--- a/content/en_security_processes.php
+++ b/content/en_security_processes.php
@@ -44,11 +44,10 @@
<pre>
- [ ] On receipt of a security report via <a href="mailto:security@webtide.com">security@webtide.com</a> or other channels, if it cannot be trivially dismissed (already fixed, known not a problem, etc.), then a <a href="https://github.com/eclipse/jetty.project/security/advisories?state=published">Github security advisory</a> is created by project leadership.</p>
- - [ ] Copy this list as a markdown in the security advisory for tracking the completion of various tasks.
+- [ ] Copy this list as a markdown in the security advisory for tracking the completion of various tasks.
- [ ] Jetty committers and the reporters are added to the security advisory. Individual committers can also be named in the comments for addition.
-
-
+
- [ ] Initial triage and discussion are performed in the comments of the advisory.
- [ ] If enough information exists to attempt reproduction or fix, then a private repository is created as part of the GitHub security advisory.
