topics: some minute fixes to the documentation which shows up in help
authorPulkit Goyal <7895pulkit@gmail.com>
Mon, 19 Jun 2017 02:44:19 +0530
changeset 2625 8f2901f4749e
parent 2624 fd602980f7ee
child 2626 bc36a608e9e4
topics: some minute fixes to the documentation which shows up in help I am not a native but these changes are simple and obvious.
hgext3rd/topic/__init__.py
--- a/hgext3rd/topic/__init__.py	Sun Jun 18 03:23:46 2017 +0530
+++ b/hgext3rd/topic/__init__.py	Mon Jun 19 02:44:19 2017 +0530
@@ -10,7 +10,7 @@
 Compared to bookmark, topic is reference carried by each changesets of the
 series instead of just the single head revision.  Topic are quite similar to
 the way named branch work, except they eventualy fade away when the changeset
-becomes part of the immutable history.  Changeset can below to both a topic and
+becomes part of the immutable history. Changeset can belong to both a topic and
 a named branch, but as long as it is mutable, its topic identity will prevail.
 As a result, default destination for 'update', 'merge', etc...  will take topic
 into account. When a topic is active these operations will only consider other
@@ -21,10 +21,11 @@
 There is currently two commands to be used with that extension: 'topics' and
 'stack'.
 
-The 'hg topics' command is used to set the current topic and list existing one.
-'hg topics --verbose' will list various information related to each topic.
+The 'hg topics' command is used to set the current topic, change and list
+existing one. 'hg topics --verbose' will list various information related to
+each topic.
 
-The 'stack' will show you in formation about the stack of commit belonging to
+The 'stack' will show you information about the stack of commit belonging to
 your current topic.
 
 Topic is offering you aliases reference to changeset in your current topic