asciidoc: consistently use 1 space after full stop

Note: the command doc strings included in hg (1) are still
      inconsistent wrt to spaces after full stops.

doc/hg.1.txt

@@ -30,7 +30,7 b' revision::'
 
 repository path::
     either the pathname of a local repository or the URI of a remote
-    repository.  There are two available URI protocols, http:// which is
+    repository. There are two available URI protocols, http:// which is
     fast and the static-http:// protocol which is much slower but does not
     require a special server on the web host.
 
@@ -43,7 +43,7 b' SPECIFYING SINGLE REVISIONS'
     Mercurial accepts several notations for identifying individual
     revisions.
 
-    A plain integer is treated as a revision number.  Negative
+    A plain integer is treated as a revision number. Negative
     integers are treated as offsets from the tip, with -1 denoting the
     tip.
 
@@ -52,11 +52,11 b' SPECIFYING SINGLE REVISIONS'
 
     A hexadecimal string less than 40 characters long is treated as a
     unique revision identifier, and referred to as a short-form
-    identifier.  A short-form identifier is only valid if it is the
+    identifier. A short-form identifier is only valid if it is the
     prefix of one full-length identifier.
 
     Any other string is treated as a tag name, which is a symbolic
-    name associated with a revision identifier.  Tag names may not
+    name associated with a revision identifier. Tag names may not
     contain the ":" character.
 
     The reserved name "tip" is a special tag that always identifies
@@ -78,16 +78,16 b' SPECIFYING MULTIPLE REVISIONS'
     separated by the ":" character.
 
     The syntax of range notation is [BEGIN]:[END], where BEGIN and END
-    are revision identifiers.  Both BEGIN and END are optional.  If
-    BEGIN is not specified, it defaults to revision number 0.  If END
-    is not specified, it defaults to the tip.  The range ":" thus
+    are revision identifiers. Both BEGIN and END are optional. If
+    BEGIN is not specified, it defaults to revision number 0. If END
+    is not specified, it defaults to the tip. The range ":" thus
     means "all revisions".
 
     If BEGIN is greater than END, revisions are treated in reverse
     order.
 
-    A range acts as a closed interval.  This means that a range of 3:5
-    gives 3, 4 and 5.  Similarly, a range of 4:2 gives 4, 3, and 2.
+    A range acts as a closed interval. This means that a range of 3:5
+    gives 3, 4 and 5. Similarly, a range of 4:2 gives 4, 3, and 2.
 
 FILES
 -----
@@ -103,7 +103,7 b' FILES'
  /etc/mercurial/hgrc, $HOME/.hgrc, .hg/hgrc::
     This file contains defaults and configuration. Values in .hg/hgrc
     override those in $HOME/.hgrc, and these override settings made in the
-    global /etc/mercurial/hgrc configuration.  See hgrc(5) for details of
+    global /etc/mercurial/hgrc configuration. See hgrc(5) for details of
     the contents and format of these files.
 
 Some commands (e.g. revert) produce backup files ending in .orig, if

doc/hgignore.5.txt

@@ -17,25 +17,25 b' DESCRIPTION'
 -----------
 
 Mercurial ignores every unmanaged file that matches any pattern in an
-ignore file.  The patterns in an ignore file do not apply to files
-managed by Mercurial.  To control Mercurial's handling of files that
-it manages, see the hg(1) man page.  Look for the "-I" and "-X"
+ignore file. The patterns in an ignore file do not apply to files
+managed by Mercurial. To control Mercurial's handling of files that
+it manages, see the hg(1) man page. Look for the "-I" and "-X"
 options.
 
 In addition, a Mercurial configuration file can point to a set of
-per-user or global ignore files.  See the hgrc(5) man page for details
-of how to configure these files.  Look for the "ignore" entry in the
+per-user or global ignore files. See the hgrc(5) man page for details
+of how to configure these files. Look for the "ignore" entry in the
 "ui" section.
 
 SYNTAX
 ------
 
 An ignore file is a plain text file consisting of a list of patterns,
