From ef79e51f2d9078d04eebf1d67da4dfb45b5c2493 Mon Sep 17 00:00:00 2001
From: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
Date: Thu, 5 Jun 2025 08:54:54 +0200
Subject: [PATCH] Fix typo in try-esql.md

^^
---
 explore-analyze/discover/try-esql.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/explore-analyze/discover/try-esql.md b/explore-analyze/discover/try-esql.md
index a9cd37809b..9c17d8c576 100644
--- a/explore-analyze/discover/try-esql.md
+++ b/explore-analyze/discover/try-esql.md
@@ -108,7 +108,7 @@ If you’d like to keep the visualization and add it to a dashboard, you can sav
 
 By default, ES|QL identifies time series data when an index contains a `@timestamp` field. This enables the time range selector and visualization options for your query.
 
-If your index doesn’t have an explicit `@timestamp` field, but has a different time field, you can still enable the time range selector and visualization options by calling the `?_start` and `?_tend` parameters in your query.
+If your index doesn’t have an explicit `@timestamp` field, but has a different time field, you can still enable the time range selector and visualization options by calling the `?_tstart` and `?_tend` parameters in your query.
 
 For example, the eCommerce sample data set doesn’t have a `@timestamp` field, but has an `order_date` field.
 
@@ -123,7 +123,7 @@ FROM kibana_sample_data_ecommerce
 :alt: ESQL query without time series capabilities enabled
 :::
 
-While still querying the same data set, by adding the `?_start` and `?_tend` parameters based on the `order_date` field, **Discover** enables times series capabilities.
+While still querying the same data set, by adding the `?_tstart` and `?_tend` parameters based on the `order_date` field, **Discover** enables times series capabilities.
 
 ```esql
 FROM kibana_sample_data_ecommerce