git: 483c73f05d - main - SA/EN templates: clarify referenced hashes / revisions

From: Ed Maste <emaste_at_FreeBSD.org>
Date: Wed, 08 Nov 2023 17:35:04 UTC
The branch main has been updated by emaste:

URL: https://cgit.FreeBSD.org/doc/commit/?id=483c73f05d99f6c36f5c4c056e374a859467e18c

commit 483c73f05d99f6c36f5c4c056e374a859467e18c
Author:     Ed Maste <emaste@FreeBSD.org>
AuthorDate: 2023-11-08 17:03:24 +0000
Commit:     Ed Maste <emaste@FreeBSD.org>
CommitDate: 2023-11-08 17:34:29 +0000

    SA/EN templates: clarify referenced hashes / revisions
    
    A fix may arrive in stable branches as multiple commits (e.g., if there
    is an issue with the initial change).  Update the templates to mention
    that the issue is corrected "as of" the specified hash rather than "by"
    the specified hash.
    
    Reported by:    brooks
    Reviewed by:    delphij, brooks
    Sponsored by:   The FreeBSD Foundation
    Differential Revision: https://reviews.freebsd.org/D42507
---
 website/static/security/advisory-template.txt | 2 +-
 website/static/security/errata-template.txt   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/static/security/advisory-template.txt b/website/static/security/advisory-template.txt
index cb0d7ad288..c28521f6e1 100644
--- a/website/static/security/advisory-template.txt
+++ b/website/static/security/advisory-template.txt
@@ -110,7 +110,7 @@ system.
 
 VI.  Correction details
 
-This issue is corrected by the corresponding Git commit hash or Subversion
+This issue is corrected as of the corresponding Git commit hash or Subversion
 revision number in the following stable and release branches:
 
 Branch/path                             Hash                     Revision
diff --git a/website/static/security/errata-template.txt b/website/static/security/errata-template.txt
index a62c819df8..a93976fe03 100644
--- a/website/static/security/errata-template.txt
+++ b/website/static/security/errata-template.txt
@@ -110,7 +110,7 @@ system.
 
 VI.  Correction details
 
-This issue is corrected by the corresponding Git commit hash or Subversion
+This issue is corrected as of the corresponding Git commit hash or Subversion
 revision number in the following stable and release branches:
 
 Branch/path                             Hash                     Revision