-with one pattern per line.  Empty lines are skipped.  The "#"
+with one pattern per line. Empty lines are skipped. The "#"
 character is treated as a comment character, and the "\" character is
 treated as an escape character.
 
-Mercurial supports several pattern syntaxes.  The default syntax used
+Mercurial supports several pattern syntaxes. The default syntax used
 is Python/Perl-style regular expressions.
 
 To change the syntax used, use a line of the following form:
@@ -52,9 +52,9 b' glob::'
 The chosen syntax stays in effect when parsing all patterns that
 follow, until another syntax is selected.
 
-Neither glob nor regexp patterns are rooted.  A glob-syntax pattern of
+Neither glob nor regexp patterns are rooted. A glob-syntax pattern of
 the form "*.c" will match a file ending in ".c" in any directory, and
-a regexp pattern of the form "\.c$" will do the same.  To root a
+a regexp pattern of the form "\.c$" will do the same. To root a
 regexp pattern, start it with "^".
 
 EXAMPLE

doc/hgrc.5.txt

@@ -17,26 +17,26 b' FILES'
 
 Mercurial reads configuration data from several files, if they exist.
 The names of these files depend on the system on which Mercurial is
-installed.  *.rc files from a single directory are read in
-alphabetical order, later ones overriding earlier ones.  Where
+installed. *.rc files from a single directory are read in
+alphabetical order, later ones overriding earlier ones. Where
 multiple paths are given below, settings from later paths override
 earlier ones.
 
 (Unix) <install-root>/etc/mercurial/hgrc.d/*.rc::
 (Unix) <install-root>/etc/mercurial/hgrc::
     Per-installation configuration files, searched for in the
-    directory where Mercurial is installed.  <install-root> is the
+    directory where Mercurial is installed. <install-root> is the
     parent directory of the hg executable (or symlink) being run.
     For example, if installed in /shared/tools/bin/hg, Mercurial will
-    look in /shared/tools/etc/mercurial/hgrc.  Options in these files
+    look in /shared/tools/etc/mercurial/hgrc. Options in these files
     apply to all Mercurial commands executed by any user in any
     directory.
 
 (Unix) /etc/mercurial/hgrc.d/*.rc::
 (Unix) /etc/mercurial/hgrc::
     Per-system configuration files, for the system on which Mercurial
-    is running.  Options in these files apply to all Mercurial
-    commands executed by any user in any directory.  Options in these
+    is running. Options in these files apply to all Mercurial
+    commands executed by any user in any directory. Options in these
     files override per-installation options.
 
 (Windows) <install-dir>\Mercurial.ini::
@@ -45,7 +45,7 b' earlier ones.'
   or else::
 (Windows) C:\Mercurial\Mercurial.ini::
     Per-installation/system configuration files, for the system on
-    which Mercurial is running.  Options in these files apply to all
+    which Mercurial is running. Options in these files apply to all
     Mercurial commands executed by any user in any directory.
     Registry keys contain PATH-like strings, every part of which must
     reference a Mercurial.ini file or be a directory where *.rc files
@@ -59,16 +59,16 b' earlier ones.'
     Per-user configuration file(s), for the user running Mercurial.
     On Windows 9x, %HOME% is replaced by %APPDATA%.
     Options in these files apply to all Mercurial commands executed
-    by this user in any directory.  Options in thes files override
+    by this user in any directory. Options in thes files override
     per-installation and per-system options.
 
 (Unix, Windows) <repo>/.hg/hgrc::
     Per-repository configuration options that only apply in a
-    particular repository.  This file is not version-controlled, and
-    will not get transferred during a "clone" operation.  Options in
+    particular repository. This file is not version-controlled, and
+    will not get transferred during a "clone" operation. Options in
     this file override options in all other configuration files.
     On Unix, most of this file will be ignored if it doesn't belong
-    to a trusted user or to a trusted group.  See the documentation
+    to a trusted user or to a trusted group. See the documentation
     for the trusted section below for more details.
 
 SYNTAX
@@ -82,10 +82,10 b' and followed by "name: value" entries; "'
     green=
        eggs
 
-Each line contains one entry.  If the lines that follow are indented,
+Each line contains one entry. If the lines that follow are indented,
 they are treated as continuations of that entry.
 
-Leading whitespace is removed from values.  Empty lines are skipped.
+Leading whitespace is removed from values. Empty lines are skipped.
 
 The optional values can contain format strings which refer to other
 values in the same section, or values in a special DEFAULT section.
@@ -107,12 +107,12 b' decode/encode::'
 
   Filters consist of a filter pattern followed by a filter command.
   Filter patterns are globs by default, rooted at the repository
-  root.  For example, to match any file ending in ".txt" in the root
-  directory only, use the pattern "*.txt".  To match any file ending
+  root. For example, to match any file ending in ".txt" in the root
+  directory only, use the pattern "*.txt". To match any file ending
   in ".c" anywhere in the repository, use the pattern "**.c".
 
   The filter command can start with a specifier, either "pipe:" or
-  "tempfile:".  If no specifier is given, "pipe:" is used by default.
+  "tempfile:". If no specifier is given, "pipe:" is used by default.
 
   A "pipe:" command must accept data on stdin and return the
   transformed data on stdout.
@@ -129,9 +129,9 b' decode/encode::'
     # can safely omit "pipe:", because it's the default)
     *.gz = gzip
 
-  A "tempfile:" command is a template.  The string INFILE is replaced
+  A "tempfile:" command is a template. The string INFILE is replaced
   with the name of a temporary file that contains the data to be
-  filtered by the command.  The string OUTFILE is replaced with the
+  filtered by the command. The string OUTFILE is replaced with the
   name of an empty temporary file, where the filtered data must be
   written by the command.
 
@@ -192,22 +192,22 b' diff::'
 email::
   Settings for extensions that send email messages.
   from;;
-    Optional.  Email address to use in "From" header and SMTP envelope
+    Optional. Email address to use in "From" header and SMTP envelope
     of outgoing messages.
   to;;
-    Optional.  Comma-separated list of recipients' email addresses.
+    Optional. Comma-separated list of recipients' email addresses.
   cc;;
-    Optional.  Comma-separated list of carbon copy recipients'
+    Optional. Comma-separated list of carbon copy recipients'
     email addresses.
   bcc;;
-    Optional.  Comma-separated list of blind carbon copy
-    recipients' email addresses.  Cannot be set interactively.
+    Optional. Comma-separated list of blind carbon copy
+    recipients' email addresses. Cannot be set interactively.
   method;;
-    Optional.  Method to use to send email messages.  If value is
+    Optional. Method to use to send email messages. If value is
     "smtp" (default), use SMTP (see section "[smtp]" for
-    configuration).  Otherwise, use as name of program to run that
+    configuration). Otherwise, use as name of program to run that
     acts like sendmail (takes "-f" option for sender, list of
-    recipients on command line, message on stdin).  Normally, setting
+    recipients on command line, message on stdin). Normally, setting
     this to "sendmail" or "/usr/sbin/sendmail" is enough to use
     sendmail to send messages.
 
@@ -298,10 +298,10 b' merge-tools::'
     launching external tool.
     Default: True
   binary;;
-    This tool can merge binary files.  Defaults to False, unless tool
+    This tool can merge binary files. Defaults to False, unless tool
     was selected by file pattern match.
   symlink;;
-    This tool can merge symlinks.  Defaults to False, even if tool was
+    This tool can merge symlinks. Defaults to False, even if tool was
     selected by file pattern match.
   checkconflicts;;
     Check whether there are conflicts even though the tool reported
@@ -319,13 +319,13 b' merge-tools::'
   regkey;;
     Windows registry key which describes install location of this tool.
     Mercurial will search for this key first under HKEY_CURRENT_USER and
-    then under HKEY_LOCAL_MACHINE.  Default: None
+    then under HKEY_LOCAL_MACHINE. Default: None
   regname;;
-    Name of value to read from specified registry key.  Defaults to the
+    Name of value to read from specified registry key. Defaults to the
     unnamed (default) value.
   regappend;;
     String to append to the value read from the registry, typically the
-    executable name of the tool.  Default: None
+    executable name of the tool. Default: None
 
 hooks::
   Commands or Python functions that get automatically executed by
@@ -343,24 +343,24 b' hooks::'
     incoming.autobuild = /my/build/hook
 
   Most hooks are run with environment variables set that give added
-  useful information.  For each hook below, the environment variables
+  useful information. For each hook below, the environment variables
   it is passed are listed with names of the form "$HG_foo".
 
   changegroup;;
     Run after a changegroup has been added via push, pull or
-    unbundle. ID of the first new changeset is in $HG_NODE.  URL from
+    unbundle. ID of the first new changeset is in $HG_NODE. URL from
     which changes came is in $HG_URL.
   commit;;
     Run after a changeset has been created in the local repository.
-    ID of the newly created changeset is in $HG_NODE.  Parent
+    ID of the newly created changeset is in $HG_NODE. Parent
     changeset IDs are in $HG_PARENT1 and $HG_PARENT2.
   incoming;;
     Run after a changeset has been pulled, pushed, or unbundled into
-    the local repository.  The ID of the newly arrived changeset is in
-    $HG_NODE.  URL that was source of changes came is in $HG_URL.
+    the local repository. The ID of the newly arrived changeset is in
+    $HG_NODE. URL that was source of changes came is in $HG_URL.
   outgoing;;
-    Run after sending changes from local repository to another.  ID of
-    first changeset sent is in $HG_NODE.  Source of operation is in
+    Run after sending changes from local repository to another. ID of
+    first changeset sent is in $HG_NODE. Source of operation is in
     $HG_SOURCE; see "preoutgoing" hook for description.
   post-<command>;;
     Run after successful invocations of the associated command. The
@@ -372,56 +372,56 b' hooks::'
     the command doesn't execute and Mercurial returns the failure code.
   prechangegroup;;
     Run before a changegroup is added via push, pull or unbundle.
-    Exit status 0 allows the changegroup to proceed.  Non-zero status
-    will cause the push, pull or unbundle to fail.  URL from which
+    Exit status 0 allows the changegroup to proceed. Non-zero status
+    will cause the push, pull or unbundle to fail. URL from which
     changes will come is in $HG_URL.
   precommit;;
-    Run before starting a local commit.  Exit status 0 allows the
-    commit to proceed.  Non-zero status will cause the commit to fail.
+    Run before starting a local commit. Exit status 0 allows the
+    commit to proceed. Non-zero status will cause the commit to fail.
     Parent changeset IDs are in $HG_PARENT1 and $HG_PARENT2.
   preoutgoing;;
     Run before collecting changes to send from the local repository to
-    another.  Non-zero status will cause failure.  This lets you
-    prevent pull over http or ssh.  Also prevents against local pull,
+    another. Non-zero status will cause failure. This lets you
+    prevent pull over http or ssh. Also prevents against local pull,
     push (outbound) or bundle commands, but not effective, since you
-    can just copy files instead then.  Source of operation is in
-    $HG_SOURCE.  If "serve", operation is happening on behalf of
-    remote ssh or http repository.  If "push", "pull" or "bundle",
+    can just copy files instead then. Source of operation is in
+    $HG_SOURCE. If "serve", operation is happening on behalf of
+    remote ssh or http repository. If "push", "pull" or "bundle",
     operation is happening on behalf of repository on same system.
   pretag;;
-    Run before creating a tag.  Exit status 0 allows the tag to be
-    created.  Non-zero status will cause the tag to fail.  ID of
-    changeset to tag is in $HG_NODE.  Name of tag is in $HG_TAG.  Tag
+    Run before creating a tag. Exit status 0 allows the tag to be
+    created. Non-zero status will cause the tag to fail. ID of
+    changeset to tag is in $HG_NODE. Name of tag is in $HG_TAG. Tag
     is local if $HG_LOCAL=1, in repo if $HG_LOCAL=0.
   pretxnchangegroup;;
     Run after a changegroup has been added via push, pull or unbundle,
-    but before the transaction has been committed.  Changegroup is
-    visible to hook program.  This lets you validate incoming changes
-    before accepting them.  Passed the ID of the first new changeset
-    in $HG_NODE.  Exit status 0 allows the transaction to commit.
+    but before the transaction has been committed. Changegroup is
+    visible to hook program. This lets you validate incoming changes
+    before accepting them. Passed the ID of the first new changeset
+    in $HG_NODE. Exit status 0 allows the transaction to commit.
     Non-zero status will cause the transaction to be rolled back and
-    the push, pull or unbundle will fail.  URL that was source of
+    the push, pull or unbundle will fail. URL that was source of
     changes is in $HG_URL.
   pretxncommit;;
     Run after a changeset has been created but the transaction not yet
-    committed.  Changeset is visible to hook program.  This lets you
-    validate commit message and changes.  Exit status 0 allows the
-    commit to proceed.  Non-zero status will cause the transaction to
-    be rolled back.  ID of changeset is in $HG_NODE.  Parent changeset
+    committed. Changeset is visible to hook program. This lets you
+    validate commit message and changes. Exit status 0 allows the
+    commit to proceed. Non-zero status will cause the transaction to
+    be rolled back. ID of changeset is in $HG_NODE. Parent changeset
     IDs are in $HG_PARENT1 and $HG_PARENT2.
   preupdate;;
-    Run before updating the working directory.  Exit status 0 allows
-    the update to proceed.  Non-zero status will prevent the update.
-    Changeset ID of first new parent is in $HG_PARENT1.  If merge, ID
+    Run before updating the working directory. Exit status 0 allows
+    the update to proceed. Non-zero status will prevent the update.
+    Changeset ID of first new parent is in $HG_PARENT1. If merge, ID
     of second new parent is in $HG_PARENT2.
   tag;;
-    Run after a tag is created.  ID of tagged changeset is in
-    $HG_NODE.  Name of tag is in $HG_TAG.  Tag is local if
+    Run after a tag is created. ID of tagged changeset is in
+    $HG_NODE. Name of tag is in $HG_TAG. Tag is local if
     $HG_LOCAL=1, in repo if $HG_LOCAL=0.
   update;;
-    Run after updating the working directory.  Changeset ID of first
-    new parent is in $HG_PARENT1.  If merge, ID of second new parent
-    is in $HG_PARENT2.  If update succeeded, $HG_ERROR=0.  If update
+    Run after updating the working directory. Changeset ID of first
+    new parent is in $HG_PARENT1. If merge, ID of second new parent
+    is in $HG_PARENT2. If update succeeded, $HG_ERROR=0. If update
     failed (e.g. because conflicts not resolved), $HG_ERROR=1.
 
   Note: it is generally better to use standard hooks rather than the
@@ -439,10 +439,10 b' hooks::'
 
     hookname = python:modulename.submodule.callable
 
-  Python hooks are run within the Mercurial process.  Each hook is
+  Python hooks are run within the Mercurial process. Each hook is
   called with at least three keyword arguments: a ui object (keyword
   "ui"), a repository object (keyword "repo"), and a "hooktype"
-  keyword that tells what kind of hook is used.  Arguments listed as
+  keyword that tells what kind of hook is used. Arguments listed as
   environment variables above are passed as keyword arguments, with no
   "HG_" prefix, and names in lower case.
 
@@ -456,68 +456,68 b' http_proxy::'
     Host name and (optional) port of the proxy server, for example
     "myproxy:8000".
   no;;
-    Optional.  Comma-separated list of host names that should bypass
+    Optional. Comma-separated list of host names that should bypass
     the proxy.
   passwd;;
-    Optional.  Password to authenticate with at the proxy server.
+    Optional. Password to authenticate with at the proxy server.
   user;;
-    Optional.  User name to authenticate with at the proxy server.
+    Optional. User name to authenticate with at the proxy server.
 
 smtp::
   Configuration for extensions that need to send email messages.
   host;;
     Host name of mail server, e.g. "mail.example.com".
   port;;
-    Optional.  Port to connect to on mail server.  Default: 25.
+    Optional. Port to connect to on mail server. Default: 25.
   tls;;
-    Optional.  Whether to connect to mail server using TLS.  True or
-    False.  Default: False.
+    Optional. Whether to connect to mail server using TLS. True or
+    False. Default: False.
   username;;
-    Optional.  User name to authenticate to SMTP server with.
+    Optional. User name to authenticate to SMTP server with.
     If username is specified, password must also be specified.
     Default: none.
   password;;
-    Optional.  Password to authenticate to SMTP server with.
+    Optional. Password to authenticate to SMTP server with.
     If username is specified, password must also be specified.
     Default: none.
   local_hostname;;
-    Optional.  It's the hostname that the sender can use to identify itself
+    Optional. It's the hostname that the sender can use to identify itself
     to the MTA.
 
 paths::
-  Assigns symbolic names to repositories.  The left side is the
+  Assigns symbolic names to repositories. The left side is the
   symbolic name, and the right gives the directory or URL that is the
-  location of the repository.  Default paths can be declared by
+  location of the repository. Default paths can be declared by
   setting the following entries.
   default;;
     Directory or URL to use when pulling if no source is specified.
     Default is set to repository from which the current repository
     was cloned.
   default-push;;
-    Optional.  Directory or URL to use when pushing if no destination
+    Optional. Directory or URL to use when pushing if no destination
     is specified.
 
 server::
   Controls generic server settings.
   uncompressed;;
     Whether to allow clients to clone a repo using the uncompressed
-    streaming protocol.  This transfers about 40% more data than a
+    streaming protocol. This transfers about 40% more data than a
     regular clone, but uses less memory and CPU on both server and
-    client.  Over a LAN (100Mbps or better) or a very fast WAN, an
+    client. Over a LAN (100Mbps or better) or a very fast WAN, an
     uncompressed streaming clone is a lot faster (~10x) than a regular
-    clone.  Over most WAN connections (anything slower than about
+    clone. Over most WAN connections (anything slower than about
     6Mbps), uncompressed streaming is slower, because of the extra
-    data transfer overhead.  Default is False.
+    data transfer overhead. Default is False.
 
 trusted::
   For security reasons, Mercurial will not use the settings in
   the .hg/hgrc file from a repository if it doesn't belong to a
-  trusted user or to a trusted group.  The main exception is the
+  trusted user or to a trusted group. The main exception is the
   web interface, which automatically uses some safe settings, since
   it's common to serve repositories from different users.
 
-  This section specifies what users and groups are trusted.  The
-  current user is always trusted.  To trust everybody, list a user
+  This section specifies what users and groups are trusted. The
+  current user is always trusted. To trust everybody, list a user
   or a group with name "*".
 
   users;;
@@ -533,12 +533,12 b' ui::'
     the hg archive command or downloaded via hgweb.
     Default is true.
   debug;;
-    Print debugging information.  True or False.  Default is False.
+    Print debugging information. True or False. Default is False.
   editor;;
-    The editor to use during a commit.  Default is $EDITOR or "vi".
+    The editor to use during a commit. Default is $EDITOR or "vi".
   fallbackencoding;;
     Encoding to try if it's not possible to decode the changelog using
-    UTF-8.  Default is ISO-8859-1.
+    UTF-8. Default is ISO-8859-1.
   ignore;;
     A file to read per-user ignore patterns from. This file should be in
     the same format as a repository-wide .hgignore file. This option
@@ -547,7 +547,7 b' ui::'
     "ignore.other = ~/.hgignore2". For details of the ignore file
     format, see the hgignore(5) man page.
   interactive;;
-    Allow to prompt the user.  True or False.  Default is True.
+    Allow to prompt the user. True or False. Default is True.
   logtemplate;;
     Template string for commands that print changesets.
   merge;;
@@ -569,14 +569,14 b' ui::'
     command to use to apply patches. Look for 'gpatch' or 'patch' in PATH if
     unset.
   quiet;;
-    Reduce the amount of output printed.  True or False.  Default is False.
+    Reduce the amount of output printed. True or False. Default is False.
   remotecmd;;
     remote command to use for clone/push/pull operations. Default is 'hg'.
   report_untrusted;;
     Warn if a .hg/hgrc file is ignored due to not being owned by a
-    trusted user or group.  True or False.  Default is True.
+    trusted user or group. True or False. Default is True.
   slash;;
-    Display paths using a slash ("/") as the path separator.  This only
+    Display paths using a slash ("/") as the path separator. This only
     makes a difference on systems where the default path separator is not
     the slash character (e.g. Windows uses the backslash character ("\")).
     Default is False.
@@ -584,7 +584,7 b' ui::'
     command to use for SSH connections. Default is 'ssh'.
   strict;;
     Require exact command names, instead of allowing unambiguous
-    abbreviations.  True or False.  Default is False.
+    abbreviations. True or False. Default is False.
   style;;
     Name of style to use for command output.
   timeout;;
@@ -593,12 +593,12 b' ui::'
   username;;
     The committer of a changeset created when running "commit".
     Typically a person's name and email address, e.g. "Fred Widget
-    <[e-mail]>".  Default is $EMAIL or username@hostname.
+    <[e-mail]>". Default is $EMAIL or username@hostname.
     If the username in hgrc is empty, it has to be specified manually or
     in a different hgrc file (e.g. $HOME/.hgrc, if the admin set "username ="
     in the system hgrc).
   verbose;;
-    Increase the amount of output printed.  True or False.  Default is False.
+    Increase the amount of output printed. True or False. Default is False.
 
 
 web::
@@ -619,9 +619,9 b' web::'
   allowpull;;
     Whether to allow pulling from the repository. Default is true.
   allow_push;;
-    Whether to allow pushing to the repository.  If empty or not set,
-    push is not allowed.  If the special value "*", any remote user
-    can push, including unauthenticated users.  Otherwise, the remote
+    Whether to allow pushing to the repository. If empty or not set,
+    push is not allowed. If the special value "*", any remote user
+    can push, including unauthenticated users. Otherwise, the remote
     user must have been authenticated, and the authenticated user name
     must be present in this list (separated by whitespace or ",").
     The contents of the allow_push list are examined after the
@@ -637,11 +637,11 b' web::'
     Name or email address of the person in charge of the repository.
     Defaults to ui.username or $EMAIL or "unknown" if unset or empty.
   deny_push;;
-    Whether to deny pushing to the repository.  If empty or not set,
-    push is not denied.  If the special value "*", all remote users
-    are denied push.  Otherwise, unauthenticated users are all denied,
+    Whether to deny pushing to the repository. If empty or not set,
+    push is not denied. If the special value "*", all remote users
+    are denied push. Otherwise, unauthenticated users are all denied,
     and any authenticated user name present in this list (separated by
-    whitespace or ",") is also denied.  The contents of the deny_push
+    whitespace or ",") is also denied. The contents of the deny_push
     list are examined before the allow_push list.
   description;;
     Textual description of the repository's purpose or contents.
@@ -668,7 +668,7 b' web::'
     Prefix path to serve from. Default is '' (server root).
   push_ssl;;
     Whether to require that inbound pushes be transported over SSL to
-    prevent password sniffing.  Default is true.
+    prevent password sniffing. Default is true.
   staticurl;;
     Base URL to use for static files. If unset, static files (e.g.
     the hgicon.png favicon) will be served by the CGI script itself.