diff options
| -rw-r--r-- | SECURITY.md | 2 | ||||
| -rw-r--r-- | pod/perlsecpolicy.pod | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/SECURITY.md b/SECURITY.md index 9db7be6a9f..d96ea12964 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -12,7 +12,7 @@ membership mailing list monitored by the Perl security team. You should receive an initial response to your report within 72 hours. If you do not receive a response in that time, please contact -the [Perl steering council](mailto:steering-council@perl.org). +the [Perl Steering Council](mailto:steering-council@perl.org). When members of the security team reply to your messages, they will generally include the perl-security@perl.org address in the "To" or "CC" diff --git a/pod/perlsecpolicy.pod b/pod/perlsecpolicy.pod index 41ef5255fb..a982dc7176 100644 --- a/pod/perlsecpolicy.pod +++ b/pod/perlsecpolicy.pod @@ -29,7 +29,7 @@ security team. You should receive an initial response to your report within 72 hours. If you do not receive a response in that time, please contact -the L<Perl steering council|mailto:steering-council@perl.org>. +the L<Perl Steering Council|mailto:steering-council@perl.org>. When members of the security team reply to your messages, they will generally include the perl-security@perl.org address in the "To" or "CC" @@ -296,7 +296,7 @@ open and transparent as possible about the state of your security report. New vulnerability reports will receive an initial reply within 72 hours from the time they arrive at the security team's mailing list. If you do not receive any response in that time, contact the -L<Perl steering council|mailto:steering-council@perl.org>. +L<Perl Steering Council|mailto:steering-council@perl.org>. The initial response sent by the security team will confirm your message was received and provide an estimated time frame for the security team's |