support/security: s/herd/project

Gentoo hasn't used 'herd' since GLEP 67 was implemented in 2015.

Signed-off-by: Sam James <sam@gentoo.org>

1 files changed, 1 insertions, 1 deletions

diff --git a/support/security/vulnerability-treatment-policy.html b/support/security/vulnerability-treatment-policy.html
index 5676ee7..2180205 100644
--- a/support/security/vulnerability-treatment-policy.html
+++ b/support/security/vulnerability-treatment-policy.html
@@ -308,7 +308,7 @@ You can use the following two tables to help you assign the severity level:
     if no upstream fix is available (<code>upstream+</code> status), a decision must be taken on masking the package:
     The Security Team can mask a package which is not depended on by itself, maintainers should be consulted before masking a package which is not standalone
   </li>
-  <li>if the maintainer/herd does not show up for producing the ebuild during 48 hours after summoning (<code>ebuild+</code> status), the Security Team should try to bump the ebuild by itself</li>
+  <li>if the maintainer/project does not show up for producing the ebuild during 48 hours after summoning (<code>ebuild+</code> status), the Security Team should try to bump the ebuild by itself</li>
   <li>
     if testing and marking stable takes too much time (<code>stable+</code> status), the Security Team will shout on IRC channels and gentoo-dev list to get more testers.
     It will either mark the ebuild stable by itself or, in the event this cannot be done due to stability issues, mask it (see security masking approval policy above)