# HG changeset patch
# User Anton Shestakov <av6@dwimlabs.net>
# Date 1704571681 10800
# Node ID 196babdbb593a1400c822b4d06c5260aa0c0abfb
# Parent  995c6163e97b100acae4821c4015c6ecd6890880
topic: we no longer add --publish to push command, it's just there

Also copywrite the rest of the section.

diff -r 995c6163e97b -r 196babdbb593 hgext3rd/topic/__init__.py
--- a/hgext3rd/topic/__init__.py	Mon Nov 06 00:58:11 2023 -0300
+++ b/hgext3rd/topic/__init__.py	Sat Jan 06 17:08:01 2024 -0300
@@ -80,32 +80,32 @@
 Publishing behavior
 ===================
 
-Topic vanish when changeset move to the public phases. Moving to the public
-phase usually happens on push, but it is possible to update that behavior. The
+Topics vanish when changesets move to the public phase. Moving to the public
+phase usually happens on push, but it is possible to modify this behavior. The
 server needs to have specific config for this.
 
-* everything pushed become public (the default)::
+* everything pushed becomes public (the default)::
 
     [phases]
     publish = yes
 
-* nothing push turned public::
+* nothing pushed turns public::
 
     [phases]
     publish = no
 
-* topic branches are not published, changeset without topic are::
+* topic branches are not published, changesets without topic are::
 
     [phases]
     publish = no
     [experimental]
     topic.publish-bare-branch = yes
 
-In addition, the topic extension adds a ``--publish`` flag on :hg:`push`. When
-used, the pushed revisions are published if the push succeeds. It also applies
-to common revisions selected by the push.
+In addition, :hg:`push` command has a ``--publish`` flag. When used, the pushed
+revisions are published if the push succeeds. It also applies to common
+revisions selected by the push.
 
-One can prevent any publishing to happens in a repository using::
+One can prevent any publishing from happening in a repository using::
 
     [experimental]
     topic.allow-publish = no
diff -r 995c6163e97b -r 196babdbb593 tests/test-topic.t
--- a/tests/test-topic.t	Mon Nov 06 00:58:11 2023 -0300
+++ b/tests/test-topic.t	Sat Jan 06 17:08:01 2024 -0300
@@ -85,32 +85,32 @@
   Publishing behavior
   ===================
   
-  Topic vanish when changeset move to the public phases. Moving to the public
-  phase usually happens on push, but it is possible to update that behavior. The
+  Topics vanish when changesets move to the public phase. Moving to the public
+  phase usually happens on push, but it is possible to modify this behavior. The
   server needs to have specific config for this.
   
-  * everything pushed become public (the default):
+  * everything pushed becomes public (the default):
   
       [phases]
       publish = yes
   
-  * nothing push turned public:
+  * nothing pushed turns public:
   
       [phases]
       publish = no
   
-  * topic branches are not published, changeset without topic are:
+  * topic branches are not published, changesets without topic are:
   
       [phases]
       publish = no
       [experimental]
       topic.publish-bare-branch = yes
   
-  In addition, the topic extension adds a "--publish" flag on 'hg push'. When
-  used, the pushed revisions are published if the push succeeds. It also applies
-  to common revisions selected by the push.
+  In addition, 'hg push' command has a "--publish" flag. When used, the pushed
+  revisions are published if the push succeeds. It also applies to common
+  revisions selected by the push.
   
-  One can prevent any publishing to happens in a repository using:
+  One can prevent any publishing from happening in a repository using:
   
     [experimental]
     topic.allow-publish = no