-
Notifications
You must be signed in to change notification settings - Fork 561
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
security docs: update capitalization of PSC
This is a nitpick, but I have picked it.
- Loading branch information
Showing
2 changed files
with
3 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -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:[email protected]). | ||
the [Perl Steering Council](mailto:[email protected]). | ||
|
||
When members of the security team reply to your messages, they will | ||
generally include the [email protected] address in the "To" or "CC" | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -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:[email protected]>. | ||
the L<Perl Steering Council|mailto:[email protected]>. | ||
|
||
When members of the security team reply to your messages, they will | ||
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. | |
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:[email protected]>. | ||
L<Perl Steering Council|mailto:[email protected]>. | ||
|
||
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 | ||
|