Merge branch 'ah/doc-updates' into maint

Doc updates.

* ah/doc-updates:
doc: fix formatting in git-update-ref
doc: fix indentation of listing blocks in gitweb.conf.txt
doc: fix descripion for 'git tag --format'
doc: fix inappropriate monospace formatting
doc: fix ASCII art tab spacing
doc: clarify boundaries of 'git worktree list --porcelain'

diff --combined Documentation/git-update-ref.txt
index fda8516677237e9c0a8343f9ca96a1eb969b3492,86afd24c7f9dc14c5904897946486bba93cc0eb0..96714231179cac8242f1bd0f781503d607c4add3
--- 1/Documentation/git-update-ref.txt
--- 2/Documentation/git-update-ref.txt
+++ b/Documentation/git-update-ref.txt
@@@ -8,7 -8,7 +8,7 @@@ git-update-ref - Update the object nam
  SYNOPSIS
  --------
  [verse]
 -'git update-ref' [-m <reason>] (-d <ref> [<oldvalue>] | [--no-deref] [--create-reflog] <ref> <newvalue> [<oldvalue>] | --stdin [-z])
 +'git update-ref' [-m <reason>] [--no-deref] (-d <ref> [<oldvalue>] | [--create-reflog] <ref> <newvalue> [<oldvalue>] | --stdin [-z])
  
  DESCRIPTION
  -----------
@@@ -129,8 -129,8 +129,8 @@@ a line to the log file "$GIT_DIR/logs/<
  symbolic refs before creating the log name) describing the change
  in ref value.  Log lines are formatted as:
  
-     . oldsha1 SP newsha1 SP committer LF
- +
+     oldsha1 SP newsha1 SP committer LF
+ 
  Where "oldsha1" is the 40 character hexadecimal value previously
  stored in <ref>, "newsha1" is the 40 character hexadecimal value of
  <newvalue> and "committer" is the committer's name, email address
@@@ -138,8 -138,8 +138,8 @@@ and date in the standard Git committer 
  
  Optionally with -m:
  
-     . oldsha1 SP newsha1 SP committer TAB message LF
- +
+     oldsha1 SP newsha1 SP committer TAB message LF
+ 
  Where all fields are as described above and "message" is the
  value supplied to the -m option.
  

diff --combined Documentation/git.txt
index 8e6a92e8ba64b64e663f96f4946f06af36e92759,495b9163eae899ca55eb482c6e910221824bfc52..254f063132037d8472cae07668cc2db2d19da8c9
--- 1/Documentation/git.txt
--- 2/Documentation/git.txt
+++ b/Documentation/git.txt
@@@ -402,11 -402,11 +402,11 @@@ Git so take care if using a foreign fro
        of Git object directories which can be used to search for Git
        objects. New objects will not be written to these directories.
  +
-       Entries that begin with `"` (double-quote) will be interpreted
-       as C-style quoted paths, removing leading and trailing
-       double-quotes and respecting backslash escapes. E.g., the value
-       `"path-with-\"-and-:-in-it":vanilla-path` has two paths:
-       `path-with-"-and-:-in-it` and `vanilla-path`.
+ Entries that begin with `"` (double-quote) will be interpreted
+ as C-style quoted paths, removing leading and trailing
+ double-quotes and respecting backslash escapes. E.g., the value
+ `"path-with-\"-and-:-in-it":vanilla-path` has two paths:
+ `path-with-"-and-:-in-it` and `vanilla-path`.
  
  `GIT_DIR`::
        If the `GIT_DIR` environment variable is set then it
@@@ -599,8 -599,8 +599,8 @@@ trace messages into this file descripto
  +
  Alternatively, if the variable is set to an absolute path
  (starting with a '/' character), Git will interpret this
 -as a file path and will try to write the trace messages
 -into it.
 +as a file path and will try to append the trace messages
 +to it.
  +
  Unsetting the variable, or setting it to empty, "0" or
  "false" (case insensitive) disables trace messages.
@@@ -858,9 -858,7 +858,9 @@@ Reporting Bug
  
  Report bugs to the Git mailing list <git@vger.kernel.org> where the
  development and maintenance is primarily done.  You do not have to be
 -subscribed to the list to send a message there.
 +subscribed to the list to send a message there.  See the list archive
 +at https://public-inbox.org/git for previous bug reports and other
 +discussions.
  
  Issues which are security relevant should be disclosed privately to
  the Git Security mailing list <git-security@googlegroups.com>.