diff --git a/general/security/security-engineer.md b/general/security/security-engineer.md
index 566282c86faaca2e3ef854ccd9170904d8484670..f4927c90ef9b39e4351a3ae5428b427f7f542954 100644
--- a/general/security/security-engineer.md
+++ b/general/security/security-engineer.md
@@ -130,11 +130,11 @@ by going to `0.0.0.0:80` in your browser.
 #### Finalize release
 
 Once blog post on dev.gitlab.org has been reviewed and all packages are ready for
-publishing:
+publishing (the status can be checked in `https://gitlab.com/gitlab-org/release/tasks/-/issues` or in the [slack channel](https://gitlab.slack.com/archives/C0139MAV672)):
 
 * Release manager starts publishing the packages
 * **When the packages are ready to be merged by the Release Team into master branch:** create an MR with the blog post file in https://gitlab.com/gitlab-com/www-gitlab-com.
-  * Destination Directory: `source/releases/posts` by copying the blog post MR that was prepared on `dev.gitlab.org`. 
+  * Destination Directory: `sites/marketing/source/releases/posts` by copying the blog post MR that was prepared on `dev.gitlab.org`. 
   * The file name should be in the format **`YYYY-MM-DD-security-release-gitlab-X.X.X.released.html.md`**
 * Put the link of the new blog post in the email notification request issue as well as the security release issue
 * Make sure the CVE IDs are documented in the corresponding GitLab.com issues and H1 reports