diff --git a/FURPS/core/light_push.md b/FURPS/core/light_push.md
index 7f695ef..8cbf331 100644
--- a/FURPS/core/light_push.md
+++ b/FURPS/core/light_push.md
@@ -3,7 +3,7 @@
 ## Functionality
 
 1. Enables light nodes to push messages to service nodes for relay to the network.
-2. Requests service nodes to publish messages to WAKU2-RELAY pubsub-topics.
+2. Requests service nodes to publish messages to WAKU2-RELAY shards.
 3. Provides confirmation that a message has been received by at least one node.
 4. Supports comprehensive error codes for various failure scenarios.
 
diff --git a/FURPS/core/waku_api.md b/FURPS/core/waku_api.md
index 6628297..582ddd5 100644
--- a/FURPS/core/waku_api.md
+++ b/FURPS/core/waku_api.md
@@ -16,6 +16,7 @@
 2. Disconnection detection and recovery, and other peer management matters are automatically handled.
 3. Developers do not need to specify the protocols used to send and receive messages; it is deduced from the mode of operation.
 4. Developers pass and receive data to the API in types native to the wrapping language.
+5. By default, auto-sharding is applied, meaning developers do not need to be concerned by sharding; pubsub topics are never exposed.
 
 ## Reliability
 
diff --git a/draft-roadmap/improve_devex_api_twn_metrics_docs.md b/draft-roadmap/improve_devex_api_twn_metrics_docs.md
index 472fb90..ad4c00c 100644
--- a/draft-roadmap/improve_devex_api_twn_metrics_docs.md
+++ b/draft-roadmap/improve_devex_api_twn_metrics_docs.md
@@ -87,6 +87,7 @@ Spec delivery not included.
 - U2. Disconnection detection and recovery, and other peer management matters are automatically handled.
 - U3. Developers do not need to specify the protocols used to send and receive messages; it is deduced from the mode of operation.
 - U4. Developers pass and receive data to the API in types native to the wrapping language.
+- U5. By default, auto-sharding is applied, meaning developers do not need to be concerned by sharding; pubsub topics are never exposed.
 - R1. Sends a message using peer-to-peer reliability (service node redundancy, optional store confirmation)
 - R2. Receives messages using peer-to-peer reliability (service node redundancy, periodic store query, periodic filter ping)
 
@@ -113,6 +114,7 @@ For S3. Browser
 - U2. Disconnection detection and recovery, and other peer management matters are automatically handled.
 - U3. Developers do not need to specify the protocols used to send and receive messages; it is deduced from the mode of operation.
 - U4. Developers pass and receive data to the API in types native to the wrapping language.
+- U5. By default, auto-sharding is applied, meaning developers do not need to be concerned by sharding; pubsub topics are never exposed.
 - R1. Sends a message using peer-to-peer reliability (service node redundancy, optional store confirmation)
 - R2. Receives messages using peer-to-peer reliability (service node redundancy, periodic store query, periodic filter ping)