Updated the review comment feedback from SME.

src/content/docs/service-architecture-intelligence/maps/dynamic-flow-map.mdx

@@ -10,11 +10,11 @@ redirects:
 freshnessValidatedDate: never
 ---
 
-<DNT>**Dynamic Flow Map**</DNT> is a visualization tool that displays aggregated trace data in a map view. It focuses on a specific service (called the focal node) and reveals how performance changes in upstream and downstream services affect each other. By highlighting anomalous latency and errors in traffic between services, the map helps you quickly identify performance bottlenecks and trace issues to their root cause.
+<DNT>**Dynamic Flow Map**</DNT> is a visualization tool that displays aggregated trace data in a map view. It focuses on a specific service (called the focal node) and reveals how performance changes in upstream and downstream services affect each other. By highlighting correlated anomalous latency and errors in traffic between services, the map helps you quickly identify performance bottlenecks and trace issues to their root cause.
 
 ## Why it matters [#why-it-matters]
 
-<DNT>**Dynamic Flow Map**</DNT> reduces mean time to resolution by surfacing performance anomalies visually. Instead of manually analyzing traces to understand service relationships, you can see at a glance which services are experiencing issues and how those issues correlate with the focal node. The color-coded visualization of anomalous edges and nodes lets you quickly identify where latency or errors are occurring in your distributed system.
+<DNT>**Dynamic Flow Map**</DNT> reduces mean time to resolution by surfacing performance anomalies visually. Instead of manually analyzing traces to understand service relationships, you can see at a glance which services are experiencing issues and how those issues correlate with the focal node. The color-coded visualization shows you where latency or errors that are correlated with the focal entity's performance are occurring in your distributed system.
 
 For general map navigation and interface controls shared across all New Relic maps, see [Maps](/docs/service-architecture-intelligence/maps/advanced-maps).
 
@@ -88,7 +88,7 @@ The <DNT>**Dynamic Flow Map**</DNT> shows relationships between the focal node a
  * **Pink dot**: The service is experiencing error anomalies.
 
 <Callout variant="tip">
-If you see a node with an anomaly dot but the connecting edge isn't color-coded, the anomalies aren't correlated. This happens because edge colors and node dots are calculated independently. Select the entity with the anomaly and check the sidebar's time series charts to see if the anomalies occurred at different times.
+If you see a node with an anomaly dot but some connecting edges aren't color-coded, this is because anomalies are calculated independently for nodes and edges. For example, a latency anomaly might only occur along some of the call paths to that entity.
 </Callout>
 
  ### Filter anomalies by type
@@ -122,6 +122,10 @@ If you see a node with an anomaly dot but the connecting edge isn't color-coded,
  * You can select individual entities only. Clusters cannot be added.
  * The focal node always remains in the filter and cannot be removed.
 
+ <Callout variant="tip">
+ When filtering by multiple entities, you may get an empty map if those entities don't appear together in any trace. To avoid this, apply one entity filter at a time to incrementally narrow down the map.
+ </Callout>
+
 </Collapser>
 <Collapser id="performance-trends" title="View detailed entity information">
  When you need to investigate a specific service's performance and its relationship with the focal node, click any entity on the map to open a detailed sidebar.