Skip to content

Commit dcbafa4

Browse files
committed
security docs: update capitalization of PSC
This is a nitpick, but I have picked it.
1 parent 9369621 commit dcbafa4

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

SECURITY.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ membership mailing list monitored by the Perl security team.
1212

1313
You should receive an initial response to your report within 72 hours.
1414
If you do not receive a response in that time, please contact
15-
the [Perl steering council](mailto:[email protected]).
15+
the [Perl Steering Council](mailto:[email protected]).
1616

1717
When members of the security team reply to your messages, they will
1818
generally include the [email protected] address in the "To" or "CC"

pod/perlsecpolicy.pod

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ security team.
2929

3030
You should receive an initial response to your report within 72 hours.
3131
If you do not receive a response in that time, please contact
32-
the L<Perl steering council|mailto:[email protected]>.
32+
the L<Perl Steering Council|mailto:[email protected]>.
3333

3434
When members of the security team reply to your messages, they will
3535
generally include the [email protected] address in the "To" or "CC"
@@ -296,7 +296,7 @@ open and transparent as possible about the state of your security report.
296296
New vulnerability reports will receive an initial reply within 72 hours
297297
from the time they arrive at the security team's mailing list. If you do
298298
not receive any response in that time, contact the
299-
L<Perl steering council|mailto:[email protected]>.
299+
L<Perl Steering Council|mailto:[email protected]>.
300300

301301
The initial response sent by the security team will confirm your message was
302302
received and provide an estimated time frame for the security team's

0 commit comments

Comments
 (0)