Soften warning about spam email to remove mention of service disruption
What does this MR do?
During discussions surrounding %12.7 release post, it was mentioned that the existing Danger
message regarding spam email checking was a bit severe as there was mention of disruption of GitLab service
. This MR leaves the language discussing the importance of spam detection for the Service Desk email address, but removes the portion mentioning disruption of GitLab service.
Related issues
gitlab-com/www-gitlab-com!37630 (comment 274335669)
Author's checklist
-
Follow the Documentation Guidelines and Style Guide. -
If applicable, update the permissions table. -
Link docs to and from the higher-level index page, plus other related docs where helpful. -
Apply the documentation label.
Review checklist
All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.
1. Primary Reviewer
Minor Change Only - no need for primary review.
* [ ] Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.
2. Technical Writer
-
Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
3. Maintainer
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set. -
If there has not been a technical writer review, create an issue for one using the Doc Review template.