diff --git a/docs/getting-started/concepts/network-domains.md b/docs/getting-started/concepts/network-domains.md
index c3880af..e61fc55 100644
--- a/docs/getting-started/concepts/network-domains.md
+++ b/docs/getting-started/concepts/network-domains.md
@@ -14,7 +14,7 @@ Gossipsub derives its name from the practice within Pub/Sub networks where peers
 
 Waku employs gossiping through [Relay](/getting-started/concepts/protocols#relay) to distribute messages across the network. Additionally, Waku introduces [RLN Relay](/getting-started/concepts/protocols#rln-relay), an experimental mechanism that combines privacy preservation and economic spam protection.
 
-## Request/Reply Domain
+## Request/Response Domain
 
 Waku provides a set of protocols to optimize its performance in resource-limited environments like low bandwidth or offline scenarios for multiple purposes.
 
diff --git a/docs/getting-started/concepts/protocols.md b/docs/getting-started/concepts/protocols.md
index b40809b..73c337f 100644
--- a/docs/getting-started/concepts/protocols.md
+++ b/docs/getting-started/concepts/protocols.md
@@ -30,7 +30,7 @@ Using `Relay` and `Filter` protocols is recommended when a node is online, as `S
 
 ## [Light Push](https://rfc.vac.dev/spec/19/)
 
-`Light Push` is a [Request/Reply](/getting-started/concepts/network-domains#requestreply-domain) protocol for nodes with limited bandwidth and short connection windows. It allows a client to receive an acknowledgment when sending messages, indicating that at least one peer has received them. Subsequently, the remote peer forwards these messages to the `Relay` network.
+`Light Push` is a [Request/Response](/getting-started/concepts/network-domains#requestresponse-domain) protocol for nodes with limited bandwidth and short connection windows. It allows a client to receive an acknowledgment when sending messages, indicating that at least one peer has received them. Subsequently, the remote peer forwards these messages to the `Relay` network.
 
 :::info
 While the `Light Push` protocol acknowledges the receipt by the remote peer, it does not guarantee network-wide propagation.
diff --git a/docs/getting-started/index.md b/docs/getting-started/index.md
index 584966b..ac8eb2d 100644
--- a/docs/getting-started/index.md
+++ b/docs/getting-started/index.md
@@ -49,6 +49,16 @@ Waku nodes are adaptive and can be customized based on the application's require
 
 These options are part of the [Anonymity Trilemma](https://eprint.iacr.org/2017/954.pdf), which Waku addresses through its adjustable protocol.
 
+
+### Service Network
+
+Waku provides developers with a convenient solution for building decentralized communication systems, eliminating the need to start from scratch or depend on centralized systems. Node operators can offer several services, such as:
+
+- Storing messages for offline devices.
+- Enabling bandwidth-saving access to the [Relay](/getting-started/concepts/protocols#relay) network through [Light Push](/getting-started/concepts/protocols#light-push) and [Filter](/getting-started/concepts/protocols#filter) protocols.
+- Implementing spam prevention and DoS mitigation features.
+- Providing a resilient and shared [Relay](/getting-started/concepts/protocols#relay) infrastructure that applications can leverage to enhance reliability and efficiency.
+
 ## How Does Waku Work?
 
 The [Relay](/getting-started/concepts/protocols#relay) protocol is the foundation of the Waku network, which employs a Pub/Sub architecture built on the [libp2p GossipSub protocol](https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/README.md). Additionally, various other Waku protocols have been created to facilitate specific functionalities, including but not limited to:
diff --git a/docs/getting-started/reference/glossary.md b/docs/getting-started/reference/glossary.md
index 72a94bf..a30ebc1 100644
--- a/docs/getting-started/reference/glossary.md
+++ b/docs/getting-started/reference/glossary.md
@@ -84,7 +84,7 @@ A Pub/Sub topic serves as a routing mechanism for messages, with the default top
 
 ### Rate Limit Nullifiers
 
-Rate Limit Nullifiers (RLN) are a construct based on zero-knowledge proofs that provide an anonymous rate-limited messaging framework, preserving message owner anonymity while preventing spam or DDoS attacks.
+Rate Limit Nullifiers (RLN) are a construct based on zero-knowledge proofs that provide an anonymous rate-limited messaging framework, preserving message owner anonymity while preventing spam or DoS attacks.
 
 ### Relay