From c70a209ee742f589984cd4b7d3f23ae3f98a7116 Mon Sep 17 00:00:00 2001
From: Sam Pfluger <108141731+Sampfluger88@users.noreply.github.com>
Date: Wed, 11 Jun 2025 08:34:17 -0500
Subject: [PATCH] Fix callout boxes (#29911)
- Removed image.
- Removed unneeded line in callout box.
---
handbook/company/communications.md | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/handbook/company/communications.md b/handbook/company/communications.md
index a55828e0ee..83a36ad6d3 100644
--- a/handbook/company/communications.md
+++ b/handbook/company/communications.md
@@ -386,14 +386,13 @@ _**Note:**_ There are only a few "special" labels that are exceptions to this ru
> If you're adding multiple labels to an issue template, GitHub won't add both labels unless you put them in an array e.g. `labels: ['~air-guitar', ':product']`. To verify the syntax is correct, you can preview the template and make sure each label name is in a separate box.
->
> ***Create an issue from a Slack message***
>
> If you need to track content from a Slack channel (e.g. #help-customers), you can automatically generate a GitHub issue by adding the emoji `create-github-issue` as a reaction to any message. This will automatically:
> - Create an issue tagged with the departmental GitHub label that corresponds with the Slack channel. If there isn't a corresponding departmental label for the channel, the issue defaults to the [#g-digital-experience](https://github.com/fleetdm/confidential/issues#workspaces/g-digital-experience-6451748b4eb15200131d4bab/board) kanban board.
-> - Link the
+