[NO ISSUE][DOC] Update SQL++ design points
- user model changes: no
- storage format changes: no
- interface changes: no
Change-Id: I8ddf7131519b854b1fdde9f56e9b3108d1e294d9
Reviewed-on: https://asterix-gerrit.ics.uci.edu/3033
Sonar-Qube: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: Dmitry Lychagin <dmitry.lychagin@couchbase.com>
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Contrib: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
diff --git a/asterixdb/asterix-doc/src/main/markdown/sqlpp/1_intro.md b/asterixdb/asterix-doc/src/main/markdown/sqlpp/1_intro.md
index e5441ba..8590c2e 100644
--- a/asterixdb/asterix-doc/src/main/markdown/sqlpp/1_intro.md
+++ b/asterixdb/asterix-doc/src/main/markdown/sqlpp/1_intro.md
@@ -26,9 +26,9 @@
SQL++ originated from research in the FORWARD project at UC San Diego, and it has
much in common with SQL; some differences exist due to the different data models that
the two languages were designed to serve.
-SQL was designed in the 1970's for interacting with the flat, schema-ified world of
-relational databases, while SQL++ is much newer and targets the nested, schema-optional
-(or even schema-less) world of modern NoSQL systems.
+SQL was designed for interacting with the flat, schema-ified world of relational
+databases, while SQL++ generalizes SQL to also handle nested data formats (like JSON) and
+the schema-optional (or even schema-less) data models of modern NoSQL and BigData systems.
In the context of Apache AsterixDB, the query language is intended for working with the Asterix Data Model
([ADM](../datamodel.html)), a data model based on a superset of JSON with an enriched and flexible type system.