-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
e659185
commit e25cae2
Showing
5 changed files
with
11 additions
and
27 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
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
This file was deleted.
Oops, something went wrong.
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
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 |
---|---|---|
|
@@ -22,7 +22,6 @@ spawn a disclosure policy for an organization. | |
choose to adopt all of these items wholesale without some modification. | ||
|
||
|
||
Check failure on line 24 in docs/reference/policy_templates/index.md GitHub Actions / lintMultiple consecutive blank lines
|
||
|
||
- :material-feather: [Style Guide](./style_guide.md) | ||
|
||
--- | ||
|
@@ -40,14 +39,4 @@ spawn a disclosure policy for an organization. | |
|
||
</div> | ||
|
||
|
||
{% include-markdown "./_adjust_to_suit.md" %} | ||
{% include-markdown "./_usage.md" %} | ||
|
||
!!! note "Use of RFC 2119 Language" | ||
|
||
We've taken the approach of using [RFC 2119](https://datatracker.ietf.org/doc/html/rfc2119)-style | ||
"MUST, SHALL, SHOULD..." language in active-voice sentences to describe what researchers/reporters and | ||
vendors/coordinators/recipients should expect of each other. | ||
|
||
|