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

He-Pin 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 364d7c6e70 docs: fix remoting incompatible change sentence (#2959)
364d7c6e70 is described below

commit 364d7c6e70bd82522fbddba8c0fa0fc9707f3406
Author: He-Pin(kerr) <[email protected]>
AuthorDate: Sun May 10 01:37:22 2026 +0800

    docs: fix remoting incompatible change sentence (#2959)
    
    Motivation:
    
    The remoting documentation sentence describing the main incompatible 
protocol-field change was missing its predicate.
    
    Modification:
    
    Add the missing predicate while preserving the Pekko-specific protocol 
names.
    
    Result:
    
    The sentence now reads correctly.
    
    Tests:
    
    - git diff --check / passed
    
    References:
    
    Refs upstream 
https://github.com/akka/akka-core/commit/02831db725f94eb76c8948483ae4e6b497324358,
 which is now Apache licensed.
---
 docs/src/main/paradox/remoting-artery.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/src/main/paradox/remoting-artery.md 
b/docs/src/main/paradox/remoting-artery.md
index bfb979151e..2109369a0c 100644
--- a/docs/src/main/paradox/remoting-artery.md
+++ b/docs/src/main/paradox/remoting-artery.md
@@ -469,7 +469,7 @@ in case of heavy traffic by using a dedicated subchannel.
 specific events
  * Providing protocol stability across major Pekko versions to support rolling 
updates of large-scale systems
 
-The main incompatible change from the previous implementation that the 
protocol field of the string representation of an
+The main incompatible change from the previous implementation is that the 
protocol field of the string representation of an
 @apidoc[actor.ActorRef] is always *pekko* instead of the previously used 
*pekko.tcp* or *pekko.ssl.tcp*. Configuration properties
 are also different.
 


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

Reply via email to