diff --git a/.DS_Store b/.DS_Store
index 9f3c7cfc..120629ae 100644
Binary files a/.DS_Store and b/.DS_Store differ
diff --git a/doc/batch_queries.md b/doc/batch_queries.md
index cee5d8d3..46c6bdf5 100644
--- a/doc/batch_queries.md
+++ b/doc/batch_queries.md
@@ -482,7 +482,7 @@ In some scenarios, you may need to fetch the output of a job. If that is the cas
 
 For best practices, follow these recommended usage notes when using Batch Queries:
 
-- Batch Queries are recommended for INSERT, UPDATE, and CREATE queries that manipulate and create new data, such as creating expensive indexes, applying updates over large tables, and creating tables from complex queries. Batch queries will **not** improve processing times for SELECT queries that retrieve data but do not store the results in a table
+- Batch Queries are recommended for INSERT, UPDATE, and CREATE queries that manipulate and create new data, such as creating expensive indexes, applying updates over large tables, and creating tables from complex queries. Batch queries have no effect for SELECT queries that retrieve data but do not store the results in a table. For example, running a batch query using `SELECT * from my_dataset` will not produce any results
 
 - Batch Queries are not intended for large query payloads (e.g: inserting thousands of rows), use the [Import API](https://carto.com/docs/carto-engine/import-api/) for this type of data management