diff --git a/docs/modules/wan/pages/wan.adoc b/docs/modules/wan/pages/wan.adoc
index a797d22de..be09b923b 100644
--- a/docs/modules/wan/pages/wan.adoc
+++ b/docs/modules/wan/pages/wan.adoc
@@ -38,9 +38,9 @@ events and replicates them actively to other clusters.
 * Passive cluster: The user updates performed on this cluster are not replicated to other clusters. In other words,
 this cluster can be seen as the "target" cluster which is capable of receiving, applying and possibly forwarding
 WAN events from other ("active") clusters. It does not generate any WAN update events because of user interaction.
-* WAN publisher: A publisher is a sink for WAN events and an implementation of `WanReplicationPublisher`.
-Most often, this is a single, entire target Hazelcast cluster but you can also define custom publishers which
-may transmit WAN events to other systems such as messaging queues, Kafka or even persist events on disk.
+* WAN publisher: A publisher acts as a sink for local WAN events and pushes them to a target. The target is usually another Hazelcast cluster.
+However, you could also use a customized target such as a message queue, Kafka, or saving data to persistent storage. You can provide a custom target
+by implementing the `WanPublisher` interface. For further information, see https://docs.hazelcast.org/docs/{full-version}/javadoc/com/hazelcast/wan/WanPublisher.html[WanPublisher interface^] documentation.
 * WAN endpoint: when a publisher is replicating events to another Hazelcast cluster, an endpoint is a single member
 in that target cluster. That means that a WAN publisher replicates to multiple WAN endpoints.
 * WAN replication scheme: a named collection of WAN publishers. Hazelcast maps and caches are configured to
@@ -48,6 +48,6 @@ replicate to a WAN replication scheme, meaning that a single map/cache update ca
 clusters or multiple external systems.
 * WAN publisher ID: A unique identifier for a specific WAN replication publisher in a WAN replication scheme. This
 identifier can then be used to control the behavior of a WAN replication publisher while the source/active cluster is
-running. For instance, you can use this identifier in combination with the WAN replication scheme name to pause, stop or
-resume WAN replication for that specific publisher. Or, you can trigger synchronization with a specific target cluster
-and so on.
\ No newline at end of file
+running. For example, you could use the WAN Publisher ID as follows:
+** In combination with the WAN replication scheme name to pause, stop, or resume WAN replication for a specific publisher
+** To trigger synchronization with a specific target cluster