diff --git a/content/integrations/overview.mdx b/content/integrations/overview.mdx
index 193417e75..89113cfb9 100644
--- a/content/integrations/overview.mdx
+++ b/content/integrations/overview.mdx
@@ -104,7 +104,7 @@ To add a condition to a channel's environment configuration, navigate to **Chann
 Knock will execute your channel conditions for every step using the given channel across all your workflow runs. Knock will join these channel conditions with any [step conditions](/designing-workflows/step-conditions) via an `AND`, meaning both channel and step conditions will need to pass evaluation for the step to execute. You can then use Knock's [conditions debugger](/concepts/conditions#debugging-conditions) to examine the evaluations of your channel conditions.
 
 <Callout
-  emoji="💡"
+  type="info"
   title="Channel conditions don't override sandbox mode."
   text="If sandbox mode is enabled for a channel, Knock skips execution entirely and channel conditions are not evaluated. Disable sandbox mode for conditions to take effect."
 />
@@ -116,7 +116,7 @@ You may encounter a use case where you consistently want to send the same templa
 Channel groups solve this problem. With a channel group, you can combine multiple providers into a single channel that you can use to send the a single notification template across multiple providers. As an example, I could have a "Push" channel group that hosts my connections for APNs and FCM, then use that single "Push" step for any workflows where I want to notify users across my mobile apps.
 
 <Callout
-  emoji="🚧"
+  type="beta"
   title="Request channel groups."
   text={
     <>