diff --git a/data-explorer/kusto-emulator-overview.md b/data-explorer/kusto-emulator-overview.md
index e0997528cc..ae64e82d16 100644
--- a/data-explorer/kusto-emulator-overview.md
+++ b/data-explorer/kusto-emulator-overview.md
@@ -3,7 +3,7 @@ title: Azure Data Explorer Kusto emulator overview
 description: In this article, you learn about the Azure Data Explorer Kusto emulator.
 ms.reviewer: vplauzon
 ms.topic: conceptual
-ms.date: 06/30/2025
+ms.date: 09/30/2025
 ---
 # Azure Data Explorer Kusto emulator
 
@@ -23,7 +23,7 @@ The emulator is available as a *Linux* Docker container image. It exposes a quer
 
 The emulator supports all commands and queries within its [architecture limitations](#limitations). For instance, [Row Level Security policy commands](/kusto/management/row-level-security-policy?view=azure-data-explorer&preserve-view=true) are supported but since there's no authentication in the emulator, they aren't useful.
 
-The emulator doesn't include the [data management service](ingest-data-overview.md) and hence doesn't support queued, managed, or streaming ingestion. However, you can ingest data using [ingestion commands](/kusto/management/data-ingestion/ingest-from-query?view=azure-data-explorer&preserve-view=true). Data can be ingested from local files, [external tables](/kusto/query/schema-entities/external-tables?view=azure-data-explorer&preserve-view=true), or [external data](/kusto/query/externaldata-operator?pivots=azuredataexplorer?view=azure-data-explorer&preserve-view=true). By default, ingested data is persisted on the disk within the container; hence, the data is as transient as the container itself. If you want to retain the data, you can persist it outside the container by mounting a volume on the container and persisting the data to the volume.
+The emulator doesn't include the [data management service](ingest-data-overview.md) and hence doesn't support queued (managed) ingestion. However, you can ingest data using [ingestion commands](/kusto/management/data-ingestion/ingest-from-query?view=azure-data-explorer&preserve-view=true) or [streaming ingestion] (ingest-data-streaming.md). Data can be ingested from local files, [external tables](/kusto/query/schema-entities/external-tables?view=azure-data-explorer&preserve-view=true), or [external data](/kusto/query/externaldata-operator?pivots=azuredataexplorer?view=azure-data-explorer&preserve-view=true). By default, ingested data is persisted on the disk within the container; hence, the data is as transient as the container itself. If you want to retain the data, you can persist it outside the container by mounting a volume on the container and persisting the data to the volume.
 
 ## Kusto emulator scenarios