apply suggestions from review

Author: renetapopova

modules/ROOT/pages/database-administration/composite-databases/concepts.adoc

@@ -8,15 +8,15 @@ A composite database is a special type of database.
 Composite databases are the means to access this partitioned data or graphs with a single Cypher query.
 
 Composite databases *do not store data* independently.
-They contain _database aliases_ that target the local or remote databases (the so-called _constituents_) that constitute a fabric setup.
+They contain _database aliases_ that target the local or remote databases (the so-called _constituents_).
 Local database aliases target databases within the same DBMS, while remote database aliases target databases from another Neo4j DBMS.
 For more information, see xref:database-administration/aliases/manage-aliases-composite-databases.adoc[].
 
 Composite databases are managed using Cypher administrative commands.
 For a detailed example of how to create a Composite database and add database aliases to it, see xref:database-administration/composite-databases/querying-composite-databases.adoc[Set up and query composite databases].
 
-Composite databases cannot guarantee compatibility between constituents from different long-term support (LTS) versions of Neo4j.
-Therefore, all constituents should belong to the same LTS version.
+Composite databases cannot guarantee compatibility between constituents from different Neo4j versions.
+Constituents from versions without breaking changes should work fine, apart from newly-added features.
 If a new feature is introduced, its availability will be limited to the intersection of features available for all constituents.
 
 Composite databases have the following characteristics:
@@ -26,9 +26,10 @@ Composite databases have the following characteristics:
 * Can be deployed in standalone and cluster deployments.
 * Managed using Cypher commands, such as `CREATE COMPOSITE DATABASE` and `CREATE ALIAS`.
 * You can shard an existing database with the help of the `neo4j-admin copy` command.
-* Use the same user credentials as the database aliases.
-* Do not support database management.
-Any database management commands, index and constraint management commands, or user and security management commands must be issued directly to the DBMSs and databases, not the Composite databases.
+See xref:database-administration/composite-databases/sharding-with-copy.adoc[Sharding data with the copy command] for details.
+* Use the existing user for local constituents or the user credentials defined by the remote aliases for remote consituents.
+* Do not support privileges, index, and constraint management commands.
+These must be defined on the constituent target database in the respective DBMS.
 * Allow only transactions with queries that read from multiple graphs, or read from multiple graphs and write to a single graph.
 * Do not support Neo4j embedded in Java applications.
 Composite databases can be used only in a typical client/server mode when users connect to a Neo4j DBMS from their client application or tool via Bolt or HTTP protocol.