This is an automated email from the ASF dual-hosted git repository.

pjfanning pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pekko.git


The following commit(s) were added to refs/heads/main by this push:
     new e9b96ad44c cherry pick some doc fixes (#2956)
e9b96ad44c is described below

commit e9b96ad44c69120cd3ae381656c3e7f56ada096f
Author: PJ Fanning <[email protected]>
AuthorDate: Sat May 9 17:52:27 2026 +0100

    cherry pick some doc fixes (#2956)
---
 docs/src/main/paradox/additional/deploying.md  | 6 +++---
 docs/src/main/paradox/additional/operations.md | 2 +-
 docs/src/main/paradox/common/other-modules.md  | 2 +-
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/src/main/paradox/additional/deploying.md 
b/docs/src/main/paradox/additional/deploying.md
index 10cc2b07c2..c8eadef86b 100644
--- a/docs/src/main/paradox/additional/deploying.md
+++ b/docs/src/main/paradox/additional/deploying.md
@@ -10,8 +10,8 @@ Deploy to Kubernetes according to the guide and example 
project for [Deploying a
 ### Cluster bootstrap
 
 To take advantage of running inside Kubernetes while forming a cluster, 
-[Pekko Cluster 
Bootstrap]($pekko.doc.dns$/docs/pekko-management/current/bootstrap/) helps 
forming or joining a cluster using Pekko Discovery to discover peer nodes. 
-with the Kubernetes API or Kubernetes via DNS.  
+[Pekko Cluster 
Bootstrap]($pekko.doc.dns$/docs/pekko-management/current/bootstrap/) helps 
forming or joining a cluster using Pekko Discovery with
+the Kubernetes API or Kubernetes via DNS to discover peer nodes.
 
 You can look at the
 @java[[Cluster with Kubernetes example 
project](https://github.com/apache/pekko-samples/tree/main/pekko-sample-cluster-kubernetes-java)]
@@ -29,7 +29,7 @@ that you will need to take special care with the network 
configuration when usin
 described here: @ref:[Pekko behind NAT or in a Docker 
container](../remoting-artery.md#remote-configuration-nat-artery)
 
 You can look at the
-@java[[Cluster with docker-compse example 
project](https://github.com/apache/pekko-samples/tree/main/pekko-sample-cluster-docker-compose-java)]
+@java[[Cluster with docker-compose example 
project](https://github.com/apache/pekko-samples/tree/main/pekko-sample-cluster-docker-compose-java)]
 @scala[[Cluster with docker-compose example 
project](https://github.com/apache/pekko-samples/tree/main/pekko-sample-cluster-docker-compose-scala)]
 to see what this looks like in practice.
 
diff --git a/docs/src/main/paradox/additional/operations.md 
b/docs/src/main/paradox/additional/operations.md
index c2e8a10579..1865e7f7a2 100644
--- a/docs/src/main/paradox/additional/operations.md
+++ b/docs/src/main/paradox/additional/operations.md
@@ -32,7 +32,7 @@ See @ref:[Rolling Updates, Cluster Shutdown and Coordinated 
Shutdown](../additio
 
 There are several management tools for the cluster. 
 Complete information on running and managing Pekko applications can be found 
in 
-the @exref:[Pekko Management](pekko-management:) project documentation.
+the @extref:[Pekko Management](pekko-management:) project documentation.
 
 <a id="cluster-http"></a>
 ### HTTP
diff --git a/docs/src/main/paradox/common/other-modules.md 
b/docs/src/main/paradox/common/other-modules.md
index 0298575f42..c59a5951a7 100644
--- a/docs/src/main/paradox/common/other-modules.md
+++ b/docs/src/main/paradox/common/other-modules.md
@@ -1,6 +1,6 @@
 # Other Apache Pekko modules
 
-This page describes modules that compliment libraries from the Pekko core.  
See [this 
overview]($pekko.doc.dns$/docs/pekko/current/typed/guide/modules.html) instead 
for a guide on the core modules.
+This page describes modules that complement libraries from the Pekko core.  
See [this 
overview]($pekko.doc.dns$/docs/pekko/current/typed/guide/modules.html) instead 
for a guide on the core modules.
 
 ## [Pekko HTTP]($pekko.doc.dns$/docs/pekko-http/current/)
 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to