diff --git a/src/connections/destinations/destination-filters.md b/src/connections/destinations/destination-filters.md
index c3736eedec..47812f7015 100644
--- a/src/connections/destinations/destination-filters.md
+++ b/src/connections/destinations/destination-filters.md
@@ -17,7 +17,8 @@ With Destination Filters, you can:
 
  - Prevent test or internally-generated events from reaching your production tools.
 
- **Note**: Destination Filters are currently available to Business Tier customers only
+ > note ""
+ > **Note**: Destination Filters are currently available to Business Tier customers only.
 
 ### Destination Filtering Limitations
 
diff --git a/src/guides/filtering-data.md b/src/guides/filtering-data.md
index e51883a7e1..7041da651b 100644
--- a/src/guides/filtering-data.md
+++ b/src/guides/filtering-data.md
@@ -44,7 +44,8 @@ Your data is sent to your warehouse (if you have one) and into the Segment backe
 
 [Destination Filters](https://segment.com/docs/connections/destinations/destination-filters/) allow you to control the data flowing into each specific destination, by examining event payloads, and conditionally preventing data from being sent to destinations. You can filter out entire events, or just specific fields in the properties, in the traits, or in the context of your events. Destination filters are not available for, and do not prevent data from reaching your warehouse(s) or S3 destinations.
 
-Destination Filters are available in workspaces that are on a Business Tier plan only.
+> note ""
+> **Note**: Destination Filters are available in workspaces that are on a Business Tier plan only. Destination Filters can only be applied to Cloud-mode ("server-side") streaming destinations. Device-mode destinations are not supported.
 
 ![](images/destination-filter-create.png)