Remove the disclaimer and add a few sentences for Infinigraph

Author: renetapopova

modules/ROOT/content-nav.adoc

@@ -173,7 +173,7 @@
 *** xref:scalability/composite-databases/querying-composite-databases.adoc[]
 *** xref:scalability/composite-databases/sharding-with-copy.adoc[]
 //*** xref:scalability/composite-databases/scaling-with-composite-databases.adoc[]
-** Property sharding (Preview feature)
+** Property sharding (Infinigraph)
 *** xref:scalability/sharded-property-databases/overview.adoc[]
 *** xref:scalability/sharded-property-databases/planning-and-sizing.adoc[]
 *** xref:scalability/sharded-property-databases/configuration.adoc[]

modules/ROOT/pages/scalability/concepts.adoc

@@ -8,7 +8,7 @@ The three main strategies are:
 
 * xref:clustering/setup/analytics-cluster.adoc[Analytics clustering] -- for horizontal read scalability.
 * xref:scalability/composite-databases/concepts.adoc[Composite databases] -- for federated queries and distributed data management.
-* xref:scalability/sharded-property-databases/overview.adoc[Property sharding] -- for handling massive property-heavy graphs.
+* xref:scalability/sharded-property-databases/overview.adoc[Property sharding] (part of Infinigraph) -- for handling massive property-heavy graphs.
 
 == What is scalability?
 

modules/ROOT/pages/scalability/scaling-with-neo4j.adoc

@@ -2,7 +2,10 @@
 :description: Scaling strategies with Neo4j.
 = Scaling with Neo4j
 
-Neo4j offers various options for scaling, tailored to specific use cases and requirements. Here are some of the supported scaling strategies:
+Neo4j offers various options for scaling, tailored to specific use cases and requirements.
+You can mix and match these strategies to create a scalable solution that meets your needs.
+
+Here are some of the supported scaling strategies:
 
 * *Data replication via Neo4j analytics clustering (read scalability)* -- A Neo4j cluster is a high-availability cluster with multi-DB support.
 It is a collection of servers running Neo4j that are configured to communicate with each other.
@@ -34,7 +37,7 @@ The main advantage is obtained by combining Neo4j clustering and composite datab
 * *Data distribution via Infinigraph* -- using a distributed graph architecture to extend a single system without fragmenting the graph.
 //This allows, in theory, the unlimited growth of a graph.
 +
-label:preview[Preview feature] xref:scalability/sharded-property-databases/overview.adoc[Property sharding] (part of Infinigraph) allows you to decouple the properties attached to nodes and relationships and store them in separate graphs.
+xref:scalability/sharded-property-databases/overview.adoc[Property sharding] (part of Infinigraph) allows you to decouple the properties attached to nodes and relationships and store them in separate graphs.
 This architecture enables the independent scaling of property data, allowing for the handling of high volumes, heavy queries, and high read concurrency.
 
 The following table summarizes the similarities and differences between analytics clustering, composite databases, and sharded property databases:
@@ -110,7 +113,7 @@ Tools used on individual shards and Bloom are not supported on composite databas
 //TODO
 //Admin considerations
 
-// == Property sharding (Preview feature)
+// == Property sharding
 
 // Sharded property databases
 

modules/ROOT/pages/scalability/sharded-property-databases/configuration.adoc

@@ -14,9 +14,6 @@ To enable the property sharding in your cluster, you must configure the followin
 |===
 | Configuration setting | Description
 
-| internal.dbms.sharded_property_database.enabled=true
-| By default, the sharded property database is disabled.footnote:[Property sharding is a preview feature. For details, see xref:scalability/sharded-property-databases/overview.adoc[Property sharding overview].]
-
 | db.query.default_language=CYPHER_25
 | Ensures that any database created will use Cypher 25 (unless users specifically override the default version in the `CREATE DATABASE` command).
 See xref:configuration/cypher-version-configuration.adoc[Configure the Cypher default version] and link:https://neo4j.com/docs/cypher-manual/current/queries/select-version/[Cypher Manual -> Select Cypher version].

modules/ROOT/pages/scalability/sharded-property-databases/overview.adoc

@@ -2,27 +2,12 @@
 :description: This page describes property sharding and how it works.
 = Overview
 
-.Preview Feature
-[IMPORTANT]
-====
-The *property sharding feature is offered AS-IS* as described in your agreement with Neo4j and should only be used for internal development purposes.
-
-When this feature becomes generally available, you will need to upgrade to the latest Neo4j version (which may require downtime) to use the feature for non-development purposes.
-
-*Enabling the preview feature (internal parameter):* +
-By default, the sharded property database is disabled.
-Use the internal setting `internal.dbms.sharded_property_database.enabled=true` to enable it.
-
-During the Preview period, if you have any feedback, comments, or encounter any issues, we welcome them in our link:https://github.com/neo4j/neo4j/issues[public GitHub repository].
-We will address them to the best of our ability.
-Please include the term *Infinigraph* or *property sharding* in the title of your issue so we can identify it more easily. +
-Customers with active contracts may contact Neo4j Support through the standard support channels.
-Please note that any cases related to the Preview feature will be classified as Severity 4 by default, in accordance with the link:https://neo4j.com/terms/support-terms/[Support Terms].
-====
+Property sharding is part of Infinigraph, Neo4j’s distributed graph architecture that uses sharding to distribute the graph’s property data across different members of a cluster.
+The graph remains logically intact, queries behave as expected, and applications scale without requiring code changes or manual workarounds.
 
 == What is property sharding?
 
-Property sharding is about decoupling the properties associated with nodes and relationships, and storing them in separate graphs.
+Property sharding involves decoupling the properties associated with nodes and relationships, and storing them in separate graphs.
 The graph structure, comprising nodes and relationships, is stored in a single "graph shard".
 The properties associated with these nodes and relationships are distributed across multiple "property shards".
 This architecture enables the independent scaling of property data, allowing for the handling of larger volumes of properties without impacting the performance of the graph structure. +