From 49edb037129ad8bd3b58a0ca5182491ec709eb31 Mon Sep 17 00:00:00 2001 From: Oleks V Date: Mon, 9 Dec 2024 09:09:02 -0800 Subject: [PATCH] Apply suggestions from code review --- docs/source/user-guide/sql/dialect.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/source/user-guide/sql/dialect.md b/docs/source/user-guide/sql/dialect.md index c91bace73358..fd0a859a2cf7 100644 --- a/docs/source/user-guide/sql/dialect.md +++ b/docs/source/user-guide/sql/dialect.md @@ -19,7 +19,7 @@ # SQL Dialect -By default, DataFusion follows the [PostgreSQL SQL dialect]. +By default, Apache DataFusion follows the [PostgreSQL SQL dialect]. For Array/List functions and semantics, it follows the [DuckDB SQL dialect]. [duckdb sql dialect]: https://duckdb.org/docs/sql/functions/array @@ -33,6 +33,6 @@ semantics exactly (need bug-for-bug compatibility), and is likely not what all users want. However, it avoids the (very significant) effort of defining semantics as well as documenting and teaching users about them. -As DataFusion is highly customizable, systems built on DataFusion can and do -update functions and SQL syntax to model other systems, such as Spark or +As Apache DataFusion is highly customizable, systems built on DataFusion can and do +update functions and SQL syntax to model other systems, such as Apache Spark or MySQL.