This can be rearranged to be imperative. (Shown without wrapping, and note capitalization in Ports Collection.)

Report security issues specific to the FreeBSD Ports Collection to the <a href="mailto:secteam@FreeBSD.org">FreeBSD Ports Security Team</a>.

(Is that the right email address?)

my apologies for the two files... it is the same path, I just did the diff at a different level

Keep Ben in the loop as he has commented on the bug before (although on a different issue).

The context just before this starts off

<p>All FreeBSD security issues should be reported to the <a
    href="mailto:secteam@FreeBSD.org">FreeBSD Security Team</a>
  or, if a higher level of confidentiality is required, PGP

This proposed addition makes the "All" no longer quite right. Given that the extra context does allow the possibility of non-encrypted mail, I will not make a blocking objection based on the non-existence of a ports-secteam PGP key; however, I will note that the proposed new text gives no guidance on what should be done when reporting an issue specific to the Ports Collection (note, capital 'C', I think) that does require a higher level of confidentiality. If we're going to touch this text, I think it would be useful to say what to do in that case.

ping?