help: fix typos

mercurial/help/bundlespec.txt

@@ -1,84 +1,84
 Mercurial supports generating standalone "bundle" files that hold repository
 data. These "bundles" are typically saved locally and used later or exchanged
 between different repositories, possibly on different machines. Example
 commands using bundles are :hg:`bundle` and :hg:`unbundle`.
 
 Generation of bundle files is controlled by a "bundle specification"
 ("bundlespec") string. This string tells the bundle generation process how
 to create the bundle.
 
 A "bundlespec" string is composed of the following elements:
 
 type
     A string denoting the bundle format to use.
 
 compression
     Denotes the compression engine to use compressing the raw bundle data.
 
 parameters
     Arbitrary key-value parameters to further control bundle generation.
 
 A "bundlespec" string has the following formats:
 
 <type>
     The literal bundle format string is used.
 
 <compression>-<type>
     The compression engine and format are delimited by a hyphen (``-``).
 
 Optional parameters follow the ``<type>``. Parameters are URI escaped
 ``key=value`` pairs. Each pair is delimited by a semicolon (``;``). The
 first parameter begins after a ``;`` immediately following the ``<type>``
 value.
 
 Available Types
 ===============
 
 The following bundle <type> strings are available:
 
 v1
     Produces a legacy "changegroup" version 1 bundle.
 
     This format is compatible with nearly all Mercurial clients because it is
     the oldest. However, it has some limitations, which is why it is no longer
     the default for new repositories.
 
     ``v1`` bundles can be used with modern repositories using the "generaldelta"
     storage format. However, it may take longer to produce the bundle and the
     resulting bundle may be significantly larger than a ``v2`` bundle.
 
     ``v1`` bundles can only use the ``gzip``, ``bzip2``, and ``none`` compression
     formats.
 
 v2
     Produces a version 2 bundle.
 
     Version 2 bundles are an extensible format that can store additional
     repository data (such as bookmarks and phases information) and they can
     store data more efficiently, resulting in smaller bundles.
 
     Version 2 bundles can also use modern compression engines, such as
     ``zstd``, making them faster to compress and often smaller.
 
 Available Compression Engines
 =============================
 
 The following bundle <compression> engines can be used:
 
 .. bundlecompressionmarker
 
 Examples
 ========
 
 ``v2``
     Produce a ``v2`` bundle using default options, including compression.
 
 ``none-v1``
-    Produce a ``v2`` bundle with no compression.
+    Produce a ``v1`` bundle with no compression.
 
 ``zstd-v2``
     Produce a ``v2`` bundle with zstandard compression using default
     settings.
 
 ``zstd-v1``
     This errors because ``zstd`` is not supported for ``v1`` types.

mercurial/help/color.txt

@@ -1,148 +1,148
 Mercurial colorizes output from several commands.
 
 For example, the diff command shows additions in green and deletions
 in red, while the status command shows modified files in magenta. Many
 other commands have analogous colors. It is possible to customize
 these colors.
 
 To enable color (default) whenever possible use::
 
   [ui]
   color = yes
 
 To disable color use::
 
   [ui]
   color = no
 
 See :hg:`help config.ui.color` for details.
 
 .. container:: windows
 
   The default pager on Windows does not support color, so enabling the pager
   will effectively disable color.  See :hg:`help config.ui.paginate` to disable
   the pager.  Alternately, MSYS and Cygwin shells provide `less` as a pager,
   which can be configured to support ANSI color mode.
 
 Mode
 ====
 
-Mercurial can use various system to display color. The supported modes are
+Mercurial can use various systems to display color. The supported modes are
 ``ansi``, ``win32``, and ``terminfo``.  See :hg:`help config.color` for details
-about how to control the mode
+about how to control the mode.
 
 Effects
 =======
 
 Other effects in addition to color, like bold and underlined text, are
 also available. By default, the terminfo database is used to find the
 terminal codes used to change color and effect.  If terminfo is not
 available, then effects are rendered with the ECMA-48 SGR control
 function (aka ANSI escape codes).
 
 The available effects in terminfo mode are 'blink', 'bold', 'dim',
 'inverse', 'invisible', 'italic', 'standout', and 'underline'; in
 ECMA-48 mode, the options are 'bold', 'inverse', 'italic', and
 'underline'.  How each is rendered depends on the terminal emulator.
 Some may not be available for a given terminal type, and will be
 silently ignored.
 
 If the terminfo entry for your terminal is missing codes for an effect
 or has the wrong codes, you can add or override those codes in your
 configuration::
 
   [color]
   terminfo.dim = \E[2m
 
 where '\E' is substituted with an escape character.
 
 Labels
 ======
 
 Text receives color effects depending on the labels that it has. Many
 default Mercurial commands emit labelled text. You can also define
 your own labels in templates using the label function, see :hg:`help
 templates`. A single portion of text may have more than one label. In
 that case, effects given to the last label will override any other
 effects. This includes the special "none" effect, which nullifies
 other effects.
 
 Labels are normally invisible. In order to see these labels and their
 position in the text, use the global --color=debug option. The same
 anchor text may be associated to multiple labels, e.g.
 
   [log.changeset changeset.secret|changeset:   22611:6f0a53c8f587]
 
 The following are the default effects for some default labels. Default
 effects may be overridden from your configuration file::
 
   [color]
   status.modified = blue bold underline red_background
   status.added = green bold
   status.removed = red bold blue_background
   status.deleted = cyan bold underline
   status.unknown = magenta bold underline
   status.ignored = black bold
 
   # 'none' turns off all effects
   status.clean = none
   status.copied = none
 
   qseries.applied = blue bold underline
   qseries.unapplied = black bold
   qseries.missing = red bold
 
   diff.diffline = bold
   diff.extended = cyan bold
   diff.file_a = red bold
   diff.file_b = green bold
   diff.hunk = magenta
   diff.deleted = red
   diff.inserted = green
   diff.changed = white
   diff.tab =
   diff.trailingwhitespace = bold red_background
 
   # Blank so it inherits the style of the surrounding label
   changeset.public =
   changeset.draft =
   changeset.secret =
 
   resolve.unresolved = red bold
   resolve.resolved = green bold
 
   bookmarks.active = green
 
   branches.active = none
   branches.closed = black bold
   branches.current = green
   branches.inactive = none
 
   tags.normal = green
   tags.local = black bold
 
   rebase.rebased = blue
   rebase.remaining = red bold
 
   shelve.age = cyan
   shelve.newest = green bold
   shelve.name = blue bold
 
   histedit.remaining = red bold
 
 Custom colors
 =============
 
 Because there are only eight standard colors, Mercurial allows you
 to define color names for other color slots which might be available
 for your terminal type, assuming terminfo mode.  For instance::
 
   color.brightblue = 12
   color.pink = 207
   color.orange = 202
 
 to set 'brightblue' to color slot 12 (useful for 16 color terminals
 that have brighter colors defined in the upper eight) and, 'pink' and
 'orange' to colors in 256-color xterm's default color cube.  These
 defined colors may then be used as any of the pre-defined eight,
 including appending '_background' to set the background to that color.