1 files changed, 3 insertions, 3 deletions

diff --git a/doc/user/project/issues/confidential_issues.md b/doc/user/project/issues/confidential_issues.md
index 5bb8805159a..02cb0313a74 100644
--- a/doc/user/project/issues/confidential_issues.md
+++ b/doc/user/project/issues/confidential_issues.md
@@ -1,7 +1,7 @@
 ---
 stage: Plan
 group: Project Management
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 ---
 
 # Confidential issues
@@ -46,7 +46,7 @@ system note in the issue's comments.
 
 ## Indications of a confidential issue
 
-NOTE: **Note:**
+NOTE:
 If you don't have [enough permissions](#permissions-and-access-to-confidential-issues),
 you won't be able to see the confidential issues at all.
 
@@ -100,7 +100,7 @@ confidential information prematurely. When the confidential commits are ready
 to be made public, this can be done by opening a merge request from the private
 fork to the public upstream project.
 
-TIP: **Best practice:**
+NOTE:
 If you create a long-lived private fork in the same group or in a sub-group of
 the original upstream, all the users with Developer membership to the public
 project will also have the same permissions in the private project. This way,