ai-supported edit

Author: renejeglinsky

guides/databases/cdl-to-ddl.md

@@ -439,9 +439,9 @@ CREATE TABLE Books (
 
 ### Invalid Names
 
-When you use names in your CDS models that conflict with reserved words of underlying databases, or names that contain non-ASCII characters, special characters, or spaces, these names are considered invalid in many databases, and are therefore escaped by CAP in the generated DDL, and all queries sent to the database.
+When you use names in your CDS models that conflict with reserved words of underlying databases, or names that contain non-ASCII characters, special characters, or spaces, these names are considered invalid in many databases. CAP escapes these names in the generated DDL and all queries sent to the database.
 
-For example, the following is a valid CDS model, with all database-invalid named elements, so the generated DDL will escape them accordingly with double quotes:
+For example, the following is a valid CDS model with database-invalid named elements. The generated DDL escapes them with double quotes:
 
 ::: code-group
 ```cds [CDS Source]
@@ -491,7 +491,7 @@ If a constraint violation occurs, the error messages coming from the database ar
 
 ### Primary Key Constraints
 
-Primary keys defined in CDS entities are translated into SQL `PRIMARY KEY` constraints in the generated DDL. For example:
+The compiler translates primary keys defined in CDS entities into SQL `PRIMARY KEY` constraints in the generated DDL. For example:
 
 ::: code-group
 ```cds [CDS Source]
@@ -567,7 +567,7 @@ annotate OrderItems with @assert.unique.someOtherConstraint: [ ... ];
 
 - The argument is expected to be an array of flat [element references](../../cds/cdl#annotation-values) referring to elements in the entity. These elements may have the following types:
 
-  - scalar types, i.e., `String`, `Integer`, etc.
+  - scalar types - `String`, `Integer`, and so on
   - structured types – **not** elements _within_ structs.
   - _managed_ associations – **not** _unmanaged_ associations.
 
@@ -626,7 +626,7 @@ entity Books {
 
 #### Deferred Enforcement
 
-Referential integrity is enforced at the time of transaction commit by using the databases [deferred foreign key constraints](https://www.sqlite.org/foreignkeys.html), which is supported by most relational databases, including SAP HANA, SQLite, and PostgreSQL, but not for H2, hence:
+Referential integrity is enforced at the time of transaction commit. This uses the database's [deferred foreign key constraints](https://www.sqlite.org/foreignkeys.html), which are supported by most relational databases, including SAP HANA, SQLite, and PostgreSQL. However, H2 does not support deferred constraints:
 
 > [!note]  Database constraints are not supported for H2
 

guides/databases/cql-to-sql.md

@@ -1,6 +1,6 @@
 # CDS Compilation to Database-Specific SQL
 
-CAP supports a number of portable functions and operators in CQL, which are automatically translated to the best-possible database-specific native SQL equivalents. These can safely be used in CDS view definitions as well as in runtime queries expressed in CQL.
+CAP supports a number of portable functions and operators in CQL. The compiler automatically translates these to the best-possible database-specific native SQL equivalents. You can safely use these in CDS view definitions and runtime queries expressed in CQL.
 {.abstract}
 
 [[toc]]
@@ -19,7 +19,7 @@ In addition, CQL provides some extended operators as described below.
 
 ### Bivalent `==` and `!=` Operators
 
-CQL supports `==` and `!=` operators as bivalent logic variants for SQL's three-valued logic `=` and `<>`. In essence, the differences are as follows:
+CQL supports `==` and `!=` operators as bivalent logic variants for SQL's three-valued logic `=` and `<>`. The differences are as follows:
 
 ::: code-group
 ```SQL [CQL's Two-Valued Logic Operators]
@@ -52,7 +52,7 @@ The result set includes all books where genre is not 'Science Fiction', includin
 The CQL behavior is consistent with common programming languages like JavaScript and Java, as well as with OData semantics. It is implemented in database by, the translation of `!=` to `IS NOT` in SQLite, or to `IS DISTINCT FROM` in standard SQL, and to an equivalent polyfill in SAP HANA.
 
 > [!tip] Prefer == and !=
-> Prefer using  `==` and `!=` in the very most cases to avoid unexpected `null` results. Only use `=` and `<>` if you _really_ want SQL's three-valued logic behavior.
+> Prefer using `==` and `!=` in most cases to avoid unexpected `null` results. Only use `=` and `<>` if you _really_ want SQL's three-valued logic behavior.
 
 ### Ternary `?:` Operator
 
@@ -74,14 +74,14 @@ FROM Books;
 ```
 :::
 
-This operator is translated to the best-possible equivalent in the target database, for example to `CASE WHEN ... THEN ... ELSE ... END` in standard SQL, or to `IF(..., ..., ...)` in SAP HANA.
+The compiler translates this operator to the best-possible equivalent in the target database: `CASE WHEN ... THEN ... ELSE ... END` in standard SQL, or `IF(..., ..., ...)` in SAP HANA.
 
 
 ## Functions
 
 ### Portable Functions
 
-Following are portable functions guaranteed by CAP. These can safely be used in CDS view definitions as well as in runtime queries expressed in CQL, and are translated to the best-possible database-specific native SQL equivalents.
+Following are portable functions supported by CAP. You can safely use these in CDS view definitions and runtime queries expressed in CQL. The compiler translates them to the best-possible database-specific native SQL equivalents.
 
 String functions: