From c6a83f3899ece6484b7ff26ee5b2d6d53295f578 Mon Sep 17 00:00:00 2001 From: Andrew Lamb Date: Wed, 11 Dec 2024 07:40:35 -0500 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Piotr Findeisen --- docs/source/user-guide/sql/dialect.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/source/user-guide/sql/dialect.md b/docs/source/user-guide/sql/dialect.md index 7fae7e1ca0b4..b2c397bc344a 100644 --- a/docs/source/user-guide/sql/dialect.md +++ b/docs/source/user-guide/sql/dialect.md @@ -22,7 +22,7 @@ The included SQL supported in Apache DataFusion mostly follows the [PostgreSQL SQL dialect], including: -- The sql parser and [SQL planner] +- The SQL parser and [SQL planner] - Type checking, analyzer, and type coercions - Semantics of functions bundled with DataFusion @@ -33,7 +33,7 @@ Notable exceptions: - DataFusion has its own syntax (dialect) for certain operations (like [`CREATE EXTERNAL TABLE`]) As Apache DataFusion is designed to be fully customizable, systems built on -DataFusion can and do implement different SQL semantics. Using DataFusion's APs, +DataFusion can and do implement different SQL semantics. Using DataFusion's APIs, you can provide alternate function definitions, type rules, and/or SQL syntax that matches other systems such as Apache Spark or MySQL or your own custom semantics.