From 3f4f1d53a7a647920376ca8571e238872c162cf2 Mon Sep 17 00:00:00 2001
From: Camelid <camelidcamel@gmail.com>
Date: Tue, 13 Oct 2020 11:40:25 -0700
Subject: [PATCH] Bold '@' in @-mentions

Thanks @LeSeulArtichaut! :)
---
 posts/inside-rust/2020-10-08-regression-labels.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/posts/inside-rust/2020-10-08-regression-labels.md b/posts/inside-rust/2020-10-08-regression-labels.md
index 51c8424dc..7edd5085a 100644
--- a/posts/inside-rust/2020-10-08-regression-labels.md
+++ b/posts/inside-rust/2020-10-08-regression-labels.md
@@ -9,7 +9,7 @@ team: the release team <https://www.rust-lang.org/governance/teams/operations#re
 If you've contributed to Rust before, you have likely used a command like this
 to [set labels][rustbot-labeling-docs]:
 
-> @**rustbot** modify labels: A-typesystem C-enhancement
+> **@rustbot** modify labels: A-typesystem C-enhancement
 
 Setting labels on issues and pull requests helps us keep track of and filter
 issues. There are many kinds of labels you can set to mark an issue
@@ -30,7 +30,7 @@ So we have now [added the ability][regression-label-pr] for *anyone* to set
 regression labels on issues! This is all you have to do to mark an issue as a
 regression and it will automatically be prioritized:
 
-> @**rustbot** modify labels: regression-from-stable-to-{release-channel}
+> **@rustbot** modify labels: regression-from-stable-to-{release-channel}
 
 Just replace `{release-channel}` with one of `nightly`, `beta`, or `stable`,
 depending on when the regression occurred, and you're good to go!
@@ -42,7 +42,7 @@ regression and providing information that will help us fix the issue.
 Finally, if you have an issue that is *not* a regression, but is still something
 that is important to be fixed, you can request prioritization with:
 
-> @**rustbot** prioritize
+> **@rustbot** prioritize
 
 We really appreciate it if you mark all regressions with an appropriate label
 so we can track them and fix them as soon as possible!