fix announcement file link

Signed-off-by: vincentgoat <[email protected]>

security-team/comms-templates/distributors-announcement-email.md

@@ -8,7 +8,7 @@ SUBJECT: `[EMBARGOED] $CVE: $SUMMARY`
 
 ### EMBARGOED
 
-The information contained in this email is **[under embargo](https://github.com/kubeedge/community/blob/master/sig-security/private-distributors-list.md#embargo-Policy)** until the scheduled public disclosure on **$DATE, at 9AM PT**.
+The information contained in this email is **[under embargo](https://github.com/kubeedge/community/blob/master/security-team/private-distributors-list.md#embargo-Policy)** until the scheduled public disclosure on **$DATE, at 9AM PT**.
 
 _Additional details on the embargo conditions._
 - _If a patch is provided, can it be deployed?_

security-team/security-release-process.md

@@ -119,7 +119,7 @@ Communications process:
   location of the binaries to get wide distribution and user action. As much as possible this
   announcement should be actionable, and include any mitigating steps users can take prior to
   upgrading to a fixed version. The announcement will be sent via the following channels:
-  - General announcement email ([template](comms-templates/vulnerability-announcement-email.md)) to multiple KubeEdge lists
+  - General announcement email ([template](comms-templates/distributors-announcement-email.md)) to multiple KubeEdge lists
   - [#announcement slack channel](https://kubeedge.slack.com/archives/CUABZBD55) ([template](comms-templates/vulnerability-announcement-slack.md))
   - Tracking issue opened in https://github.com/kubeedge/kubeedge/issues ([template](comms-templates/vulnerability-announcement-issue.md)) and prefixed with the associated CVE ID (if applicable)
   - [GitHub Security Advisories](https://github.com/kubeedge/kubeedge/security/advisories) of KubeEdge