doc: correct typos in security release process

- Double word "the"
- offical -> official
- annoucement -> announcement
PR-URL: #29822
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>

Author: nschonni

doc/guides/security_release_process.md

@@ -19,7 +19,7 @@ a security release.
 *[ ] Co-ordinate with the Release team members to line up one or more releasers
  to do the releases on the agreed date.
 
-*[ ] Prep for the pre-security announcement and final security annoucement by
+*[ ] Prep for the pre-security announcement and final security announcement by
  getting agreement on drafts following the
 [security_announcement_process](https://github.com/nodejs/security-wg/blob/master/processes/security_annoucement_process.md).
 
@@ -50,7 +50,7 @@ a security release.
 
 *[ ] Co-ordinate with the Release team members and keep up to date on progress.
  Get an guesstimate of when releases may be ready and send an FYI to the docker
-offical image
+official image
 [maintainers](https://github.com/docker-library/official-images/blob/master/MAINTAINERS).
 
 *[ ] When the releases are promoted, ensure the final announce goes out as per
@@ -85,7 +85,7 @@ a security release.
  [cve_management_process](https://github.com/nodejs/security-wg/blob/master/processes/cve_management_process.md).
 
 * [ ] Ensure that the announced CVEs are updated in the cve-management
- repository as per the the
+ repository as per the
  [cve_management_process](https://github.com/nodejs/security-wg/blob/master/processes/cve_management_process.md)
  so that they are listed under Announced.