{"thread":{"id":"65053","subject":"[PATCH] doc: format config values with backticks","startedAt":"2026-02-23T10:55:33Z","lastAt":"2026-02-23T11:23:55Z","messageCount":2,"participants":["Md Ferdous Alam via GitGitGadget"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"536741","messageId":"pull.2055.git.1771844130973.gitgitgadget@gmail.com","threadId":"65053","inReplyTo":null,"subject":"[PATCH] doc: format config values with backticks","fromName":"Md Ferdous Alam via GitGitGadget","fromEmail":"gitgitgadget@gmail.com","sentAt":"2026-02-23T10:55:30Z","receivedAt":"2026-02-23T10:55:33Z","isPatch":true,"sender":{"key":"name:Md Ferdous Alam","avatar":null},"body":"From: mdferdousalam <mdferdousalam1989@yahoo.com>\n\nAdd backtick formatting to bare true/false values in configuration\ndocumentation so they render in monospace as config literals, matching\nthe style used throughout most of the existing documentation.\n\nSigned-off-by: Md Ferdous Alam <mdferdousalam@gmail.com>\n---\n    doc: format config values with backticks\n    \n    Add backtick formatting to bare true/false values in configuration\n    documentation so they render in monospace as config literals, matching\n    the style used throughout most of the existing documentation.\n    \n    Files updated:\n    \n     * am.adoc, blame.adoc, clean.adoc, commitgraph.adoc\n     * credential.adoc, fmt-merge-msg.adoc, format.adoc\n     * grep.adoc, rebase.adoc, rerere.adoc, stash.adoc, status.adoc\n    \n    This addresses https://github.com/gitgitgadget/git/issues/244\n\nPublished-As: https://github.com/gitgitgadget/git/releases/tag/pr-2055%2Fmdferdousalam%2Ffix-config-doc-formatting-v1\nFetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-2055/mdferdousalam/fix-config-doc-formatting-v1\nPull-Request: https://github.com/gitgitgadget/git/pull/2055\n\n Documentation/config/am.adoc            |  4 ++--\n Documentation/config/blame.adoc         |  2 +-\n Documentation/config/clean.adoc         |  2 +-\n Documentation/config/commitgraph.adoc   |  8 ++++----\n Documentation/config/credential.adoc    |  2 +-\n Documentation/config/fmt-merge-msg.adoc |  6 +++---\n Documentation/config/format.adoc        | 22 +++++++++++-----------\n Documentation/config/grep.adoc          | 12 ++++++------\n Documentation/config/rebase.adoc        | 18 +++++++++---------\n Documentation/config/rerere.adoc        |  4 ++--\n Documentation/config/stash.adoc         | 16 ++++++++--------\n Documentation/config/status.adoc        | 20 ++++++++++----------\n 12 files changed, 58 insertions(+), 58 deletions(-)\n\ndiff --git a/Documentation/config/am.adoc b/Documentation/config/am.adoc\nindex 5bcad2efb1..d072613400 100644\n--- a/Documentation/config/am.adoc\n+++ b/Documentation/config/am.adoc\n@@ -1,5 +1,5 @@\n am.keepcr::\n-\tIf true, git-am will call git-mailsplit for patches in mbox format\n+\tIf `true`, git-am will call git-mailsplit for patches in mbox format\n \twith parameter `--keep-cr`. In this case git-mailsplit will\n \tnot remove `\\r` from lines ending with `\\r\\n`. Can be overridden\n \tby giving `--no-keep-cr` from the command line.\n@@ -7,7 +7,7 @@ am.keepcr::\n \n am.threeWay::\n \tBy default, `git am` will fail if the patch does not apply cleanly. When\n-\tset to true, this setting tells `git am` to fall back on 3-way merge if\n+\tset to `true`, this setting tells `git am` to fall back on 3-way merge if\n \tthe patch records the identity of blobs it is supposed to apply to and\n \twe have those blobs available locally (equivalent to giving the `--3way`\n \toption from the command line). Defaults to `false`.\ndiff --git a/Documentation/config/blame.adoc b/Documentation/config/blame.adoc\nindex 4d047c1790..3ca7ea6ccd 100644\n--- a/Documentation/config/blame.adoc\n+++ b/Documentation/config/blame.adoc\n@@ -1,6 +1,6 @@\n blame.blankBoundary::\n \tShow blank commit object name for boundary commits in\n-\tlinkgit:git-blame[1]. This option defaults to false.\n+\tlinkgit:git-blame[1]. This option defaults to `false`.\n \n blame.coloring::\n \tThis determines the coloring scheme to be applied to blame\ndiff --git a/Documentation/config/clean.adoc b/Documentation/config/clean.adoc\nindex c0188ead4e..095945d508 100644\n--- a/Documentation/config/clean.adoc\n+++ b/Documentation/config/clean.adoc\n@@ -1,3 +1,3 @@\n clean.requireForce::\n \tA boolean to make git-clean refuse to delete files unless -f\n-\tis given. Defaults to true.\n+\tis given. Defaults to `true`.\ndiff --git a/Documentation/config/commitgraph.adoc b/Documentation/config/commitgraph.adoc\nindex 70a56c53d2..1c33e08141 100644\n--- a/Documentation/config/commitgraph.adoc\n+++ b/Documentation/config/commitgraph.adoc\n@@ -9,9 +9,9 @@ commitGraph.maxNewFilters::\n \tcommit-graph write` (c.f., linkgit:git-commit-graph[1]).\n \n commitGraph.changedPaths::\n-\tIf true, then `git commit-graph write` will compute and write\n+\tIf `true`, then `git commit-graph write` will compute and write\n \tchanged-path Bloom filters by default, equivalent to passing\n-\t`--changed-paths`. If false or unset, changed-paths Bloom filters will\n+\t`--changed-paths`. If `false` or unset, changed-paths Bloom filters will\n \tbe written during `git commit-graph write` only if the filters already\n \texist in the current commit-graph file. This matches the default\n \tbehavior of `git commit-graph write` without any `--[no-]changed-paths`\n@@ -20,8 +20,8 @@ commitGraph.changedPaths::\n \talways takes precedence over this configuration. Defaults to unset.\n \n commitGraph.readChangedPaths::\n-\tDeprecated. Equivalent to commitGraph.changedPathsVersion=-1 if true, and\n-\tcommitGraph.changedPathsVersion=0 if false. (If commitGraph.changedPathVersion\n+\tDeprecated. Equivalent to commitGraph.changedPathsVersion=-1 if `true`, and\n+\tcommitGraph.changedPathsVersion=0 if `false`. (If commitGraph.changedPathVersion\n \tis also set, commitGraph.changedPathsVersion takes precedence.)\n \n commitGraph.changedPathsVersion::\ndiff --git a/Documentation/config/credential.adoc b/Documentation/config/credential.adoc\nindex 80a7c77772..0e88c4c7f2 100644\n--- a/Documentation/config/credential.adoc\n+++ b/Documentation/config/credential.adoc\n@@ -19,7 +19,7 @@ credential.interactive::\n \n credential.useHttpPath::\n \tWhen acquiring credentials, consider the \"path\" component of an http\n-\tor https URL to be important. Defaults to false. See\n+\tor https URL to be important. Defaults to `false`. See\n \tlinkgit:gitcredentials[7] for more information.\n \n credential.sanitizePrompt::\ndiff --git a/Documentation/config/fmt-merge-msg.adoc b/Documentation/config/fmt-merge-msg.adoc\nindex 696ba0531a..4bcf5b2688 100644\n--- a/Documentation/config/fmt-merge-msg.adoc\n+++ b/Documentation/config/fmt-merge-msg.adoc\n@@ -1,13 +1,13 @@\n `merge.branchdesc`::\n \tIn addition to branch names, populate the log message with\n \tthe branch description text associated with them.  Defaults\n-\tto false.\n+\tto `false`.\n \n `merge.log`::\n \tIn addition to branch names, populate the log message with at\n \tmost the specified number of one-line descriptions from the\n-\tactual commits that are being merged.  Defaults to false, and\n-\ttrue is a synonym for 20.\n+\tactual commits that are being merged.  Defaults to `false`, and\n+\t`true` is a synonym for 20.\n \n `merge.suppressDest`::\n \tBy adding a glob that matches the names of integration\ndiff --git a/Documentation/config/format.adoc b/Documentation/config/format.adoc\nindex ab0710e86a..a9736b196a 100644\n--- a/Documentation/config/format.adoc\n+++ b/Documentation/config/format.adoc\n@@ -8,23 +8,23 @@ format.attach::\n \n format.from::\n \tProvides the default value for the `--from` option to format-patch.\n-\tAccepts a boolean value, or a name and email address.  If false,\n+\tAccepts a boolean value, or a name and email address.  If `false`,\n \tformat-patch defaults to `--no-from`, using commit authors directly in\n-\tthe \"From:\" field of patch mails.  If true, format-patch defaults to\n+\tthe \"From:\" field of patch mails.  If `true`, format-patch defaults to\n \t`--from`, using your committer identity in the \"From:\" field of patch\n \tmails and including a \"From:\" field in the body of the patch mail if\n \tdifferent.  If set to a non-boolean value, format-patch uses that\n-\tvalue instead of your committer identity.  Defaults to false.\n+\tvalue instead of your committer identity.  Defaults to `false`.\n \n format.forceInBodyFrom::\n \tProvides the default value for the `--[no-]force-in-body-from`\n-\toption to format-patch.  Defaults to false.\n+\toption to format-patch.  Defaults to `false`.\n \n format.numbered::\n \tA boolean which can enable or disable sequence numbers in patch\n \tsubjects.  It defaults to \"auto\" which enables it only if there\n \tis more than one patch.  It can be enabled or disabled for all\n-\tmessages by setting it to \"true\" or \"false\".  See --numbered\n+\tmessages by setting it to `true` or `false`.  See --numbered\n \toption in linkgit:git-format-patch[1].\n \n format.headers::\n@@ -65,7 +65,7 @@ format.suffix::\n format.encodeEmailHeaders::\n \tEncode email headers that have non-ASCII characters with\n \t\"Q-encoding\" (described in RFC 2047) for email transmission.\n-\tDefaults to true.\n+\tDefaults to `true`.\n \n format.pretty::\n ifndef::with-breaking-changes[]\n@@ -85,7 +85,7 @@ format.thread::\n \twhere the head is chosen from the cover letter, the\n \t`--in-reply-to`, and the first patch mail, in this order.\n \t`deep` threading makes every mail a reply to the previous one.\n-\tA true boolean value is the same as `shallow`, and a false\n+\tA `true` boolean value is the same as `shallow`, and a `false`\n \tvalue disables threading.\n \n format.signOff::\n@@ -99,7 +99,7 @@ format.coverLetter::\n \tA boolean that controls whether to generate a cover-letter when\n \tformat-patch is invoked, but in addition can be set to \"auto\", to\n \tgenerate a cover-letter only when there's more than one patch.\n-\tDefault is false.\n+\tDefault is `false`.\n \n format.outputDirectory::\n \tSet a custom directory to store the resulting files instead of the\n@@ -119,11 +119,11 @@ format.useAutoBase::\n format.notes::\n \tProvides the default value for the `--notes` option to\n \tformat-patch. Accepts a boolean value, or a ref which specifies\n-\twhere to get notes. If false, format-patch defaults to\n-\t`--no-notes`. If true, format-patch defaults to `--notes`. If\n+\twhere to get notes. If `false`, format-patch defaults to\n+\t`--no-notes`. If `true`, format-patch defaults to `--notes`. If\n \tset to a non-boolean value, format-patch defaults to\n \t`--notes=<ref>`, where `ref` is the non-boolean value. Defaults\n-\tto false.\n+\tto `false`.\n +\n If one wishes to use the ref `refs/notes/true`, please use that literal\n instead.\ndiff --git a/Documentation/config/grep.adoc b/Documentation/config/grep.adoc\nindex 10041f27b0..a446830a5c 100644\n--- a/Documentation/config/grep.adoc\n+++ b/Documentation/config/grep.adoc\n@@ -1,8 +1,8 @@\n grep.lineNumber::\n-\tIf set to true, enable `-n` option by default.\n+\tIf set to `true`, enable `-n` option by default.\n \n grep.column::\n-\tIf set to true, enable the `--column` option by default.\n+\tIf set to `true`, enable the `--column` option by default.\n \n grep.patternType::\n \tSet the default matching behavior. Using a value of 'basic', 'extended',\n@@ -12,7 +12,7 @@ grep.patternType::\n \tbetween 'basic' and 'extended'.\n \n grep.extendedRegexp::\n-\tIf set to true, enable `--extended-regexp` option by default. This\n+\tIf set to `true`, enable `--extended-regexp` option by default. This\n \toption is ignored when the `grep.patternType` option is set to a value\n \tother than 'default'.\n \n@@ -21,8 +21,8 @@ grep.threads::\n \tuse as many threads as the number of logical cores available.\n \n grep.fullName::\n-\tIf set to true, enable `--full-name` option by default.\n+\tIf set to `true`, enable `--full-name` option by default.\n \n grep.fallbackToNoIndex::\n-\tIf set to true, fall back to `git grep --no-index` if `git grep`\n-\tis executed outside of a git repository.  Defaults to false.\n+\tIf set to `true`, fall back to `git grep --no-index` if `git grep`\n+\tis executed outside of a git repository.  Defaults to `false`.\ndiff --git a/Documentation/config/rebase.adoc b/Documentation/config/rebase.adoc\nindex c6187ab28b..307688f306 100644\n--- a/Documentation/config/rebase.adoc\n+++ b/Documentation/config/rebase.adoc\n@@ -9,22 +9,22 @@ rebase.stat::\n \trebase. False by default.\n \n rebase.autoSquash::\n-\tIf set to true, enable the `--autosquash` option of\n+\tIf set to `true`, enable the `--autosquash` option of\n \tlinkgit:git-rebase[1] by default for interactive mode.\n \tThis can be overridden with the `--no-autosquash` option.\n \n rebase.autoStash::\n-\tWhen set to true, automatically create a temporary stash entry\n+\tWhen set to `true`, automatically create a temporary stash entry\n \tbefore the operation begins, and apply it after the operation\n \tends.  This means that you can run rebase on a dirty worktree.\n \tHowever, use with care: the final stash application after a\n \tsuccessful rebase might result in non-trivial conflicts.\n \tThis option can be overridden by the `--no-autostash` and\n \t`--autostash` options of linkgit:git-rebase[1].\n-\tDefaults to false.\n+\tDefaults to `false`.\n \n rebase.updateRefs::\n-\tIf set to true enable `--update-refs` option by default.\n+\tIf set to `true` enable `--update-refs` option by default.\n \n rebase.missingCommitsCheck::\n \tIf set to \"warn\", git rebase -i will print a warning if some\n@@ -43,7 +43,7 @@ rebase.instructionFormat::\n \tautomatically have the commit hash prepended to the format.\n \n rebase.abbreviateCommands::\n-\tIf set to true, `git rebase` will use abbreviated command names in the\n+\tIf set to `true`, `git rebase` will use abbreviated command names in the\n \ttodo list resulting in something like this:\n +\n -------------------------------------------\n@@ -60,7 +60,7 @@ instead of:\n \t...\n -------------------------------------------\n +\n-Defaults to false.\n+Defaults to `false`.\n \n rebase.rescheduleFailedExec::\n \tAutomatically reschedule `exec` commands that failed. This only makes\n@@ -68,14 +68,14 @@ rebase.rescheduleFailedExec::\n \tThis is the same as specifying the `--reschedule-failed-exec` option.\n \n rebase.forkPoint::\n-\tIf set to false set `--no-fork-point` option by default.\n+\tIf set to `false` set `--no-fork-point` option by default.\n \n rebase.rebaseMerges::\n \tWhether and how to set the `--rebase-merges` option by default. Can\n \tbe `rebase-cousins`, `no-rebase-cousins`, or a boolean. Setting to\n-\ttrue or to `no-rebase-cousins` is equivalent to\n+\t`true` or to `no-rebase-cousins` is equivalent to\n \t`--rebase-merges=no-rebase-cousins`, setting to `rebase-cousins` is\n-\tequivalent to `--rebase-merges=rebase-cousins`, and setting to false is\n+\tequivalent to `--rebase-merges=rebase-cousins`, and setting to `false` is\n \tequivalent to `--no-rebase-merges`. Passing `--rebase-merges` on the\n \tcommand line, with or without an argument, overrides any\n \t`rebase.rebaseMerges` configuration.\ndiff --git a/Documentation/config/rerere.adoc b/Documentation/config/rerere.adoc\nindex 3a78b5ebb1..20eb3ba870 100644\n--- a/Documentation/config/rerere.adoc\n+++ b/Documentation/config/rerere.adoc\n@@ -1,7 +1,7 @@\n rerere.autoUpdate::\n-\tWhen set to true, `git-rerere` updates the index with the\n+\tWhen set to `true`, `git-rerere` updates the index with the\n \tresulting contents after it cleanly resolves conflicts using\n-\tpreviously recorded resolutions.  Defaults to false.\n+\tpreviously recorded resolutions.  Defaults to `false`.\n \n rerere.enabled::\n \tActivate recording of resolved conflicts, so that identical\ndiff --git a/Documentation/config/stash.adoc b/Documentation/config/stash.adoc\nindex a1197ffd7d..c4c998d575 100644\n--- a/Documentation/config/stash.adoc\n+++ b/Documentation/config/stash.adoc\n@@ -7,8 +7,8 @@ ifdef::git-stash[]\n endif::git-stash[]\n \n `stash.index`::\n-\tIf this is set to true, `git stash apply` and `git stash pop` will\n-\tbehave as if `--index` was supplied. Defaults to false.\n+\tIf this is set to `true`, `git stash apply` and `git stash pop` will\n+\tbehave as if `--index` was supplied. Defaults to `false`.\n ifndef::git-stash[]\n See the descriptions in linkgit:git-stash[1].\n +\n@@ -18,15 +18,15 @@ linkgit:git-pull[1].\n endif::git-stash[]\n \n `stash.showIncludeUntracked`::\n-\tIf this is set to true, the `git stash show` command will show\n-\tthe untracked files of a stash entry. Defaults to false. {see-show}\n+\tIf this is set to `true`, the `git stash show` command will show\n+\tthe untracked files of a stash entry. Defaults to `false`. {see-show}\n \n `stash.showPatch`::\n-\tIf this is set to true, the `git stash show` command without an\n-\toption will show the stash entry in patch form.  Defaults to false.\n+\tIf this is set to `true`, the `git stash show` command without an\n+\toption will show the stash entry in patch form.  Defaults to `false`.\n \t{see-show}\n \n `stash.showStat`::\n-\tIf this is set to true, the `git stash show` command without an\n-\toption will show a diffstat of the stash entry.  Defaults to true.\n+\tIf this is set to `true`, the `git stash show` command without an\n+\toption will show a diffstat of the stash entry.  Defaults to `true`.\n \t{see-show}\ndiff --git a/Documentation/config/status.adoc b/Documentation/config/status.adoc\nindex 8caf90f51c..fe0d44e617 100644\n--- a/Documentation/config/status.adoc\n+++ b/Documentation/config/status.adoc\n@@ -5,24 +5,24 @@ status.relativePaths::\n \tprior to v1.5.4).\n \n status.short::\n-\tSet to true to enable --short by default in linkgit:git-status[1].\n+\tSet to `true` to enable --short by default in linkgit:git-status[1].\n \tThe option --no-short takes precedence over this variable.\n \n status.branch::\n-\tSet to true to enable --branch by default in linkgit:git-status[1].\n+\tSet to `true` to enable --branch by default in linkgit:git-status[1].\n \tThe option --no-branch takes precedence over this variable.\n \n status.aheadBehind::\n-\tSet to true to enable `--ahead-behind` and false to enable\n+\tSet to `true` to enable `--ahead-behind` and `false` to enable\n \t`--no-ahead-behind` by default in linkgit:git-status[1] for\n-\tnon-porcelain status formats.  Defaults to true.\n+\tnon-porcelain status formats.  Defaults to `true`.\n \n status.displayCommentPrefix::\n-\tIf set to true, linkgit:git-status[1] will insert a comment\n+\tIf set to `true`, linkgit:git-status[1] will insert a comment\n \tprefix before each output line (starting with\n \t`core.commentChar`, i.e. `#` by default). This was the\n \tbehavior of linkgit:git-status[1] in Git 1.8.4 and previous.\n-\tDefaults to false.\n+\tDefaults to `false`.\n \n status.renameLimit::\n \tThe number of files to consider when performing rename detection\n@@ -37,9 +37,9 @@ status.renames::\n \tDefaults to the value of diff.renames.\n \n status.showStash::\n-\tIf set to true, linkgit:git-status[1] will display the number of\n+\tIf set to `true`, linkgit:git-status[1] will display the number of\n \tentries currently stashed away.\n-\tDefaults to false.\n+\tDefaults to `false`.\n \n status.showUntrackedFiles::\n \tBy default, linkgit:git-status[1] and linkgit:git-commit[1] show\n@@ -63,8 +63,8 @@ This variable can be overridden with the -u|--untracked-files option\n of linkgit:git-status[1] and linkgit:git-commit[1].\n \n status.submoduleSummary::\n-\tDefaults to false.\n-\tIf this is set to a non-zero number or true (identical to -1 or an\n+\tDefaults to `false`.\n+\tIf this is set to a non-zero number or `true` (identical to -1 or an\n \tunlimited number), the submodule summary will be enabled and a\n \tsummary of commits for modified submodules will be shown (see\n \t--summary-limit option of linkgit:git-submodule[1]). Please note\n\nbase-commit: 7c02d39fc2ed2702223c7674f73150d9a7e61ba4\n-- \ngitgitgadget\n"},{"id":"536745","messageId":"pull.2055.v2.git.1771845829480.gitgitgadget@gmail.com","threadId":"65053","inReplyTo":"pull.2055.git.1771844130973.gitgitgadget@gmail.com","subject":"[PATCH v2] doc: format config values with backticks","fromName":"Md Ferdous Alam via GitGitGadget","fromEmail":"gitgitgadget@gmail.com","sentAt":"2026-02-23T11:23:49Z","receivedAt":"2026-02-23T11:23:55Z","isPatch":true,"sender":{"key":"name:Md Ferdous Alam","avatar":null},"body":"From: mdferdousalam <mdferdousalam1989@yahoo.com>\n\nWrap bare true/false config values in backticks throughout the\nDocumentation/config/*.adoc files, following the convention used\nby most of the documentation. This ensures consistent formatting\nof boolean configuration values.\n\nSigned-off-by: Md Ferdous Alam <md.ferdous.alam.official@gmail.com>\n---\n    doc: format config values with backticks\n    \n    Add backtick formatting to bare true/false values in configuration\n    documentation so they render in monospace as config literals, matching\n    the style used throughout most of the existing documentation.\n    \n    Files updated:\n    \n     * am.adoc, blame.adoc, branch.adoc, clean.adoc, color.adoc\n     * commitgraph.adoc, core.adoc, credential.adoc, fetch.adoc\n     * fmt-merge-msg.adoc, format.adoc, gc.adoc, gitcvs.adoc\n     * grep.adoc, gui.adoc, http.adoc, instaweb.adoc, interactive.adoc\n     * log.adoc, mailinfo.adoc, maintenance.adoc, merge.adoc\n     * mergetool.adoc, pack.adoc, pull.adoc, push.adoc, rebase.adoc\n     * receive.adoc, remote.adoc, repack.adoc, rerere.adoc, revert.adoc\n     * stash.adoc, status.adoc, submodule.adoc, trace2.adoc\n     * transfer.adoc, uploadarchive.adoc, worktree.adoc\n    \n    This addresses https://github.com/gitgitgadget/git/issues/244\n\nPublished-As: https://github.com/gitgitgadget/git/releases/tag/pr-2055%2Fmdferdousalam%2Ffix-config-doc-formatting-v2\nFetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-2055/mdferdousalam/fix-config-doc-formatting-v2\nPull-Request: https://github.com/gitgitgadget/git/pull/2055\n\nRange-diff vs v1:\n\n 1:  631b9abe41 ! 1:  3a1ca6e5d9 doc: format config values with backticks\n     @@ Metadata\n       ## Commit message ##\n          doc: format config values with backticks\n      \n     -    Add backtick formatting to bare true/false values in configuration\n     -    documentation so they render in monospace as config literals, matching\n     -    the style used throughout most of the existing documentation.\n     +    Wrap bare true/false config values in backticks throughout the\n     +    Documentation/config/*.adoc files, following the convention used\n     +    by most of the documentation. This ensures consistent formatting\n     +    of boolean configuration values.\n      \n     -    Signed-off-by: Md Ferdous Alam <mdferdousalam@gmail.com>\n     +    Signed-off-by: Md Ferdous Alam <md.ferdous.alam.official@gmail.com>\n      \n       ## Documentation/config/am.adoc ##\n      @@\n     @@ Documentation/config/blame.adoc\n       \n       blame.coloring::\n       \tThis determines the coloring scheme to be applied to blame\n     +@@ Documentation/config/blame.adoc: blame.date::\n     + \n     + blame.showEmail::\n     + \tShow the author email instead of author name in linkgit:git-blame[1].\n     +-\tThis option defaults to false.\n     ++\tThis option defaults to `false`.\n     + \n     + blame.showRoot::\n     + \tDo not treat root commits as boundaries in linkgit:git-blame[1].\n     +-\tThis option defaults to false.\n     ++\tThis option defaults to `false`.\n     + \n     + blame.ignoreRevsFile::\n     + \tIgnore revisions listed in the file, one unabbreviated object name per\n     +\n     + ## Documentation/config/branch.adoc ##\n     +@@\n     + \tthat tracks another branch, this variable tells Git to set\n     + \tup pull to rebase instead of merge (see `branch.<name>.rebase`).\n     + \tThe valid settings are:\n     +-`never`;; rebase is never automatically set to true.\n     +-`local`;; rebase is set to true for tracked branches of other local branches.\n     +-`remote`;; rebase is set to true for tracked branches of remote-tracking branches.\n     +-`always`;; rebase will be set to true for all tracking branches.\n     ++`never`;; rebase is never automatically set to `true`.\n     ++`local`;; rebase is set to `true` for tracked branches of other local branches.\n     ++`remote`;; rebase is set to `true` for tracked branches of remote-tracking branches.\n     ++`always`;; rebase will be set to `true` for all tracking branches.\n     + \n     + +\n     + See `branch.autoSetupMerge` for details on how to set up a branch to track another branch.\n     +@@ Documentation/config/branch.adoc: This option defaults to `never`.\n     + \tsupported.\n     + \n     + `branch.<name>.rebase`::\n     +-\tWhen true, rebase the branch _<name>_ on top of the fetched branch,\n     ++\tWhen `true`, rebase the branch _<name>_ on top of the fetched branch,\n     + \tinstead of merging the default branch from the default remote when\n     + \t`git pull` is run. See `pull.rebase` for doing this in a non\n     + \tbranch-specific manner.\n      \n       ## Documentation/config/clean.adoc ##\n      @@\n     @@ Documentation/config/clean.adoc\n      -\tis given. Defaults to true.\n      +\tis given. Defaults to `true`.\n      \n     + ## Documentation/config/color.adoc ##\n     +@@ Documentation/config/color.adoc: color.interactive.<slot>::\n     + \n     + color.pager::\n     + \tA boolean to specify whether `auto` color modes should colorize\n     +-\toutput going to the pager. Defaults to true; set this to false\n     ++\toutput going to the pager. Defaults to `true`; set this to `false`\n     + \tif your pager does not understand ANSI color codes.\n     + \n     + color.push::\n     +\n       ## Documentation/config/commitgraph.adoc ##\n      @@ Documentation/config/commitgraph.adoc: commitGraph.maxNewFilters::\n       \tcommit-graph write` (c.f., linkgit:git-commit-graph[1]).\n     @@ Documentation/config/commitgraph.adoc: commitGraph.changedPaths::\n       \n       commitGraph.changedPathsVersion::\n      \n     + ## Documentation/config/core.adoc ##\n     +@@ Documentation/config/core.adoc: Git for Windows or Eclipse).\n     + In such a case it may be necessary to set this variable to 'false'.\n     + See linkgit:git-update-index[1].\n     + +\n     +-The default is true (when core.filemode is not specified in the config file).\n     ++The default is `true` (when core.filemode is not specified in the config file).\n     + \n     + core.hideDotFiles::\n     +-\t(Windows-only) If true, mark newly-created directories and files whose\n     ++\t(Windows-only) If `true`, mark newly-created directories and files whose\n     + \tname starts with a dot as hidden.  If 'dotGitOnly', only the `.git/`\n     + \tdirectory is hidden, but no other files starting with a dot.  The\n     + \tdefault mode is 'dotGitOnly'.\n     +@@ Documentation/config/core.adoc: core.ignoreCase::\n     + \tit is really the same file, and continue to remember it as\n     + \t\"Makefile\".\n     + +\n     +-The default is false, except linkgit:git-clone[1] or linkgit:git-init[1]\n     +-will probe and set core.ignoreCase true if appropriate when the repository\n     ++The default is `false`, except linkgit:git-clone[1] or linkgit:git-init[1]\n     ++will probe and set core.ignoreCase `true` if appropriate when the repository\n     + is created.\n     + +\n     + Git relies on the proper configuration of this variable for your operating\n     +@@ Documentation/config/core.adoc: and file system. Modifying this value may result in unexpected behavior.\n     + \n     + core.precomposeUnicode::\n     + \tThis option is only used by Mac OS implementation of Git.\n     +-\tWhen core.precomposeUnicode=true, Git reverts the unicode decomposition\n     ++\tWhen core.precomposeUnicode=`true`, Git reverts the unicode decomposition\n     + \tof filenames done by Mac OS. This is useful when sharing a repository\n     + \tbetween Mac OS and Linux or Windows.\n     + \t(Git for Windows 1.7.10 or higher is needed, or Git under cygwin 1.7).\n     +-\tWhen false, file names are handled fully transparent by Git,\n     ++\tWhen `false`, file names are handled fully transparent by Git,\n     + \twhich is backward compatible with older versions of Git.\n     + \n     + core.protectHFS::\n     +-\tIf set to true, do not allow checkout of paths that would\n     ++\tIf set to `true`, do not allow checkout of paths that would\n     + \tbe considered equivalent to `.git` on an HFS+ filesystem.\n     + \tDefaults to `true` on Mac OS, and `false` elsewhere.\n     + \n     + core.protectNTFS::\n     +-\tIf set to true, do not allow checkout of paths that would\n     ++\tIf set to `true`, do not allow checkout of paths that would\n     + \tcause problems with the NTFS filesystem, e.g. conflict with\n     + \t8.3 \"short\" names.\n     + \tDefaults to `true` on Windows, and `false` elsewhere.\n     + \n     + core.fsmonitor::\n     +-\tIf set to true, enable the built-in file system monitor\n     ++\tIf set to `true`, enable the built-in file system monitor\n     + \tdaemon for this working directory (linkgit:git-fsmonitor{litdd}daemon[1]).\n     + +\n     + Like hook-based file system monitors, the built-in file system monitor\n     +@@ Documentation/config/core.adoc: something that can be used to determine what files have changed\n     + without race conditions.\n     + \n     + core.trustctime::\n     +-\tIf false, the ctime differences between the index and the\n     ++\tIf `false`, the ctime differences between the index and the\n     + \tworking tree are ignored; useful when the inode change time\n     + \tis regularly modified by something outside Git (file system\n     + \tcrawlers and some backup systems).\n     +-\tSee linkgit:git-update-index[1]. True by default.\n     ++\tSee linkgit:git-update-index[1]. `True` by default.\n     + \n     + core.splitIndex::\n     +-\tIf true, the split-index feature of the index will be used.\n     +-\tSee linkgit:git-update-index[1]. False by default.\n     ++\tIf `true`, the split-index feature of the index will be used.\n     ++\tSee linkgit:git-update-index[1]. `False` by default.\n     + \n     + core.untrackedCache::\n     + \tDetermines what to do about the untracked cache feature of the\n     +@@ Documentation/config/core.adoc: core.quotePath::\n     + \tbackslashes in the same way C escapes control characters (e.g.\n     + \t`\\t` for TAB, `\\n` for LF, `\\\\` for backslash) or bytes with\n     + \tvalues larger than 0x80 (e.g. octal `\\302\\265` for \"micro\" in\n     +-\tUTF-8).  If this variable is set to false, bytes higher than\n     ++\tUTF-8).  If this variable is set to `false`, bytes higher than\n     + \t0x80 are not considered \"unusual\" any more. Double-quotes,\n     + \tbackslash and control characters are always escaped regardless\n     + \tof the setting of this variable.  A simple space character is\n     + \tnot considered \"unusual\".  Many commands can output pathnames\n     + \tcompletely verbatim using the `-z` option. The default value\n     +-\tis true.\n     ++\tis `true`.\n     + \n     + core.eol::\n     + \tSets the line ending type to use in the working directory for\n     +@@ Documentation/config/core.adoc: core.eol::\n     + \tis set to `true` or `input`.\n     + \n     + core.safecrlf::\n     +-\tIf true, makes Git check if converting `CRLF` is reversible when\n     ++\tIf `true`, makes Git check if converting `CRLF` is reversible when\n     + \tend-of-line conversion is active.  Git will verify if a command\n     + \tmodifies a file in the work tree either directly or indirectly.\n     + \tFor example, committing a file followed by checking out the\n     +@@ Documentation/config/core.adoc: mechanism.\n     + core.autocrlf::\n     + \tSetting this variable to \"true\" is the same as setting\n     + \tthe `text` attribute to \"auto\" on all files and core.eol to \"crlf\".\n     +-\tSet to true if you want to have `CRLF` line endings in your\n     ++\tSet to `true` if you want to have `CRLF` line endings in your\n     + \tworking directory and the repository has LF line endings.\n     + \tThis variable can be set to 'input',\n     + \tin which case no output conversion is performed.\n     +@@ Documentation/config/core.adoc: core.checkRoundtripEncoding::\n     + \tThe default value is `SHIFT-JIS`.\n     + \n     + core.symlinks::\n     +-\tIf false, symbolic links are checked out as small plain files that\n     ++\tIf `false`, symbolic links are checked out as small plain files that\n     + \tcontain the link text. linkgit:git-update-index[1] and\n     + \tlinkgit:git-add[1] will not change the recorded type to regular\n     + \tfile. Useful on filesystems like FAT that do not support\n     + \tsymbolic links.\n     + +\n     +-The default is true, except linkgit:git-clone[1] or linkgit:git-init[1]\n     +-will probe and set core.symlinks false if appropriate when the repository\n     ++The default is `true`, except linkgit:git-clone[1] or linkgit:git-init[1]\n     ++will probe and set core.symlinks `false` if appropriate when the repository\n     + is created.\n     + \n     + core.gitProxy::\n     +@@ Documentation/config/core.adoc: core.sshCommand::\n     + \twhen the environment variable is set.\n     + \n     + core.ignoreStat::\n     +-\tIf true, Git will avoid using lstat() calls to detect if files have\n     ++\tIf `true`, Git will avoid using lstat() calls to detect if files have\n     + \tchanged by setting the \"assume-unchanged\" bit for those tracked files\n     + \twhich it has updated identically in both the index and working tree.\n     + +\n     +@@ Documentation/config/core.adoc: Git will not normally detect changes to those files.\n     + This is useful on systems where lstat() calls are very slow, such as\n     + CIFS/Microsoft Windows.\n     + +\n     +-False by default.\n     ++`False` by default.\n     + \n     + core.preferSymlinkRefs::\n     + \tInstead of the default \"symref\" format for HEAD\n     +@@ Documentation/config/core.adoc: core.alternateRefsPrefixes::\n     + \t`core.alternateRefsPrefixes` has no effect.\n     + \n     + core.bare::\n     +-\tIf true this repository is assumed to be 'bare' and has no\n     ++\tIf `true` this repository is assumed to be 'bare' and has no\n     + \tworking directory associated with it.  If this is the case a\n     + \tnumber of commands that require a working directory will be\n     + \tdisabled, such as linkgit:git-add[1] or linkgit:git-merge[1].\n     +@@ Documentation/config/core.adoc: core.bare::\n     + This setting is automatically guessed by linkgit:git-clone[1] or\n     + linkgit:git-init[1] when the repository was created.  By default a\n     + repository that ends in \"/.git\" is assumed to be not bare (bare =\n     +-false), while all other repositories are assumed to be bare (bare\n     +-= true).\n     ++`false`), while all other repositories are assumed to be bare (bare\n     ++= `true`).\n     + \n     + core.worktree::\n     + \tSet the path to the root of the working tree.\n     +@@ Documentation/config/core.adoc: read-only snapshot of the same index to a location different from the\n     + repository's usual working tree).\n     + \n     + core.lockfilePid::\n     +-\tIf true, Git will create a PID file alongside lock files. When a\n     ++\tIf `true`, Git will create a PID file alongside lock files. When a\n     + \tlock acquisition fails and a PID file exists, Git can provide\n     + \tadditional diagnostic information about the process holding the\n     + \tlock, including whether it is still running. Defaults to `false`.\n     +@@ Documentation/config/core.adoc: core.logAllRefUpdates::\n     + This information can be used to determine what commit\n     + was the tip of a branch \"2 days ago\".\n     + +\n     +-This value is true by default in a repository that has\n     +-a working directory associated with it, and false by\n     ++This value is `true` by default in a repository that has\n     ++a working directory associated with it, and `false` by\n     + default in a bare repository.\n     + \n     + core.repositoryFormatVersion::\n     +@@ Documentation/config/core.adoc: core.sharedRepository::\n     + \tthe repo read/write-able for the owner and group, but inaccessible to\n     + \tothers (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a\n     + \trepository that is group-readable but not group-writable.\n     +-\tSee linkgit:git-init[1]. False by default.\n     ++\tSee linkgit:git-init[1]. `False` by default.\n     + \n     + core.warnAmbiguousRefs::\n     +-\tIf true, Git will warn you if the ref name you passed it is ambiguous\n     +-\tand might match multiple refs in the repository. True by default.\n     ++\tIf `true`, Git will warn you if the ref name you passed it is ambiguous\n     ++\tand might match multiple refs in the repository. `True` by default.\n     + \n     + core.compression::\n     + \tAn integer -1..9, indicating a default compression level.\n     +@@ Documentation/config/core.adoc: core.fsyncObjectFiles::\n     + \tThis setting is deprecated. Use core.fsync instead.\n     + +\n     + This setting affects data added to the Git repository in loose-object\n     +-form. When set to true, Git will issue an fsync or similar system call\n     ++form. When set to `true`, Git will issue an fsync or similar system call\n     + to flush caches so that loose-objects remain consistent in the face\n     + of a unclean system shutdown.\n     + \n     +@@ Documentation/config/core.adoc: This can speed up operations like 'git diff' and 'git status' especially\n     + on filesystems like NFS that have weak caching semantics and thus\n     + relatively high IO latencies.  When enabled, Git will do the\n     + index comparison to the filesystem data in parallel, allowing\n     +-overlapping IO's.  Defaults to true.\n     ++overlapping IO's.  Defaults to `true`.\n     + \n     + core.unsetenvvars::\n     + \tWindows-only: comma-separated list of environment variables'\n     +@@ Documentation/config/core.adoc: This setting defaults to \"refs/notes/commits\", and it can be overridden by\n     + the `GIT_NOTES_REF` environment variable.  See linkgit:git-notes[1].\n     + \n     + core.commitGraph::\n     +-\tIf true, then git will read the commit-graph file (if it exists)\n     +-\tto parse the graph structure of commits. Defaults to true. See\n     ++\tIf `true`, then git will read the commit-graph file (if it exists)\n     ++\tto parse the graph structure of commits. Defaults to `true`. See\n     + \tlinkgit:git-commit-graph[1] for more information.\n     + \n     + core.useReplaceRefs::\n     +@@ Documentation/config/core.adoc: core.useReplaceRefs::\n     + core.multiPackIndex::\n     + \tUse the multi-pack-index file to track multiple packfiles using a\n     + \tsingle index. See linkgit:git-multi-pack-index[1] for more\n     +-\tinformation. Defaults to true.\n     ++\tinformation. Defaults to `true`.\n     + \n     + core.sparseCheckout::\n     + \tEnable \"sparse checkout\" feature. See linkgit:git-sparse-checkout[1]\n     +\n       ## Documentation/config/credential.adoc ##\n      @@ Documentation/config/credential.adoc: credential.interactive::\n       \n     @@ Documentation/config/credential.adoc: credential.interactive::\n       \n       credential.sanitizePrompt::\n      \n     + ## Documentation/config/fetch.adoc ##\n     +@@\n     + \tin `git pull`) will recursively fetch into populated submodules.\n     + \tThis option can be set either to a boolean value or to `on-demand`.\n     + \tSetting it to a boolean changes the behavior of fetch and pull to\n     +-\trecurse unconditionally into submodules when set to true or to not\n     +-\trecurse at all when set to false. When set to `on-demand`, fetch and\n     ++\trecurse unconditionally into submodules when set to `true` or to not\n     ++\trecurse at all when set to `false`. When set to `on-demand`, fetch and\n     + \tpull will only recurse into a populated submodule when its\n     + \tsuperproject retrieves a commit that updates the submodule's\n     + \treference.\n     + \tDefaults to `on-demand`, or to the value of `submodule.recurse` if set.\n     + \n     + `fetch.fsckObjects`::\n     +-\tIf it is set to true, git-fetch-pack will check all fetched\n     ++\tIf it is set to `true`, git-fetch-pack will check all fetched\n     + \tobjects. See `transfer.fsckObjects` for what's\n     + \tchecked. Defaults to `false`. If not set, the value of\n     + \t`transfer.fsckObjects` is used instead.\n     +@@\n     + \t`transfer.unpackLimit` is used instead.\n     + \n     + `fetch.prune`::\n     +-\tIf true, fetch will automatically behave as if the `--prune`\n     ++\tIf `true`, fetch will automatically behave as if the `--prune`\n     + \toption was given on the command line.  See also `remote.<name>.prune`\n     + \tand the PRUNING section of linkgit:git-fetch[1].\n     + \n     + `fetch.pruneTags`::\n     +-\tIf true, fetch will automatically behave as if the\n     ++\tIf `true`, fetch will automatically behave as if the\n     + \t`refs/tags/*:refs/tags/*` refspec was provided when pruning,\n     + \tif not set already. This allows for setting both this option\n     + \tand `fetch.prune` to maintain a 1=1 mapping to upstream\n     +@@\n     + \tsection of linkgit:git-fetch[1].\n     + \n     + `fetch.all`::\n     +-\tIf true, fetch will attempt to update all available remotes.\n     ++\tIf `true`, fetch will attempt to update all available remotes.\n     + \tThis behavior can be overridden by passing `--no-all` or by\n     + \texplicitly specifying one or more remote(s) to fetch from.\n     + \tDefaults to `false`.\n     +@@ Documentation/config/fetch.adoc: For submodules, this setting can be overridden using the `submodule.fetchJobs`\n     + config setting.\n     + \n     + `fetch.writeCommitGraph`::\n     +-\tSet to true to write a commit-graph after every `git fetch` command\n     ++\tSet to `true` to write a commit-graph after every `git fetch` command\n     + \tthat downloads a pack-file from a remote. Using the `--split` option,\n     + \tmost executions will create a very small commit-graph file on top of\n     + \tthe existing commit-graph file(s). Occasionally, these files will\n     +\n       ## Documentation/config/fmt-merge-msg.adoc ##\n      @@\n       `merge.branchdesc`::\n     @@ Documentation/config/format.adoc: format.useAutoBase::\n       If one wishes to use the ref `refs/notes/true`, please use that literal\n       instead.\n      \n     + ## Documentation/config/gc.adoc ##\n     +@@ Documentation/config/gc.adoc: use, it'll affect how the auto pack limit works.\n     + \n     + gc.autoDetach::\n     + \tMake `git gc --auto` return immediately and run in the background\n     +-\tif the system supports it. Default is true. This config variable acts\n     ++\tif the system supports it. Default is `true`. This config variable acts\n     + \tas a fallback in case `maintenance.autoDetach` is not set.\n     + \n     + gc.bigPackThreshold::\n     +@@ Documentation/config/gc.adoc: will also be excluded (this is the equivalent of running `git gc` with\n     + `--keep-largest-pack`).\n     + \n     + gc.writeCommitGraph::\n     +-\tIf true, then gc will rewrite the commit-graph file when\n     ++\tIf `true`, then gc will rewrite the commit-graph file when\n     + \tlinkgit:git-gc[1] is run. When using `git gc --auto`\n     + \tthe commit-graph will be updated if housekeeping is\n     +-\trequired. Default is true. See linkgit:git-commit-graph[1]\n     ++\trequired. Default is `true`. See linkgit:git-commit-graph[1]\n     + \tfor details.\n     + \n     + gc.logExpiry::\n     +\n     + ## Documentation/config/gitcvs.adoc ##\n     +@@ Documentation/config/gitcvs.adoc: gitcvs.logFile::\n     + \tvarious stuff. See linkgit:git-cvsserver[1].\n     + \n     + gitcvs.usecrlfattr::\n     +-\tIf true, the server will look up the end-of-line conversion\n     ++\tIf `true`, the server will look up the end-of-line conversion\n     + \tattributes for files to determine the `-k` modes to use. If\n     + \tthe attributes force Git to treat a file as text,\n     + \tthe `-k` mode will be left blank so CVS clients will\n     +@@ Documentation/config/gitcvs.adoc: gitcvs.usecrlfattr::\n     + \n     + gitcvs.allBinary::\n     + \tThis is used if `gitcvs.usecrlfattr` does not resolve\n     +-\tthe correct '-kb' mode to use. If true, all\n     ++\tthe correct '-kb' mode to use. If `true`, all\n     + \tunresolved files are sent to the client in\n     + \tmode '-kb'. This causes the client to treat them\n     + \tas binary files, which suppresses any newline munging it\n     +\n       ## Documentation/config/grep.adoc ##\n      @@\n       grep.lineNumber::\n     @@ Documentation/config/grep.adoc: grep.threads::\n      +\tIf set to `true`, fall back to `git grep --no-index` if `git grep`\n      +\tis executed outside of a git repository.  Defaults to `false`.\n      \n     + ## Documentation/config/gui.adoc ##\n     +@@ Documentation/config/gui.adoc: gui.spellingDictionary::\n     + \toff.\n     + \n     + gui.fastCopyBlame::\n     +-\tIf true, 'git gui blame' uses `-C` instead of `-C -C` for original\n     ++\tIf `true`, 'git gui blame' uses `-C` instead of `-C -C` for original\n     + \tlocation detection. It makes blame significantly faster on huge\n     + \trepositories at the expense of less thorough copy detection.\n     + \n     +\n     + ## Documentation/config/http.adoc ##\n     +@@ Documentation/config/http.adoc: http.emptyAuth::\n     + http.proactiveAuth::\n     + \tAttempt authentication without first making an unauthenticated attempt and\n     + \treceiving a 401 response. This can be used to ensure that all requests are\n     +-\tauthenticated. If `http.emptyAuth` is set to true, this value has no effect.\n     ++\tauthenticated. If `http.emptyAuth` is set to `true`, this value has no effect.\n     + +\n     + If the credential helper used specifies an authentication scheme (i.e., via the\n     + `authtype` field), that value will be used; if a username and password is\n     +@@ Documentation/config/http.adoc: empty string.\n     + \n     + http.sslVerify::\n     + \tWhether to verify the SSL certificate when fetching or pushing\n     +-\tover HTTPS. Defaults to true. Can be overridden by the\n     ++\tover HTTPS. Defaults to `true`. Can be overridden by the\n     + \t`GIT_SSL_NO_VERIFY` environment variable.\n     + \n     + http.sslCert::\n     +@@ Documentation/config/http.adoc: http.sslTry::\n     + \twhen connecting via regular FTP protocol. This might be needed\n     + \tif the FTP server requires it for security reasons or you wish\n     + \tto connect securely whenever remote FTP server supports it.\n     +-\tDefault is false since it might trigger certificate verification\n     ++\tDefault is `false` since it might trigger certificate verification\n     + \terrors on misconfigured servers.\n     + \n     + http.maxRequests::\n     +@@ Documentation/config/http.adoc: http.noEPSV::\n     + \tA boolean which disables using of EPSV ftp command by curl.\n     + \tThis can be helpful with some \"poor\" ftp servers which don't\n     + \tsupport EPSV mode. Can be overridden by the `GIT_CURL_FTP_NO_EPSV`\n     +-\tenvironment variable. Default is false (curl will use EPSV).\n     ++\tenvironment variable. Default is `false` (curl will use EPSV).\n     + \n     + http.userAgent::\n     + \tThe HTTP USER_AGENT string presented to an HTTP server.  The default\n     +\n     + ## Documentation/config/instaweb.adoc ##\n     +@@ Documentation/config/instaweb.adoc: instaweb.httpd::\n     + \trepository. See linkgit:git-instaweb[1].\n     + \n     + instaweb.local::\n     +-\tIf true the web server started by linkgit:git-instaweb[1] will\n     ++\tIf `true` the web server started by linkgit:git-instaweb[1] will\n     + \tbe bound to the local IP (127.0.0.1).\n     + \n     + instaweb.modulePath::\n     +\n     + ## Documentation/config/interactive.adoc ##\n     +@@\n     + interactive.singleKey::\n     +-\tWhen set to true, allow the user to provide one-letter input\n     ++\tWhen set to `true`, allow the user to provide one-letter input\n     + \twith a single key (i.e., without hitting the Enter key) in\n     + \tinteractive commands.  This is currently used by the `--patch`\n     + \tmode of linkgit:git-add[1], linkgit:git-checkout[1],\n     +\n     + ## Documentation/config/log.adoc ##\n     +@@ Documentation/config/log.adoc: This is the same as the `--decorate` option of the `git log`.\n     + \thistory lines in `git log --graph`.\n     + \n     + `log.showRoot`::\n     +-\tIf true, the initial commit will be shown as a big creation event.\n     ++\tIf `true`, the initial commit will be shown as a big creation event.\n     + \tThis is equivalent to a diff against an empty tree.\n     + \tTools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which\n     + \tnormally hide the root commit will now show it. True by default.\n     + \n     + `log.showSignature`::\n     +-\tIf true, makes linkgit:git-log[1], linkgit:git-show[1], and\n     ++\tIf `true`, makes linkgit:git-log[1], linkgit:git-show[1], and\n     + \tlinkgit:git-whatchanged[1] assume `--show-signature`.\n     + \n     + `log.mailmap`::\n     +-\tIf true, makes linkgit:git-log[1], linkgit:git-show[1], and\n     ++\tIf `true`, makes linkgit:git-log[1], linkgit:git-show[1], and\n     + \tlinkgit:git-whatchanged[1] assume `--use-mailmap`, otherwise\n     + \tassume `--no-use-mailmap`. True by default.\n     +\n     + ## Documentation/config/mailinfo.adoc ##\n     +@@\n     + mailinfo.scissors::\n     +-\tIf true, makes linkgit:git-mailinfo[1] (and therefore\n     ++\tIf `true`, makes linkgit:git-mailinfo[1] (and therefore\n     + \tlinkgit:git-am[1]) act by default as if the --scissors option\n     + \twas provided on the command-line. When active, this feature\n     + \tremoves everything from the message body before a scissors\n     +\n     + ## Documentation/config/maintenance.adoc ##\n     +@@\n     + maintenance.auto::\n     + \tThis boolean config option controls whether some commands run\n     + \t`git maintenance run --auto` after doing their normal work. Defaults\n     +-\tto true.\n     ++\tto `true`.\n     + \n     + maintenance.autoDetach::\n     + \tMany Git commands trigger automatic maintenance after they have\n     +@@ Documentation/config/maintenance.adoc: maintenance.autoDetach::\n     + \tcontinue to run in the background.\n     + +\n     + If unset, the value of `gc.autoDetach` is used as a fallback. Defaults\n     +-to true if both are unset, meaning that the maintenance process will\n     ++to `true` if both are unset, meaning that the maintenance process will\n     + detach.\n     + \n     + maintenance.strategy::\n     +@@ Documentation/config/maintenance.adoc: maintenance.<task>.enabled::\n     + \twith name `<task>` is run when no `--task` option is specified to\n     + \t`git maintenance run`. These config values are ignored if a\n     + \t`--task` option exists. By default, only `maintenance.gc.enabled`\n     +-\tis true.\n     ++\tis `true`.\n     + \n     + maintenance.<task>.schedule::\n     + \tThis config option controls whether or not the given `<task>` runs\n     +\n     + ## Documentation/config/merge.adoc ##\n     +@@\n     + \tbranches at the remote named by `branch.<current-branch>.remote`\n     + \tare consulted, and then they are mapped via `remote.<remote>.fetch`\n     + \tto their corresponding remote-tracking branches, and the tips of\n     +-\tthese tracking branches are merged. Defaults to true.\n     ++\tthese tracking branches are merged. Defaults to `true`.\n     + \n     + `merge.ff`::\n     + \tBy default, Git does not create an extra merge commit when merging\n     +@@\n     + \tcommand line).\n     + \n     + `merge.verifySignatures`::\n     +-\tIf true, this is equivalent to the `--verify-signatures` command\n     ++\tIf `true`, this is equivalent to the `--verify-signatures` command\n     + \tline option. See linkgit:git-merge[1] for details.\n     + \n     + include::fmt-merge-msg.adoc[]\n     +\n     + ## Documentation/config/mergetool.adoc ##\n     +@@\n     + `mergetool.<tool>.trustExitCode`::\n     + \tFor a custom merge command, specify whether the exit code of\n     + \tthe merge command can be used to determine whether the merge was\n     +-\tsuccessful.  If this is not set to true then the merge target file\n     ++\tsuccessful.  If this is not set to `true` then the merge target file\n     + \ttimestamp is checked, and the merge is assumed to have been successful\n     + \tif the file has been updated; otherwise, the user is prompted to\n     + \tindicate the success of the merge.\n     +\n     + ## Documentation/config/pack.adoc ##\n     +@@ Documentation/config/pack.adoc: all existing objects. You can force recompression by passing the -F option\n     + to linkgit:git-repack[1].\n     + \n     + pack.allowPackReuse::\n     +-\tWhen true or \"single\", and when reachability bitmaps are\n     ++\tWhen `true` or \"single\", and when reachability bitmaps are\n     + \tenabled, pack-objects will try to send parts of the bitmapped\n     + \tpackfile verbatim. When \"multi\", and when a multi-pack\n     + \treachability bitmap is available, pack-objects will try to send\n     +@@ Documentation/config/pack.adoc: pack.allowPackReuse::\n     + If only a single pack bitmap is available, and `pack.allowPackReuse`\n     + is set to \"multi\", reuse parts of just the bitmapped packfile. This\n     + can reduce memory and CPU usage to serve fetches, but might result in\n     +-sending a slightly larger pack. Defaults to true.\n     ++sending a slightly larger pack. Defaults to `true`.\n     + \n     + pack.island::\n     + \tAn extended regular expression configuring a set of delta\n     +@@ Documentation/config/pack.adoc: The minimum size allowed is limited to 1 MiB. The default is unlimited.\n     + Common unit suffixes of 'k', 'm', or 'g' are supported.\n     + \n     + pack.useBitmaps::\n     +-\tWhen true, git will use pack bitmaps (if available) when packing\n     ++\tWhen `true`, git will use pack bitmaps (if available) when packing\n     + \tto stdout (e.g., during the server side of a fetch). Defaults to\n     +-\ttrue. You should not generally need to turn this off unless\n     ++\t`true`. You should not generally need to turn this off unless\n     + \tyou are debugging pack bitmaps.\n     + \n     + pack.useBitmapBoundaryTraversal::\n     +-\tWhen true, Git will use an experimental algorithm for computing\n     ++\tWhen `true`, Git will use an experimental algorithm for computing\n     + \treachability queries with bitmaps. Instead of building up\n     + \tcomplete bitmaps for all of the negated tips and then OR-ing\n     + \tthem together, consider negated tips with existing bitmaps as\n     +@@ Documentation/config/pack.adoc: particularly when there is poor bitmap coverage of the negated side of\n     + the query.\n     + \n     + pack.useSparse::\n     +-\tWhen true, git will default to using the '--sparse' option in\n     ++\tWhen `true`, git will default to using the '--sparse' option in\n     + \t'git pack-objects' when the '--revs' option is present. This\n     + \talgorithm only walks trees that appear in paths that introduce new\n     + \tobjects. This can have significant performance benefits when\n     +@@ Documentation/config/pack.adoc: pack.writeBitmaps (deprecated)::\n     + \tThis is a deprecated synonym for `repack.writeBitmaps`.\n     + \n     + pack.writeBitmapHashCache::\n     +-\tWhen true, git will include a \"hash cache\" section in the bitmap\n     ++\tWhen `true`, git will include a \"hash cache\" section in the bitmap\n     + \tindex (if one is written). This cache can be used to feed git's\n     + \tdelta heuristics, potentially leading to better deltas between\n     + \tbitmapped and non-bitmapped objects (e.g., when serving a fetch\n     + \tbetween an older, bitmapped pack and objects that have been\n     + \tpushed since the last gc). The downside is that it consumes 4\n     +-\tbytes per object of disk space. Defaults to true.\n     ++\tbytes per object of disk space. Defaults to `true`.\n     + +\n     + When writing a multi-pack reachability bitmap, no new namehashes are\n     + computed; instead, any namehashes stored in an existing bitmap are\n     + permuted into their appropriate location when writing a new bitmap.\n     + \n     + pack.writeBitmapLookupTable::\n     +-\tWhen true, Git will include a \"lookup table\" section in the\n     ++\tWhen `true`, Git will include a \"lookup table\" section in the\n     + \tbitmap index (if one is written). This table is used to defer\n     + \tloading individual bitmaps as late as possible. This can be\n     + \tbeneficial in repositories that have relatively large bitmap\n     +-\tindexes. Defaults to false.\n     ++\tindexes. Defaults to `false`.\n     + \n     + pack.readReverseIndex::\n     +-\tWhen true, git will read any .rev file(s) that may be available\n     +-\t(see: linkgit:gitformat-pack[5]). When false, the reverse index\n     ++\tWhen `true`, git will read any .rev file(s) that may be available\n     ++\t(see: linkgit:gitformat-pack[5]). When `false`, the reverse index\n     + \twill be generated from scratch and stored in memory. Defaults to\n     +-\ttrue.\n     ++\t`true`.\n     + \n     + pack.writeReverseIndex::\n     +-\tWhen true, git will write a corresponding .rev file (see:\n     ++\tWhen `true`, git will write a corresponding .rev file (see:\n     + \tlinkgit:gitformat-pack[5])\n     + \tfor each new packfile that it writes in all places except for\n     + \tlinkgit:git-fast-import[1] and in the bulk checkin mechanism.\n     +-\tDefaults to true.\n     ++\tDefaults to `true`.\n     +\n     + ## Documentation/config/pull.adoc ##\n     +@@ Documentation/config/pull.adoc: pull.ff::\n     + \tcommand line). This setting overrides `merge.ff` when pulling.\n     + \n     + pull.rebase::\n     +-\tWhen true, rebase branches on top of the fetched branch, instead\n     ++\tWhen `true`, rebase branches on top of the fetched branch, instead\n     + \tof merging the default branch from the default remote when \"git\n     + \tpull\" is run. See \"branch.<name>.rebase\" for setting this on a\n     + \tper-branch basis.\n     +@@ Documentation/config/pull.adoc: pull.octopus::\n     + \tat once.\n     + \n     + pull.autoStash::\n     +-\tWhen set to true, automatically create a temporary stash entry\n     ++\tWhen set to `true`, automatically create a temporary stash entry\n     + \tto record the local changes before the operation begins, and\n     + \trestore them after the operation completes.  When your \"git\n     + \tpull\" rebases (instead of merges), this may be convenient, since\n     +\n     + ## Documentation/config/push.adoc ##\n     +@@ Documentation/config/push.adoc: new default).\n     + --\n     + \n     + `push.followTags`::\n     +-\tIf set to true, enable `--follow-tags` option by default.  You\n     ++\tIf set to `true`, enable `--follow-tags` option by default.  You\n     + \tmay override this configuration at time of push by specifying\n     + \t`--no-follow-tags`.\n     + \n     +\n       ## Documentation/config/rebase.adoc ##\n      @@ Documentation/config/rebase.adoc: rebase.stat::\n       \trebase. False by default.\n     @@ Documentation/config/rebase.adoc: rebase.rescheduleFailedExec::\n       \tcommand line, with or without an argument, overrides any\n       \t`rebase.rebaseMerges` configuration.\n      \n     + ## Documentation/config/receive.adoc ##\n     +@@\n     + receive.advertiseAtomic::\n     + \tBy default, git-receive-pack will advertise the atomic push\n     + \tcapability to its clients. If you don't want to advertise this\n     +-\tcapability, set this variable to false.\n     ++\tcapability, set this variable to `false`.\n     + \n     + receive.advertisePushOptions::\n     +-\tWhen set to true, git-receive-pack will advertise the push options\n     ++\tWhen set to `true`, git-receive-pack will advertise the push options\n     + \tcapability to its clients. False by default.\n     + \n     + receive.autogc::\n     + \tBy default, git-receive-pack will run \"git maintenance run --auto\" after\n     + \treceiving data from git-push and updating refs.  You can stop\n     +-\tit by setting this variable to false.\n     ++\tit by setting this variable to `false`.\n     + \n     + receive.certNonceSeed::\n     + \tBy setting this variable to a string, `git receive-pack`\n     +@@ Documentation/config/receive.adoc: receive.certNonceSlop::\n     + \tcan check `GIT_PUSH_CERT_NONCE_STATUS` is `OK`.\n     + \n     + receive.fsckObjects::\n     +-\tIf it is set to true, git-receive-pack will check all received\n     ++\tIf it is set to `true`, git-receive-pack will check all received\n     + \tobjects. See `transfer.fsckObjects` for what's checked.\n     +-\tDefaults to false. If not set, the value of\n     ++\tDefaults to `false`. If not set, the value of\n     + \t`transfer.fsckObjects` is used instead.\n     + \n     + receive.fsck.<msg-id>::\n     +@@ Documentation/config/receive.adoc: receive.maxInputSize::\n     + \tis unlimited.\n     + \n     + receive.denyDeletes::\n     +-\tIf set to true, git-receive-pack will deny a ref update that deletes\n     ++\tIf set to `true`, git-receive-pack will deny a ref update that deletes\n     + \tthe ref. Use this to prevent such a ref deletion via a push.\n     + \n     + receive.denyDeleteCurrent::\n     +-\tIf set to true, git-receive-pack will deny a ref update that\n     ++\tIf set to `true`, git-receive-pack will deny a ref update that\n     + \tdeletes the currently checked out branch of a non-bare repository.\n     + \n     + receive.denyCurrentBranch::\n     +-\tIf set to true or \"refuse\", git-receive-pack will deny a ref update\n     ++\tIf set to `true` or \"refuse\", git-receive-pack will deny a ref update\n     + \tto the currently checked out branch of a non-bare repository.\n     + \tSuch a push is potentially dangerous because it brings the HEAD\n     + \tout of sync with the index and working tree. If set to \"warn\",\n     + \tprint a warning of such a push to stderr, but allow the push to\n     +-\tproceed. If set to false or \"ignore\", allow such pushes with no\n     ++\tproceed. If set to `false` or \"ignore\", allow such pushes with no\n     + \tmessage. Defaults to \"refuse\".\n     + +\n     + Another option is \"updateInstead\" which will update the working\n     +@@ Documentation/config/receive.adoc: the index have any difference from the HEAD, but the `push-to-checkout`\n     + hook can be used to customize this.  See linkgit:githooks[5].\n     + \n     + receive.denyNonFastForwards::\n     +-\tIf set to true, git-receive-pack will deny a ref update which is\n     ++\tIf set to `true`, git-receive-pack will deny a ref update which is\n     + \tnot a fast-forward. Use this to prevent such an update via a push,\n     + \teven if that push is forced. This configuration variable is\n     + \tset when initializing a shared repository.\n     +@@ Documentation/config/receive.adoc: E.g.:\n     + \tgit config --system --add receive.procReceiveRefs !:refs/heads\n     + \n     + receive.updateServerInfo::\n     +-\tIf set to true, git-receive-pack will run git-update-server-info\n     ++\tIf set to `true`, git-receive-pack will run git-update-server-info\n     + \tafter receiving data from git-push and updating refs.\n     + \n     + receive.shallowUpdate::\n     +-\tIf set to true, .git/shallow can be updated when new refs\n     ++\tIf set to `true`, .git/shallow can be updated when new refs\n     + \trequire new shallow roots. Otherwise those refs are rejected.\n     +\n     + ## Documentation/config/remote.adoc ##\n     +@@ Documentation/config/remote.adoc: remote.<name>.push::\n     + \tlinkgit:git-push[1].\n     + \n     + remote.<name>.mirror::\n     +-\tIf true, pushing to this remote will automatically behave\n     ++\tIf `true`, pushing to this remote will automatically behave\n     + \tas if the `--mirror` option was given on the command line.\n     + \n     + remote.<name>.skipDefaultUpdate::\n     +@@ Documentation/config/remote.adoc: remote.<name>.skipDefaultUpdate::\n     + \tvalues, the value of the last occurrence will be used).\n     + \n     + remote.<name>.skipFetchAll::\n     +-\tIf true, this remote will be skipped when updating\n     ++\tIf `true`, this remote will be skipped when updating\n     + \tusing linkgit:git-fetch[1], the `update` subcommand of\n     + \tlinkgit:git-remote[1], and ignored by the prefetch task\n     + \tof `git maintenance`.\n     +@@ Documentation/config/remote.adoc: remote.<name>.vcs::\n     + \tthe remote with the git-remote-<vcs> helper.\n     + \n     + remote.<name>.prune::\n     +-\tWhen set to true, fetching from this remote by default will also\n     ++\tWhen set to `true`, fetching from this remote by default will also\n     + \tremove any remote-tracking references that no longer exist on the\n     + \tremote (as if the `--prune` option was given on the command line).\n     + \tOverrides `fetch.prune` settings, if any.\n     + \n     + remote.<name>.pruneTags::\n     +-\tWhen set to true, fetching from this remote by default will also\n     ++\tWhen set to `true`, fetching from this remote by default will also\n     + \tremove any local tags that no longer exist on the remote if pruning\n     + \tis activated in general via `remote.<name>.prune`, `fetch.prune` or\n     + \t`--prune`. Overrides `fetch.pruneTags` settings, if any.\n     +@@ Documentation/config/remote.adoc: See also `remote.<name>.prune` and the PRUNING section of\n     + linkgit:git-fetch[1].\n     + \n     + remote.<name>.promisor::\n     +-\tWhen set to true, this remote will be used to fetch promisor\n     ++\tWhen set to `true`, this remote will be used to fetch promisor\n     + \tobjects.\n     + \n     + remote.<name>.partialclonefilter::\n     +\n     + ## Documentation/config/repack.adoc ##\n     +@@ Documentation/config/repack.adoc: repack.useDeltaBaseOffset::\n     + \tnative protocol are unaffected by this option.\n     + \n     + repack.packKeptObjects::\n     +-\tIf set to true, makes `git repack` act as if\n     ++\tIf set to `true`, makes `git repack` act as if\n     + \t`--pack-kept-objects` was passed. See linkgit:git-repack[1] for\n     + \tdetails. Defaults to `false` normally, but `true` if a bitmap\n     + \tindex is being written (either via `--write-bitmap-index` or\n     + \t`repack.writeBitmaps`).\n     + \n     + repack.useDeltaIslands::\n     +-\tIf set to true, makes `git repack` act as if `--delta-islands`\n     ++\tIf set to `true`, makes `git repack` act as if `--delta-islands`\n     + \twas passed. Defaults to `false`.\n     + \n     + repack.writeBitmaps::\n     +-\tWhen true, git will write a bitmap index when packing all\n     ++\tWhen `true`, git will write a bitmap index when packing all\n     + \tobjects to disk (e.g., when `git repack -a` is run).  This\n     + \tindex can speed up the \"counting objects\" phase of subsequent\n     + \tpacks created for clones and fetches, at the cost of some disk\n     + \tspace and extra time spent on the initial repack.  This has\n     + \tno effect if multiple packfiles are created.\n     +-\tDefaults to true on bare repos, false otherwise.\n     ++\tDefaults to `true` on bare repos, `false` otherwise.\n     + \n     + repack.updateServerInfo::\n     +-\tIf set to false, linkgit:git-repack[1] will not run\n     +-\tlinkgit:git-update-server-info[1]. Defaults to true. Can be overridden\n     +-\twhen true by the `-n` option of linkgit:git-repack[1].\n     ++\tIf set to `false`, linkgit:git-repack[1] will not run\n     ++\tlinkgit:git-update-server-info[1]. Defaults to `true`. Can be overridden\n     ++\twhen `true` by the `-n` option of linkgit:git-repack[1].\n     + \n     + repack.cruftWindow::\n     + repack.cruftWindowMemory::\n     +@@ Documentation/config/repack.adoc: repack.cruftThreads::\n     + \tvariables for defaults and meaning.\n     + \n     + repack.midxMustContainCruft::\n     +-\tWhen set to true, linkgit:git-repack[1] will unconditionally include\n     ++\tWhen set to `true`, linkgit:git-repack[1] will unconditionally include\n     + \tcruft pack(s), if any, in the multi-pack index when invoked with\n     +-\t`--write-midx`. When false, cruft packs are only included in the MIDX\n     ++\t`--write-midx`. When `false`, cruft packs are only included in the MIDX\n     + \twhen necessary (e.g., because they might be required to form a\n     +-\treachability closure with MIDX bitmaps). Defaults to true.\n     ++\treachability closure with MIDX bitmaps). Defaults to `true`.\n     +\n       ## Documentation/config/rerere.adoc ##\n      @@\n       rerere.autoUpdate::\n     @@ Documentation/config/rerere.adoc\n       rerere.enabled::\n       \tActivate recording of resolved conflicts, so that identical\n      \n     + ## Documentation/config/revert.adoc ##\n     +@@\n     + revert.reference::\n     +-\tSetting this variable to true makes `git revert` behave\n     ++\tSetting this variable to `true` makes `git revert` behave\n     + \tas if the `--reference` option is given.\n     +\n       ## Documentation/config/stash.adoc ##\n      @@ Documentation/config/stash.adoc: ifdef::git-stash[]\n       endif::git-stash[]\n     @@ Documentation/config/status.adoc: This variable can be overridden with the -u|--\n       \tunlimited number), the submodule summary will be enabled and a\n       \tsummary of commits for modified submodules will be shown (see\n       \t--summary-limit option of linkgit:git-submodule[1]). Please note\n     +\n     + ## Documentation/config/submodule.adoc ##\n     +@@ Documentation/config/submodule.adoc: submodule.active::\n     + \n     + submodule.recurse::\n     + \tA boolean indicating if commands should enable the `--recurse-submodules`\n     +-\toption by default. Defaults to false.\n     ++\toption by default. Defaults to `false`.\n     + +\n     +-When set to true, it can be deactivated via the\n     ++When set to `true`, it can be deactivated via the\n     + `--no-recurse-submodules` option. Note that some Git commands\n     + lacking this option may call some of the above commands affected by\n     + `submodule.recurse`; for instance `git remote update` will call\n     +@@ Documentation/config/submodule.adoc: submodule.propagateBranches::\n     + \tEnabling this will allow certain commands to accept\n     + \t`--recurse-submodules` and certain commands that already accept\n     + \t`--recurse-submodules` will now consider branches.\n     +-\tDefaults to false.\n     ++\tDefaults to `false`.\n     + \n     + submodule.fetchJobs::\n     + \tSpecifies how many submodules are fetched/cloned at the same time.\n     +\n     + ## Documentation/config/trace2.adoc ##\n     +@@ Documentation/config/trace2.adoc: trace2.eventTarget::\n     + include::../trace2-target-values.adoc[]\n     + \n     + trace2.normalBrief::\n     +-\tBoolean.  When true `time`, `filename`, and `line` fields are\n     ++\tBoolean.  When `true` `time`, `filename`, and `line` fields are\n     + \tomitted from normal output.  May be overridden by the\n     +-\t`GIT_TRACE2_BRIEF` environment variable.  Defaults to false.\n     ++\t`GIT_TRACE2_BRIEF` environment variable.  Defaults to `false`.\n     + \n     + trace2.perfBrief::\n     +-\tBoolean.  When true `time`, `filename`, and `line` fields are\n     ++\tBoolean.  When `true` `time`, `filename`, and `line` fields are\n     + \tomitted from PERF output.  May be overridden by the\n     +-\t`GIT_TRACE2_PERF_BRIEF` environment variable.  Defaults to false.\n     ++\t`GIT_TRACE2_PERF_BRIEF` environment variable.  Defaults to `false`.\n     + \n     + trace2.eventBrief::\n     +-\tBoolean.  When true `time`, `filename`, and `line` fields are\n     ++\tBoolean.  When `true` `time`, `filename`, and `line` fields are\n     + \tomitted from event output.  May be overridden by the\n     +-\t`GIT_TRACE2_EVENT_BRIEF` environment variable.  Defaults to false.\n     ++\t`GIT_TRACE2_EVENT_BRIEF` environment variable.  Defaults to `false`.\n     + \n     + trace2.eventNesting::\n     + \tInteger.  Specifies desired depth of nested regions in the\n     +@@ Documentation/config/trace2.adoc: trace2.envVars::\n     + \tdefault.\n     + \n     + trace2.destinationDebug::\n     +-\tBoolean.  When true Git will print error messages when a\n     ++\tBoolean.  When `true` Git will print error messages when a\n     + \ttrace target destination cannot be opened for writing.\n     + \tBy default, these errors are suppressed and tracing is\n     + \tsilently disabled.  May be overridden by the\n     +\n     + ## Documentation/config/transfer.adoc ##\n     +@@ Documentation/config/transfer.adoc: data in git's configuration files. If you do want to use this, set\n     + transfer.fsckObjects::\n     + \tWhen `fetch.fsckObjects` or `receive.fsckObjects` are\n     + \tnot set, the value of this variable is used instead.\n     +-\tDefaults to false.\n     ++\tDefaults to `false`.\n     + +\n     + When set, the fetch or receive will abort in the case of a malformed\n     + object or a link to a nonexistent object. In addition, various other\n     +@@ Documentation/config/transfer.adoc: transfer.unpackLimit::\n     + \tThe default value is 100.\n     + \n     + transfer.advertiseSID::\n     +-\tBoolean. When true, client and server processes will advertise their\n     +-\tunique session IDs to their remote counterpart. Defaults to false.\n     ++\tBoolean. When `true`, client and server processes will advertise their\n     ++\tunique session IDs to their remote counterpart. Defaults to `false`.\n     + \n     + transfer.bundleURI::\n     + \tWhen `true`, local `git clone` commands will request bundle\n     +@@ Documentation/config/transfer.adoc: transfer.bundleURI::\n     + \n     + transfer.advertiseObjectInfo::\n     + \tWhen `true`, the `object-info` capability is advertised by\n     +-\tservers. Defaults to false.\n     ++\tservers. Defaults to `false`.\n     +\n     + ## Documentation/config/uploadarchive.adoc ##\n     +@@\n     + uploadarchive.allowUnreachable::\n     +-\tIf true, allow clients to use `git archive --remote` to request\n     ++\tIf `true`, allow clients to use `git archive --remote` to request\n     + \tany tree, whether reachable from the ref tips or not. See the\n     + \tdiscussion in the \"SECURITY\" section of\n     + \tlinkgit:git-upload-archive[1] for more details. Defaults to\n     +\n     + ## Documentation/config/worktree.adoc ##\n     +@@\n     + \tIf no branch is specified and neither `-b` nor `-B` nor\n     + \t`--detach` is used, then `git worktree add` defaults to\n     + \tcreating a new branch from HEAD.  If `worktree.guessRemote` is\n     +-\tset to true, `worktree add` tries to find a remote-tracking\n     ++\tset to `true`, `worktree add` tries to find a remote-tracking\n     + \tbranch whose name uniquely matches the new branch name.  If\n     + \tsuch a branch exists, it is checked out and set as \"upstream\"\n     + \tfor the new branch.  If no such match can be found, it falls\n\n\n Documentation/config/am.adoc            |  4 +-\n Documentation/config/blame.adoc         |  6 +--\n Documentation/config/branch.adoc        | 10 ++--\n Documentation/config/clean.adoc         |  2 +-\n Documentation/config/color.adoc         |  2 +-\n Documentation/config/commitgraph.adoc   |  8 +--\n Documentation/config/core.adoc          | 72 ++++++++++++-------------\n Documentation/config/credential.adoc    |  2 +-\n Documentation/config/fetch.adoc         | 14 ++---\n Documentation/config/fmt-merge-msg.adoc |  6 +--\n Documentation/config/format.adoc        | 22 ++++----\n Documentation/config/gc.adoc            |  6 +--\n Documentation/config/gitcvs.adoc        |  4 +-\n Documentation/config/grep.adoc          | 12 ++---\n Documentation/config/gui.adoc           |  2 +-\n Documentation/config/http.adoc          |  8 +--\n Documentation/config/instaweb.adoc      |  2 +-\n Documentation/config/interactive.adoc   |  2 +-\n Documentation/config/log.adoc           |  6 +--\n Documentation/config/mailinfo.adoc      |  2 +-\n Documentation/config/maintenance.adoc   |  6 +--\n Documentation/config/merge.adoc         |  4 +-\n Documentation/config/mergetool.adoc     |  2 +-\n Documentation/config/pack.adoc          | 30 +++++------\n Documentation/config/pull.adoc          |  4 +-\n Documentation/config/push.adoc          |  2 +-\n Documentation/config/rebase.adoc        | 18 +++----\n Documentation/config/receive.adoc       | 24 ++++-----\n Documentation/config/remote.adoc        | 10 ++--\n Documentation/config/repack.adoc        | 20 +++----\n Documentation/config/rerere.adoc        |  4 +-\n Documentation/config/revert.adoc        |  2 +-\n Documentation/config/stash.adoc         | 16 +++---\n Documentation/config/status.adoc        | 20 +++----\n Documentation/config/submodule.adoc     |  6 +--\n Documentation/config/trace2.adoc        | 14 ++---\n Documentation/config/transfer.adoc      |  8 +--\n Documentation/config/uploadarchive.adoc |  2 +-\n Documentation/config/worktree.adoc      |  2 +-\n 39 files changed, 193 insertions(+), 193 deletions(-)\n\ndiff --git a/Documentation/config/am.adoc b/Documentation/config/am.adoc\nindex 5bcad2efb1..d072613400 100644\n--- a/Documentation/config/am.adoc\n+++ b/Documentation/config/am.adoc\n@@ -1,5 +1,5 @@\n am.keepcr::\n-\tIf true, git-am will call git-mailsplit for patches in mbox format\n+\tIf `true`, git-am will call git-mailsplit for patches in mbox format\n \twith parameter `--keep-cr`. In this case git-mailsplit will\n \tnot remove `\\r` from lines ending with `\\r\\n`. Can be overridden\n \tby giving `--no-keep-cr` from the command line.\n@@ -7,7 +7,7 @@ am.keepcr::\n \n am.threeWay::\n \tBy default, `git am` will fail if the patch does not apply cleanly. When\n-\tset to true, this setting tells `git am` to fall back on 3-way merge if\n+\tset to `true`, this setting tells `git am` to fall back on 3-way merge if\n \tthe patch records the identity of blobs it is supposed to apply to and\n \twe have those blobs available locally (equivalent to giving the `--3way`\n \toption from the command line). Defaults to `false`.\ndiff --git a/Documentation/config/blame.adoc b/Documentation/config/blame.adoc\nindex 4d047c1790..2fc99d7da7 100644\n--- a/Documentation/config/blame.adoc\n+++ b/Documentation/config/blame.adoc\n@@ -1,6 +1,6 @@\n blame.blankBoundary::\n \tShow blank commit object name for boundary commits in\n-\tlinkgit:git-blame[1]. This option defaults to false.\n+\tlinkgit:git-blame[1]. This option defaults to `false`.\n \n blame.coloring::\n \tThis determines the coloring scheme to be applied to blame\n@@ -14,11 +14,11 @@ blame.date::\n \n blame.showEmail::\n \tShow the author email instead of author name in linkgit:git-blame[1].\n-\tThis option defaults to false.\n+\tThis option defaults to `false`.\n \n blame.showRoot::\n \tDo not treat root commits as boundaries in linkgit:git-blame[1].\n-\tThis option defaults to false.\n+\tThis option defaults to `false`.\n \n blame.ignoreRevsFile::\n \tIgnore revisions listed in the file, one unabbreviated object name per\ndiff --git a/Documentation/config/branch.adoc b/Documentation/config/branch.adoc\nindex a4db9fa5c8..e05563efe2 100644\n--- a/Documentation/config/branch.adoc\n+++ b/Documentation/config/branch.adoc\n@@ -20,10 +20,10 @@\n \tthat tracks another branch, this variable tells Git to set\n \tup pull to rebase instead of merge (see `branch.<name>.rebase`).\n \tThe valid settings are:\n-`never`;; rebase is never automatically set to true.\n-`local`;; rebase is set to true for tracked branches of other local branches.\n-`remote`;; rebase is set to true for tracked branches of remote-tracking branches.\n-`always`;; rebase will be set to true for all tracking branches.\n+`never`;; rebase is never automatically set to `true`.\n+`local`;; rebase is set to `true` for tracked branches of other local branches.\n+`remote`;; rebase is set to `true` for tracked branches of remote-tracking branches.\n+`always`;; rebase will be set to `true` for all tracking branches.\n \n +\n See `branch.autoSetupMerge` for details on how to set up a branch to track another branch.\n@@ -81,7 +81,7 @@ This option defaults to `never`.\n \tsupported.\n \n `branch.<name>.rebase`::\n-\tWhen true, rebase the branch _<name>_ on top of the fetched branch,\n+\tWhen `true`, rebase the branch _<name>_ on top of the fetched branch,\n \tinstead of merging the default branch from the default remote when\n \t`git pull` is run. See `pull.rebase` for doing this in a non\n \tbranch-specific manner.\ndiff --git a/Documentation/config/clean.adoc b/Documentation/config/clean.adoc\nindex c0188ead4e..095945d508 100644\n--- a/Documentation/config/clean.adoc\n+++ b/Documentation/config/clean.adoc\n@@ -1,3 +1,3 @@\n clean.requireForce::\n \tA boolean to make git-clean refuse to delete files unless -f\n-\tis given. Defaults to true.\n+\tis given. Defaults to `true`.\ndiff --git a/Documentation/config/color.adoc b/Documentation/config/color.adoc\nindex 2f2275ac69..9a0cc992ca 100644\n--- a/Documentation/config/color.adoc\n+++ b/Documentation/config/color.adoc\n@@ -132,7 +132,7 @@ color.interactive.<slot>::\n \n color.pager::\n \tA boolean to specify whether `auto` color modes should colorize\n-\toutput going to the pager. Defaults to true; set this to false\n+\toutput going to the pager. Defaults to `true`; set this to `false`\n \tif your pager does not understand ANSI color codes.\n \n color.push::\ndiff --git a/Documentation/config/commitgraph.adoc b/Documentation/config/commitgraph.adoc\nindex 70a56c53d2..1c33e08141 100644\n--- a/Documentation/config/commitgraph.adoc\n+++ b/Documentation/config/commitgraph.adoc\n@@ -9,9 +9,9 @@ commitGraph.maxNewFilters::\n \tcommit-graph write` (c.f., linkgit:git-commit-graph[1]).\n \n commitGraph.changedPaths::\n-\tIf true, then `git commit-graph write` will compute and write\n+\tIf `true`, then `git commit-graph write` will compute and write\n \tchanged-path Bloom filters by default, equivalent to passing\n-\t`--changed-paths`. If false or unset, changed-paths Bloom filters will\n+\t`--changed-paths`. If `false` or unset, changed-paths Bloom filters will\n \tbe written during `git commit-graph write` only if the filters already\n \texist in the current commit-graph file. This matches the default\n \tbehavior of `git commit-graph write` without any `--[no-]changed-paths`\n@@ -20,8 +20,8 @@ commitGraph.changedPaths::\n \talways takes precedence over this configuration. Defaults to unset.\n \n commitGraph.readChangedPaths::\n-\tDeprecated. Equivalent to commitGraph.changedPathsVersion=-1 if true, and\n-\tcommitGraph.changedPathsVersion=0 if false. (If commitGraph.changedPathVersion\n+\tDeprecated. Equivalent to commitGraph.changedPathsVersion=-1 if `true`, and\n+\tcommitGraph.changedPathsVersion=0 if `false`. (If commitGraph.changedPathVersion\n \tis also set, commitGraph.changedPathsVersion takes precedence.)\n \n commitGraph.changedPathsVersion::\ndiff --git a/Documentation/config/core.adoc b/Documentation/config/core.adoc\nindex a0ebf03e2e..a04b9d39f8 100644\n--- a/Documentation/config/core.adoc\n+++ b/Documentation/config/core.adoc\n@@ -18,10 +18,10 @@ Git for Windows or Eclipse).\n In such a case it may be necessary to set this variable to 'false'.\n See linkgit:git-update-index[1].\n +\n-The default is true (when core.filemode is not specified in the config file).\n+The default is `true` (when core.filemode is not specified in the config file).\n \n core.hideDotFiles::\n-\t(Windows-only) If true, mark newly-created directories and files whose\n+\t(Windows-only) If `true`, mark newly-created directories and files whose\n \tname starts with a dot as hidden.  If 'dotGitOnly', only the `.git/`\n \tdirectory is hidden, but no other files starting with a dot.  The\n \tdefault mode is 'dotGitOnly'.\n@@ -34,8 +34,8 @@ core.ignoreCase::\n \tit is really the same file, and continue to remember it as\n \t\"Makefile\".\n +\n-The default is false, except linkgit:git-clone[1] or linkgit:git-init[1]\n-will probe and set core.ignoreCase true if appropriate when the repository\n+The default is `false`, except linkgit:git-clone[1] or linkgit:git-init[1]\n+will probe and set core.ignoreCase `true` if appropriate when the repository\n is created.\n +\n Git relies on the proper configuration of this variable for your operating\n@@ -43,26 +43,26 @@ and file system. Modifying this value may result in unexpected behavior.\n \n core.precomposeUnicode::\n \tThis option is only used by Mac OS implementation of Git.\n-\tWhen core.precomposeUnicode=true, Git reverts the unicode decomposition\n+\tWhen core.precomposeUnicode=`true`, Git reverts the unicode decomposition\n \tof filenames done by Mac OS. This is useful when sharing a repository\n \tbetween Mac OS and Linux or Windows.\n \t(Git for Windows 1.7.10 or higher is needed, or Git under cygwin 1.7).\n-\tWhen false, file names are handled fully transparent by Git,\n+\tWhen `false`, file names are handled fully transparent by Git,\n \twhich is backward compatible with older versions of Git.\n \n core.protectHFS::\n-\tIf set to true, do not allow checkout of paths that would\n+\tIf set to `true`, do not allow checkout of paths that would\n \tbe considered equivalent to `.git` on an HFS+ filesystem.\n \tDefaults to `true` on Mac OS, and `false` elsewhere.\n \n core.protectNTFS::\n-\tIf set to true, do not allow checkout of paths that would\n+\tIf set to `true`, do not allow checkout of paths that would\n \tcause problems with the NTFS filesystem, e.g. conflict with\n \t8.3 \"short\" names.\n \tDefaults to `true` on Windows, and `false` elsewhere.\n \n core.fsmonitor::\n-\tIf set to true, enable the built-in file system monitor\n+\tIf set to `true`, enable the built-in file system monitor\n \tdaemon for this working directory (linkgit:git-fsmonitor{litdd}daemon[1]).\n +\n Like hook-based file system monitors, the built-in file system monitor\n@@ -112,15 +112,15 @@ something that can be used to determine what files have changed\n without race conditions.\n \n core.trustctime::\n-\tIf false, the ctime differences between the index and the\n+\tIf `false`, the ctime differences between the index and the\n \tworking tree are ignored; useful when the inode change time\n \tis regularly modified by something outside Git (file system\n \tcrawlers and some backup systems).\n-\tSee linkgit:git-update-index[1]. True by default.\n+\tSee linkgit:git-update-index[1]. `True` by default.\n \n core.splitIndex::\n-\tIf true, the split-index feature of the index will be used.\n-\tSee linkgit:git-update-index[1]. False by default.\n+\tIf `true`, the split-index feature of the index will be used.\n+\tSee linkgit:git-update-index[1]. `False` by default.\n \n core.untrackedCache::\n \tDetermines what to do about the untracked cache feature of the\n@@ -156,13 +156,13 @@ core.quotePath::\n \tbackslashes in the same way C escapes control characters (e.g.\n \t`\\t` for TAB, `\\n` for LF, `\\\\` for backslash) or bytes with\n \tvalues larger than 0x80 (e.g. octal `\\302\\265` for \"micro\" in\n-\tUTF-8).  If this variable is set to false, bytes higher than\n+\tUTF-8).  If this variable is set to `false`, bytes higher than\n \t0x80 are not considered \"unusual\" any more. Double-quotes,\n \tbackslash and control characters are always escaped regardless\n \tof the setting of this variable.  A simple space character is\n \tnot considered \"unusual\".  Many commands can output pathnames\n \tcompletely verbatim using the `-z` option. The default value\n-\tis true.\n+\tis `true`.\n \n core.eol::\n \tSets the line ending type to use in the working directory for\n@@ -176,7 +176,7 @@ core.eol::\n \tis set to `true` or `input`.\n \n core.safecrlf::\n-\tIf true, makes Git check if converting `CRLF` is reversible when\n+\tIf `true`, makes Git check if converting `CRLF` is reversible when\n \tend-of-line conversion is active.  Git will verify if a command\n \tmodifies a file in the work tree either directly or indirectly.\n \tFor example, committing a file followed by checking out the\n@@ -223,7 +223,7 @@ mechanism.\n core.autocrlf::\n \tSetting this variable to \"true\" is the same as setting\n \tthe `text` attribute to \"auto\" on all files and core.eol to \"crlf\".\n-\tSet to true if you want to have `CRLF` line endings in your\n+\tSet to `true` if you want to have `CRLF` line endings in your\n \tworking directory and the repository has LF line endings.\n \tThis variable can be set to 'input',\n \tin which case no output conversion is performed.\n@@ -235,14 +235,14 @@ core.checkRoundtripEncoding::\n \tThe default value is `SHIFT-JIS`.\n \n core.symlinks::\n-\tIf false, symbolic links are checked out as small plain files that\n+\tIf `false`, symbolic links are checked out as small plain files that\n \tcontain the link text. linkgit:git-update-index[1] and\n \tlinkgit:git-add[1] will not change the recorded type to regular\n \tfile. Useful on filesystems like FAT that do not support\n \tsymbolic links.\n +\n-The default is true, except linkgit:git-clone[1] or linkgit:git-init[1]\n-will probe and set core.symlinks false if appropriate when the repository\n+The default is `true`, except linkgit:git-clone[1] or linkgit:git-init[1]\n+will probe and set core.symlinks `false` if appropriate when the repository\n is created.\n \n core.gitProxy::\n@@ -271,7 +271,7 @@ core.sshCommand::\n \twhen the environment variable is set.\n \n core.ignoreStat::\n-\tIf true, Git will avoid using lstat() calls to detect if files have\n+\tIf `true`, Git will avoid using lstat() calls to detect if files have\n \tchanged by setting the \"assume-unchanged\" bit for those tracked files\n \twhich it has updated identically in both the index and working tree.\n +\n@@ -283,7 +283,7 @@ Git will not normally detect changes to those files.\n This is useful on systems where lstat() calls are very slow, such as\n CIFS/Microsoft Windows.\n +\n-False by default.\n+`False` by default.\n \n core.preferSymlinkRefs::\n \tInstead of the default \"symref\" format for HEAD\n@@ -313,7 +313,7 @@ core.alternateRefsPrefixes::\n \t`core.alternateRefsPrefixes` has no effect.\n \n core.bare::\n-\tIf true this repository is assumed to be 'bare' and has no\n+\tIf `true` this repository is assumed to be 'bare' and has no\n \tworking directory associated with it.  If this is the case a\n \tnumber of commands that require a working directory will be\n \tdisabled, such as linkgit:git-add[1] or linkgit:git-merge[1].\n@@ -321,8 +321,8 @@ core.bare::\n This setting is automatically guessed by linkgit:git-clone[1] or\n linkgit:git-init[1] when the repository was created.  By default a\n repository that ends in \"/.git\" is assumed to be not bare (bare =\n-false), while all other repositories are assumed to be bare (bare\n-= true).\n+`false`), while all other repositories are assumed to be bare (bare\n+= `true`).\n \n core.worktree::\n \tSet the path to the root of the working tree.\n@@ -349,7 +349,7 @@ read-only snapshot of the same index to a location different from the\n repository's usual working tree).\n \n core.lockfilePid::\n-\tIf true, Git will create a PID file alongside lock files. When a\n+\tIf `true`, Git will create a PID file alongside lock files. When a\n \tlock acquisition fails and a PID file exists, Git can provide\n \tadditional diagnostic information about the process holding the\n \tlock, including whether it is still running. Defaults to `false`.\n@@ -374,8 +374,8 @@ core.logAllRefUpdates::\n This information can be used to determine what commit\n was the tip of a branch \"2 days ago\".\n +\n-This value is true by default in a repository that has\n-a working directory associated with it, and false by\n+This value is `true` by default in a repository that has\n+a working directory associated with it, and `false` by\n default in a bare repository.\n \n core.repositoryFormatVersion::\n@@ -395,11 +395,11 @@ core.sharedRepository::\n \tthe repo read/write-able for the owner and group, but inaccessible to\n \tothers (equivalent to 'group' unless umask is e.g. '0022'). '0640' is a\n \trepository that is group-readable but not group-writable.\n-\tSee linkgit:git-init[1]. False by default.\n+\tSee linkgit:git-init[1]. `False` by default.\n \n core.warnAmbiguousRefs::\n-\tIf true, Git will warn you if the ref name you passed it is ambiguous\n-\tand might match multiple refs in the repository. True by default.\n+\tIf `true`, Git will warn you if the ref name you passed it is ambiguous\n+\tand might match multiple refs in the repository. `True` by default.\n \n core.compression::\n \tAn integer -1..9, indicating a default compression level.\n@@ -708,7 +708,7 @@ core.fsyncObjectFiles::\n \tThis setting is deprecated. Use core.fsync instead.\n +\n This setting affects data added to the Git repository in loose-object\n-form. When set to true, Git will issue an fsync or similar system call\n+form. When set to `true`, Git will issue an fsync or similar system call\n to flush caches so that loose-objects remain consistent in the face\n of a unclean system shutdown.\n \n@@ -719,7 +719,7 @@ This can speed up operations like 'git diff' and 'git status' especially\n on filesystems like NFS that have weak caching semantics and thus\n relatively high IO latencies.  When enabled, Git will do the\n index comparison to the filesystem data in parallel, allowing\n-overlapping IO's.  Defaults to true.\n+overlapping IO's.  Defaults to `true`.\n \n core.unsetenvvars::\n \tWindows-only: comma-separated list of environment variables'\n@@ -746,8 +746,8 @@ This setting defaults to \"refs/notes/commits\", and it can be overridden by\n the `GIT_NOTES_REF` environment variable.  See linkgit:git-notes[1].\n \n core.commitGraph::\n-\tIf true, then git will read the commit-graph file (if it exists)\n-\tto parse the graph structure of commits. Defaults to true. See\n+\tIf `true`, then git will read the commit-graph file (if it exists)\n+\tto parse the graph structure of commits. Defaults to `true`. See\n \tlinkgit:git-commit-graph[1] for more information.\n \n core.useReplaceRefs::\n@@ -758,7 +758,7 @@ core.useReplaceRefs::\n core.multiPackIndex::\n \tUse the multi-pack-index file to track multiple packfiles using a\n \tsingle index. See linkgit:git-multi-pack-index[1] for more\n-\tinformation. Defaults to true.\n+\tinformation. Defaults to `true`.\n \n core.sparseCheckout::\n \tEnable \"sparse checkout\" feature. See linkgit:git-sparse-checkout[1]\ndiff --git a/Documentation/config/credential.adoc b/Documentation/config/credential.adoc\nindex 80a7c77772..0e88c4c7f2 100644\n--- a/Documentation/config/credential.adoc\n+++ b/Documentation/config/credential.adoc\n@@ -19,7 +19,7 @@ credential.interactive::\n \n credential.useHttpPath::\n \tWhen acquiring credentials, consider the \"path\" component of an http\n-\tor https URL to be important. Defaults to false. See\n+\tor https URL to be important. Defaults to `false`. See\n \tlinkgit:gitcredentials[7] for more information.\n \n credential.sanitizePrompt::\ndiff --git a/Documentation/config/fetch.adoc b/Documentation/config/fetch.adoc\nindex cd40db0cad..2b90ed52f2 100644\n--- a/Documentation/config/fetch.adoc\n+++ b/Documentation/config/fetch.adoc\n@@ -3,15 +3,15 @@\n \tin `git pull`) will recursively fetch into populated submodules.\n \tThis option can be set either to a boolean value or to `on-demand`.\n \tSetting it to a boolean changes the behavior of fetch and pull to\n-\trecurse unconditionally into submodules when set to true or to not\n-\trecurse at all when set to false. When set to `on-demand`, fetch and\n+\trecurse unconditionally into submodules when set to `true` or to not\n+\trecurse at all when set to `false`. When set to `on-demand`, fetch and\n \tpull will only recurse into a populated submodule when its\n \tsuperproject retrieves a commit that updates the submodule's\n \treference.\n \tDefaults to `on-demand`, or to the value of `submodule.recurse` if set.\n \n `fetch.fsckObjects`::\n-\tIf it is set to true, git-fetch-pack will check all fetched\n+\tIf it is set to `true`, git-fetch-pack will check all fetched\n \tobjects. See `transfer.fsckObjects` for what's\n \tchecked. Defaults to `false`. If not set, the value of\n \t`transfer.fsckObjects` is used instead.\n@@ -38,12 +38,12 @@\n \t`transfer.unpackLimit` is used instead.\n \n `fetch.prune`::\n-\tIf true, fetch will automatically behave as if the `--prune`\n+\tIf `true`, fetch will automatically behave as if the `--prune`\n \toption was given on the command line.  See also `remote.<name>.prune`\n \tand the PRUNING section of linkgit:git-fetch[1].\n \n `fetch.pruneTags`::\n-\tIf true, fetch will automatically behave as if the\n+\tIf `true`, fetch will automatically behave as if the\n \t`refs/tags/*:refs/tags/*` refspec was provided when pruning,\n \tif not set already. This allows for setting both this option\n \tand `fetch.prune` to maintain a 1=1 mapping to upstream\n@@ -51,7 +51,7 @@\n \tsection of linkgit:git-fetch[1].\n \n `fetch.all`::\n-\tIf true, fetch will attempt to update all available remotes.\n+\tIf `true`, fetch will attempt to update all available remotes.\n \tThis behavior can be overridden by passing `--no-all` or by\n \texplicitly specifying one or more remote(s) to fetch from.\n \tDefaults to `false`.\n@@ -95,7 +95,7 @@ For submodules, this setting can be overridden using the `submodule.fetchJobs`\n config setting.\n \n `fetch.writeCommitGraph`::\n-\tSet to true to write a commit-graph after every `git fetch` command\n+\tSet to `true` to write a commit-graph after every `git fetch` command\n \tthat downloads a pack-file from a remote. Using the `--split` option,\n \tmost executions will create a very small commit-graph file on top of\n \tthe existing commit-graph file(s). Occasionally, these files will\ndiff --git a/Documentation/config/fmt-merge-msg.adoc b/Documentation/config/fmt-merge-msg.adoc\nindex 696ba0531a..4bcf5b2688 100644\n--- a/Documentation/config/fmt-merge-msg.adoc\n+++ b/Documentation/config/fmt-merge-msg.adoc\n@@ -1,13 +1,13 @@\n `merge.branchdesc`::\n \tIn addition to branch names, populate the log message with\n \tthe branch description text associated with them.  Defaults\n-\tto false.\n+\tto `false`.\n \n `merge.log`::\n \tIn addition to branch names, populate the log message with at\n \tmost the specified number of one-line descriptions from the\n-\tactual commits that are being merged.  Defaults to false, and\n-\ttrue is a synonym for 20.\n+\tactual commits that are being merged.  Defaults to `false`, and\n+\t`true` is a synonym for 20.\n \n `merge.suppressDest`::\n \tBy adding a glob that matches the names of integration\ndiff --git a/Documentation/config/format.adoc b/Documentation/config/format.adoc\nindex ab0710e86a..a9736b196a 100644\n--- a/Documentation/config/format.adoc\n+++ b/Documentation/config/format.adoc\n@@ -8,23 +8,23 @@ format.attach::\n \n format.from::\n \tProvides the default value for the `--from` option to format-patch.\n-\tAccepts a boolean value, or a name and email address.  If false,\n+\tAccepts a boolean value, or a name and email address.  If `false`,\n \tformat-patch defaults to `--no-from`, using commit authors directly in\n-\tthe \"From:\" field of patch mails.  If true, format-patch defaults to\n+\tthe \"From:\" field of patch mails.  If `true`, format-patch defaults to\n \t`--from`, using your committer identity in the \"From:\" field of patch\n \tmails and including a \"From:\" field in the body of the patch mail if\n \tdifferent.  If set to a non-boolean value, format-patch uses that\n-\tvalue instead of your committer identity.  Defaults to false.\n+\tvalue instead of your committer identity.  Defaults to `false`.\n \n format.forceInBodyFrom::\n \tProvides the default value for the `--[no-]force-in-body-from`\n-\toption to format-patch.  Defaults to false.\n+\toption to format-patch.  Defaults to `false`.\n \n format.numbered::\n \tA boolean which can enable or disable sequence numbers in patch\n \tsubjects.  It defaults to \"auto\" which enables it only if there\n \tis more than one patch.  It can be enabled or disabled for all\n-\tmessages by setting it to \"true\" or \"false\".  See --numbered\n+\tmessages by setting it to `true` or `false`.  See --numbered\n \toption in linkgit:git-format-patch[1].\n \n format.headers::\n@@ -65,7 +65,7 @@ format.suffix::\n format.encodeEmailHeaders::\n \tEncode email headers that have non-ASCII characters with\n \t\"Q-encoding\" (described in RFC 2047) for email transmission.\n-\tDefaults to true.\n+\tDefaults to `true`.\n \n format.pretty::\n ifndef::with-breaking-changes[]\n@@ -85,7 +85,7 @@ format.thread::\n \twhere the head is chosen from the cover letter, the\n \t`--in-reply-to`, and the first patch mail, in this order.\n \t`deep` threading makes every mail a reply to the previous one.\n-\tA true boolean value is the same as `shallow`, and a false\n+\tA `true` boolean value is the same as `shallow`, and a `false`\n \tvalue disables threading.\n \n format.signOff::\n@@ -99,7 +99,7 @@ format.coverLetter::\n \tA boolean that controls whether to generate a cover-letter when\n \tformat-patch is invoked, but in addition can be set to \"auto\", to\n \tgenerate a cover-letter only when there's more than one patch.\n-\tDefault is false.\n+\tDefault is `false`.\n \n format.outputDirectory::\n \tSet a custom directory to store the resulting files instead of the\n@@ -119,11 +119,11 @@ format.useAutoBase::\n format.notes::\n \tProvides the default value for the `--notes` option to\n \tformat-patch. Accepts a boolean value, or a ref which specifies\n-\twhere to get notes. If false, format-patch defaults to\n-\t`--no-notes`. If true, format-patch defaults to `--notes`. If\n+\twhere to get notes. If `false`, format-patch defaults to\n+\t`--no-notes`. If `true`, format-patch defaults to `--notes`. If\n \tset to a non-boolean value, format-patch defaults to\n \t`--notes=<ref>`, where `ref` is the non-boolean value. Defaults\n-\tto false.\n+\tto `false`.\n +\n If one wishes to use the ref `refs/notes/true`, please use that literal\n instead.\ndiff --git a/Documentation/config/gc.adoc b/Documentation/config/gc.adoc\nindex 21d56db279..b63202cfcc 100644\n--- a/Documentation/config/gc.adoc\n+++ b/Documentation/config/gc.adoc\n@@ -40,7 +40,7 @@ use, it'll affect how the auto pack limit works.\n \n gc.autoDetach::\n \tMake `git gc --auto` return immediately and run in the background\n-\tif the system supports it. Default is true. This config variable acts\n+\tif the system supports it. Default is `true`. This config variable acts\n \tas a fallback in case `maintenance.autoDetach` is not set.\n \n gc.bigPackThreshold::\n@@ -61,10 +61,10 @@ will also be excluded (this is the equivalent of running `git gc` with\n `--keep-largest-pack`).\n \n gc.writeCommitGraph::\n-\tIf true, then gc will rewrite the commit-graph file when\n+\tIf `true`, then gc will rewrite the commit-graph file when\n \tlinkgit:git-gc[1] is run. When using `git gc --auto`\n \tthe commit-graph will be updated if housekeeping is\n-\trequired. Default is true. See linkgit:git-commit-graph[1]\n+\trequired. Default is `true`. See linkgit:git-commit-graph[1]\n \tfor details.\n \n gc.logExpiry::\ndiff --git a/Documentation/config/gitcvs.adoc b/Documentation/config/gitcvs.adoc\nindex 31d7be3992..dc5c9b53a1 100644\n--- a/Documentation/config/gitcvs.adoc\n+++ b/Documentation/config/gitcvs.adoc\n@@ -11,7 +11,7 @@ gitcvs.logFile::\n \tvarious stuff. See linkgit:git-cvsserver[1].\n \n gitcvs.usecrlfattr::\n-\tIf true, the server will look up the end-of-line conversion\n+\tIf `true`, the server will look up the end-of-line conversion\n \tattributes for files to determine the `-k` modes to use. If\n \tthe attributes force Git to treat a file as text,\n \tthe `-k` mode will be left blank so CVS clients will\n@@ -23,7 +23,7 @@ gitcvs.usecrlfattr::\n \n gitcvs.allBinary::\n \tThis is used if `gitcvs.usecrlfattr` does not resolve\n-\tthe correct '-kb' mode to use. If true, all\n+\tthe correct '-kb' mode to use. If `true`, all\n \tunresolved files are sent to the client in\n \tmode '-kb'. This causes the client to treat them\n \tas binary files, which suppresses any newline munging it\ndiff --git a/Documentation/config/grep.adoc b/Documentation/config/grep.adoc\nindex 10041f27b0..a446830a5c 100644\n--- a/Documentation/config/grep.adoc\n+++ b/Documentation/config/grep.adoc\n@@ -1,8 +1,8 @@\n grep.lineNumber::\n-\tIf set to true, enable `-n` option by default.\n+\tIf set to `true`, enable `-n` option by default.\n \n grep.column::\n-\tIf set to true, enable the `--column` option by default.\n+\tIf set to `true`, enable the `--column` option by default.\n \n grep.patternType::\n \tSet the default matching behavior. Using a value of 'basic', 'extended',\n@@ -12,7 +12,7 @@ grep.patternType::\n \tbetween 'basic' and 'extended'.\n \n grep.extendedRegexp::\n-\tIf set to true, enable `--extended-regexp` option by default. This\n+\tIf set to `true`, enable `--extended-regexp` option by default. This\n \toption is ignored when the `grep.patternType` option is set to a value\n \tother than 'default'.\n \n@@ -21,8 +21,8 @@ grep.threads::\n \tuse as many threads as the number of logical cores available.\n \n grep.fullName::\n-\tIf set to true, enable `--full-name` option by default.\n+\tIf set to `true`, enable `--full-name` option by default.\n \n grep.fallbackToNoIndex::\n-\tIf set to true, fall back to `git grep --no-index` if `git grep`\n-\tis executed outside of a git repository.  Defaults to false.\n+\tIf set to `true`, fall back to `git grep --no-index` if `git grep`\n+\tis executed outside of a git repository.  Defaults to `false`.\ndiff --git a/Documentation/config/gui.adoc b/Documentation/config/gui.adoc\nindex 1565c0af19..da7f9ef7fe 100644\n--- a/Documentation/config/gui.adoc\n+++ b/Documentation/config/gui.adoc\n@@ -41,7 +41,7 @@ gui.spellingDictionary::\n \toff.\n \n gui.fastCopyBlame::\n-\tIf true, 'git gui blame' uses `-C` instead of `-C -C` for original\n+\tIf `true`, 'git gui blame' uses `-C` instead of `-C -C` for original\n \tlocation detection. It makes blame significantly faster on huge\n \trepositories at the expense of less thorough copy detection.\n \ndiff --git a/Documentation/config/http.adoc b/Documentation/config/http.adoc\nindex 9da5c298cc..c45b386b2a 100644\n--- a/Documentation/config/http.adoc\n+++ b/Documentation/config/http.adoc\n@@ -64,7 +64,7 @@ http.emptyAuth::\n http.proactiveAuth::\n \tAttempt authentication without first making an unauthenticated attempt and\n \treceiving a 401 response. This can be used to ensure that all requests are\n-\tauthenticated. If `http.emptyAuth` is set to true, this value has no effect.\n+\tauthenticated. If `http.emptyAuth` is set to `true`, this value has no effect.\n +\n If the credential helper used specifies an authentication scheme (i.e., via the\n `authtype` field), that value will be used; if a username and password is\n@@ -182,7 +182,7 @@ empty string.\n \n http.sslVerify::\n \tWhether to verify the SSL certificate when fetching or pushing\n-\tover HTTPS. Defaults to true. Can be overridden by the\n+\tover HTTPS. Defaults to `true`. Can be overridden by the\n \t`GIT_SSL_NO_VERIFY` environment variable.\n \n http.sslCert::\n@@ -260,7 +260,7 @@ http.sslTry::\n \twhen connecting via regular FTP protocol. This might be needed\n \tif the FTP server requires it for security reasons or you wish\n \tto connect securely whenever remote FTP server supports it.\n-\tDefault is false since it might trigger certificate verification\n+\tDefault is `false` since it might trigger certificate verification\n \terrors on misconfigured servers.\n \n http.maxRequests::\n@@ -319,7 +319,7 @@ http.noEPSV::\n \tA boolean which disables using of EPSV ftp command by curl.\n \tThis can be helpful with some \"poor\" ftp servers which don't\n \tsupport EPSV mode. Can be overridden by the `GIT_CURL_FTP_NO_EPSV`\n-\tenvironment variable. Default is false (curl will use EPSV).\n+\tenvironment variable. Default is `false` (curl will use EPSV).\n \n http.userAgent::\n \tThe HTTP USER_AGENT string presented to an HTTP server.  The default\ndiff --git a/Documentation/config/instaweb.adoc b/Documentation/config/instaweb.adoc\nindex 50cb2f7d62..5173a8a7db 100644\n--- a/Documentation/config/instaweb.adoc\n+++ b/Documentation/config/instaweb.adoc\n@@ -7,7 +7,7 @@ instaweb.httpd::\n \trepository. See linkgit:git-instaweb[1].\n \n instaweb.local::\n-\tIf true the web server started by linkgit:git-instaweb[1] will\n+\tIf `true` the web server started by linkgit:git-instaweb[1] will\n \tbe bound to the local IP (127.0.0.1).\n \n instaweb.modulePath::\ndiff --git a/Documentation/config/interactive.adoc b/Documentation/config/interactive.adoc\nindex 8b876cb4eb..4baf303df4 100644\n--- a/Documentation/config/interactive.adoc\n+++ b/Documentation/config/interactive.adoc\n@@ -1,5 +1,5 @@\n interactive.singleKey::\n-\tWhen set to true, allow the user to provide one-letter input\n+\tWhen set to `true`, allow the user to provide one-letter input\n \twith a single key (i.e., without hitting the Enter key) in\n \tinteractive commands.  This is currently used by the `--patch`\n \tmode of linkgit:git-add[1], linkgit:git-checkout[1],\ndiff --git a/Documentation/config/log.adoc b/Documentation/config/log.adoc\nindex f20cc25cd7..4c914b0496 100644\n--- a/Documentation/config/log.adoc\n+++ b/Documentation/config/log.adoc\n@@ -61,16 +61,16 @@ This is the same as the `--decorate` option of the `git log`.\n \thistory lines in `git log --graph`.\n \n `log.showRoot`::\n-\tIf true, the initial commit will be shown as a big creation event.\n+\tIf `true`, the initial commit will be shown as a big creation event.\n \tThis is equivalent to a diff against an empty tree.\n \tTools like linkgit:git-log[1] or linkgit:git-whatchanged[1], which\n \tnormally hide the root commit will now show it. True by default.\n \n `log.showSignature`::\n-\tIf true, makes linkgit:git-log[1], linkgit:git-show[1], and\n+\tIf `true`, makes linkgit:git-log[1], linkgit:git-show[1], and\n \tlinkgit:git-whatchanged[1] assume `--show-signature`.\n \n `log.mailmap`::\n-\tIf true, makes linkgit:git-log[1], linkgit:git-show[1], and\n+\tIf `true`, makes linkgit:git-log[1], linkgit:git-show[1], and\n \tlinkgit:git-whatchanged[1] assume `--use-mailmap`, otherwise\n \tassume `--no-use-mailmap`. True by default.\ndiff --git a/Documentation/config/mailinfo.adoc b/Documentation/config/mailinfo.adoc\nindex ec3a5d81f7..e719cb59f9 100644\n--- a/Documentation/config/mailinfo.adoc\n+++ b/Documentation/config/mailinfo.adoc\n@@ -1,5 +1,5 @@\n mailinfo.scissors::\n-\tIf true, makes linkgit:git-mailinfo[1] (and therefore\n+\tIf `true`, makes linkgit:git-mailinfo[1] (and therefore\n \tlinkgit:git-am[1]) act by default as if the --scissors option\n \twas provided on the command-line. When active, this feature\n \tremoves everything from the message body before a scissors\ndiff --git a/Documentation/config/maintenance.adoc b/Documentation/config/maintenance.adoc\nindex d0c38f03fa..fdfb35fb6c 100644\n--- a/Documentation/config/maintenance.adoc\n+++ b/Documentation/config/maintenance.adoc\n@@ -1,7 +1,7 @@\n maintenance.auto::\n \tThis boolean config option controls whether some commands run\n \t`git maintenance run --auto` after doing their normal work. Defaults\n-\tto true.\n+\tto `true`.\n \n maintenance.autoDetach::\n \tMany Git commands trigger automatic maintenance after they have\n@@ -11,7 +11,7 @@ maintenance.autoDetach::\n \tcontinue to run in the background.\n +\n If unset, the value of `gc.autoDetach` is used as a fallback. Defaults\n-to true if both are unset, meaning that the maintenance process will\n+to `true` if both are unset, meaning that the maintenance process will\n detach.\n \n maintenance.strategy::\n@@ -52,7 +52,7 @@ maintenance.<task>.enabled::\n \twith name `<task>` is run when no `--task` option is specified to\n \t`git maintenance run`. These config values are ignored if a\n \t`--task` option exists. By default, only `maintenance.gc.enabled`\n-\tis true.\n+\tis `true`.\n \n maintenance.<task>.schedule::\n \tThis config option controls whether or not the given `<task>` runs\ndiff --git a/Documentation/config/merge.adoc b/Documentation/config/merge.adoc\nindex 15a4c14c38..4eb90fbd88 100644\n--- a/Documentation/config/merge.adoc\n+++ b/Documentation/config/merge.adoc\n@@ -21,7 +21,7 @@\n \tbranches at the remote named by `branch.<current-branch>.remote`\n \tare consulted, and then they are mapped via `remote.<remote>.fetch`\n \tto their corresponding remote-tracking branches, and the tips of\n-\tthese tracking branches are merged. Defaults to true.\n+\tthese tracking branches are merged. Defaults to `true`.\n \n `merge.ff`::\n \tBy default, Git does not create an extra merge commit when merging\n@@ -34,7 +34,7 @@\n \tcommand line).\n \n `merge.verifySignatures`::\n-\tIf true, this is equivalent to the `--verify-signatures` command\n+\tIf `true`, this is equivalent to the `--verify-signatures` command\n \tline option. See linkgit:git-merge[1] for details.\n \n include::fmt-merge-msg.adoc[]\ndiff --git a/Documentation/config/mergetool.adoc b/Documentation/config/mergetool.adoc\nindex 7064f5a462..088edaebc6 100644\n--- a/Documentation/config/mergetool.adoc\n+++ b/Documentation/config/mergetool.adoc\n@@ -21,7 +21,7 @@\n `mergetool.<tool>.trustExitCode`::\n \tFor a custom merge command, specify whether the exit code of\n \tthe merge command can be used to determine whether the merge was\n-\tsuccessful.  If this is not set to true then the merge target file\n+\tsuccessful.  If this is not set to `true` then the merge target file\n \ttimestamp is checked, and the merge is assumed to have been successful\n \tif the file has been updated; otherwise, the user is prompted to\n \tindicate the success of the merge.\ndiff --git a/Documentation/config/pack.adoc b/Documentation/config/pack.adoc\nindex 75402d5579..ae2226b3f7 100644\n--- a/Documentation/config/pack.adoc\n+++ b/Documentation/config/pack.adoc\n@@ -28,7 +28,7 @@ all existing objects. You can force recompression by passing the -F option\n to linkgit:git-repack[1].\n \n pack.allowPackReuse::\n-\tWhen true or \"single\", and when reachability bitmaps are\n+\tWhen `true` or \"single\", and when reachability bitmaps are\n \tenabled, pack-objects will try to send parts of the bitmapped\n \tpackfile verbatim. When \"multi\", and when a multi-pack\n \treachability bitmap is available, pack-objects will try to send\n@@ -37,7 +37,7 @@ pack.allowPackReuse::\n If only a single pack bitmap is available, and `pack.allowPackReuse`\n is set to \"multi\", reuse parts of just the bitmapped packfile. This\n can reduce memory and CPU usage to serve fetches, but might result in\n-sending a slightly larger pack. Defaults to true.\n+sending a slightly larger pack. Defaults to `true`.\n \n pack.island::\n \tAn extended regular expression configuring a set of delta\n@@ -123,13 +123,13 @@ The minimum size allowed is limited to 1 MiB. The default is unlimited.\n Common unit suffixes of 'k', 'm', or 'g' are supported.\n \n pack.useBitmaps::\n-\tWhen true, git will use pack bitmaps (if available) when packing\n+\tWhen `true`, git will use pack bitmaps (if available) when packing\n \tto stdout (e.g., during the server side of a fetch). Defaults to\n-\ttrue. You should not generally need to turn this off unless\n+\t`true`. You should not generally need to turn this off unless\n \tyou are debugging pack bitmaps.\n \n pack.useBitmapBoundaryTraversal::\n-\tWhen true, Git will use an experimental algorithm for computing\n+\tWhen `true`, Git will use an experimental algorithm for computing\n \treachability queries with bitmaps. Instead of building up\n \tcomplete bitmaps for all of the negated tips and then OR-ing\n \tthem together, consider negated tips with existing bitmaps as\n@@ -146,7 +146,7 @@ particularly when there is poor bitmap coverage of the negated side of\n the query.\n \n pack.useSparse::\n-\tWhen true, git will default to using the '--sparse' option in\n+\tWhen `true`, git will default to using the '--sparse' option in\n \t'git pack-objects' when the '--revs' option is present. This\n \talgorithm only walks trees that appear in paths that introduce new\n \tobjects. This can have significant performance benefits when\n@@ -178,34 +178,34 @@ pack.writeBitmaps (deprecated)::\n \tThis is a deprecated synonym for `repack.writeBitmaps`.\n \n pack.writeBitmapHashCache::\n-\tWhen true, git will include a \"hash cache\" section in the bitmap\n+\tWhen `true`, git will include a \"hash cache\" section in the bitmap\n \tindex (if one is written). This cache can be used to feed git's\n \tdelta heuristics, potentially leading to better deltas between\n \tbitmapped and non-bitmapped objects (e.g., when serving a fetch\n \tbetween an older, bitmapped pack and objects that have been\n \tpushed since the last gc). The downside is that it consumes 4\n-\tbytes per object of disk space. Defaults to true.\n+\tbytes per object of disk space. Defaults to `true`.\n +\n When writing a multi-pack reachability bitmap, no new namehashes are\n computed; instead, any namehashes stored in an existing bitmap are\n permuted into their appropriate location when writing a new bitmap.\n \n pack.writeBitmapLookupTable::\n-\tWhen true, Git will include a \"lookup table\" section in the\n+\tWhen `true`, Git will include a \"lookup table\" section in the\n \tbitmap index (if one is written). This table is used to defer\n \tloading individual bitmaps as late as possible. This can be\n \tbeneficial in repositories that have relatively large bitmap\n-\tindexes. Defaults to false.\n+\tindexes. Defaults to `false`.\n \n pack.readReverseIndex::\n-\tWhen true, git will read any .rev file(s) that may be available\n-\t(see: linkgit:gitformat-pack[5]). When false, the reverse index\n+\tWhen `true`, git will read any .rev file(s) that may be available\n+\t(see: linkgit:gitformat-pack[5]). When `false`, the reverse index\n \twill be generated from scratch and stored in memory. Defaults to\n-\ttrue.\n+\t`true`.\n \n pack.writeReverseIndex::\n-\tWhen true, git will write a corresponding .rev file (see:\n+\tWhen `true`, git will write a corresponding .rev file (see:\n \tlinkgit:gitformat-pack[5])\n \tfor each new packfile that it writes in all places except for\n \tlinkgit:git-fast-import[1] and in the bulk checkin mechanism.\n-\tDefaults to true.\n+\tDefaults to `true`.\ndiff --git a/Documentation/config/pull.adoc b/Documentation/config/pull.adoc\nindex 125c930f72..4a7ac40149 100644\n--- a/Documentation/config/pull.adoc\n+++ b/Documentation/config/pull.adoc\n@@ -9,7 +9,7 @@ pull.ff::\n \tcommand line). This setting overrides `merge.ff` when pulling.\n \n pull.rebase::\n-\tWhen true, rebase branches on top of the fetched branch, instead\n+\tWhen `true`, rebase branches on top of the fetched branch, instead\n \tof merging the default branch from the default remote when \"git\n \tpull\" is run. See \"branch.<name>.rebase\" for setting this on a\n \tper-branch basis.\n@@ -30,7 +30,7 @@ pull.octopus::\n \tat once.\n \n pull.autoStash::\n-\tWhen set to true, automatically create a temporary stash entry\n+\tWhen set to `true`, automatically create a temporary stash entry\n \tto record the local changes before the operation begins, and\n \trestore them after the operation completes.  When your \"git\n \tpull\" rebases (instead of merges), this may be convenient, since\ndiff --git a/Documentation/config/push.adoc b/Documentation/config/push.adoc\nindex d9112b2260..e39a7d8c5b 100644\n--- a/Documentation/config/push.adoc\n+++ b/Documentation/config/push.adoc\n@@ -72,7 +72,7 @@ new default).\n --\n \n `push.followTags`::\n-\tIf set to true, enable `--follow-tags` option by default.  You\n+\tIf set to `true`, enable `--follow-tags` option by default.  You\n \tmay override this configuration at time of push by specifying\n \t`--no-follow-tags`.\n \ndiff --git a/Documentation/config/rebase.adoc b/Documentation/config/rebase.adoc\nindex c6187ab28b..307688f306 100644\n--- a/Documentation/config/rebase.adoc\n+++ b/Documentation/config/rebase.adoc\n@@ -9,22 +9,22 @@ rebase.stat::\n \trebase. False by default.\n \n rebase.autoSquash::\n-\tIf set to true, enable the `--autosquash` option of\n+\tIf set to `true`, enable the `--autosquash` option of\n \tlinkgit:git-rebase[1] by default for interactive mode.\n \tThis can be overridden with the `--no-autosquash` option.\n \n rebase.autoStash::\n-\tWhen set to true, automatically create a temporary stash entry\n+\tWhen set to `true`, automatically create a temporary stash entry\n \tbefore the operation begins, and apply it after the operation\n \tends.  This means that you can run rebase on a dirty worktree.\n \tHowever, use with care: the final stash application after a\n \tsuccessful rebase might result in non-trivial conflicts.\n \tThis option can be overridden by the `--no-autostash` and\n \t`--autostash` options of linkgit:git-rebase[1].\n-\tDefaults to false.\n+\tDefaults to `false`.\n \n rebase.updateRefs::\n-\tIf set to true enable `--update-refs` option by default.\n+\tIf set to `true` enable `--update-refs` option by default.\n \n rebase.missingCommitsCheck::\n \tIf set to \"warn\", git rebase -i will print a warning if some\n@@ -43,7 +43,7 @@ rebase.instructionFormat::\n \tautomatically have the commit hash prepended to the format.\n \n rebase.abbreviateCommands::\n-\tIf set to true, `git rebase` will use abbreviated command names in the\n+\tIf set to `true`, `git rebase` will use abbreviated command names in the\n \ttodo list resulting in something like this:\n +\n -------------------------------------------\n@@ -60,7 +60,7 @@ instead of:\n \t...\n -------------------------------------------\n +\n-Defaults to false.\n+Defaults to `false`.\n \n rebase.rescheduleFailedExec::\n \tAutomatically reschedule `exec` commands that failed. This only makes\n@@ -68,14 +68,14 @@ rebase.rescheduleFailedExec::\n \tThis is the same as specifying the `--reschedule-failed-exec` option.\n \n rebase.forkPoint::\n-\tIf set to false set `--no-fork-point` option by default.\n+\tIf set to `false` set `--no-fork-point` option by default.\n \n rebase.rebaseMerges::\n \tWhether and how to set the `--rebase-merges` option by default. Can\n \tbe `rebase-cousins`, `no-rebase-cousins`, or a boolean. Setting to\n-\ttrue or to `no-rebase-cousins` is equivalent to\n+\t`true` or to `no-rebase-cousins` is equivalent to\n \t`--rebase-merges=no-rebase-cousins`, setting to `rebase-cousins` is\n-\tequivalent to `--rebase-merges=rebase-cousins`, and setting to false is\n+\tequivalent to `--rebase-merges=rebase-cousins`, and setting to `false` is\n \tequivalent to `--no-rebase-merges`. Passing `--rebase-merges` on the\n \tcommand line, with or without an argument, overrides any\n \t`rebase.rebaseMerges` configuration.\ndiff --git a/Documentation/config/receive.adoc b/Documentation/config/receive.adoc\nindex 36a1e6f2d2..75ffe2d980 100644\n--- a/Documentation/config/receive.adoc\n+++ b/Documentation/config/receive.adoc\n@@ -1,16 +1,16 @@\n receive.advertiseAtomic::\n \tBy default, git-receive-pack will advertise the atomic push\n \tcapability to its clients. If you don't want to advertise this\n-\tcapability, set this variable to false.\n+\tcapability, set this variable to `false`.\n \n receive.advertisePushOptions::\n-\tWhen set to true, git-receive-pack will advertise the push options\n+\tWhen set to `true`, git-receive-pack will advertise the push options\n \tcapability to its clients. False by default.\n \n receive.autogc::\n \tBy default, git-receive-pack will run \"git maintenance run --auto\" after\n \treceiving data from git-push and updating refs.  You can stop\n-\tit by setting this variable to false.\n+\tit by setting this variable to `false`.\n \n receive.certNonceSeed::\n \tBy setting this variable to a string, `git receive-pack`\n@@ -32,9 +32,9 @@ receive.certNonceSlop::\n \tcan check `GIT_PUSH_CERT_NONCE_STATUS` is `OK`.\n \n receive.fsckObjects::\n-\tIf it is set to true, git-receive-pack will check all received\n+\tIf it is set to `true`, git-receive-pack will check all received\n \tobjects. See `transfer.fsckObjects` for what's checked.\n-\tDefaults to false. If not set, the value of\n+\tDefaults to `false`. If not set, the value of\n \t`transfer.fsckObjects` is used instead.\n \n receive.fsck.<msg-id>::\n@@ -75,20 +75,20 @@ receive.maxInputSize::\n \tis unlimited.\n \n receive.denyDeletes::\n-\tIf set to true, git-receive-pack will deny a ref update that deletes\n+\tIf set to `true`, git-receive-pack will deny a ref update that deletes\n \tthe ref. Use this to prevent such a ref deletion via a push.\n \n receive.denyDeleteCurrent::\n-\tIf set to true, git-receive-pack will deny a ref update that\n+\tIf set to `true`, git-receive-pack will deny a ref update that\n \tdeletes the currently checked out branch of a non-bare repository.\n \n receive.denyCurrentBranch::\n-\tIf set to true or \"refuse\", git-receive-pack will deny a ref update\n+\tIf set to `true` or \"refuse\", git-receive-pack will deny a ref update\n \tto the currently checked out branch of a non-bare repository.\n \tSuch a push is potentially dangerous because it brings the HEAD\n \tout of sync with the index and working tree. If set to \"warn\",\n \tprint a warning of such a push to stderr, but allow the push to\n-\tproceed. If set to false or \"ignore\", allow such pushes with no\n+\tproceed. If set to `false` or \"ignore\", allow such pushes with no\n \tmessage. Defaults to \"refuse\".\n +\n Another option is \"updateInstead\" which will update the working\n@@ -103,7 +103,7 @@ the index have any difference from the HEAD, but the `push-to-checkout`\n hook can be used to customize this.  See linkgit:githooks[5].\n \n receive.denyNonFastForwards::\n-\tIf set to true, git-receive-pack will deny a ref update which is\n+\tIf set to `true`, git-receive-pack will deny a ref update which is\n \tnot a fast-forward. Use this to prevent such an update via a push,\n \teven if that push is forced. This configuration variable is\n \tset when initializing a shared repository.\n@@ -137,9 +137,9 @@ E.g.:\n \tgit config --system --add receive.procReceiveRefs !:refs/heads\n \n receive.updateServerInfo::\n-\tIf set to true, git-receive-pack will run git-update-server-info\n+\tIf set to `true`, git-receive-pack will run git-update-server-info\n \tafter receiving data from git-push and updating refs.\n \n receive.shallowUpdate::\n-\tIf set to true, .git/shallow can be updated when new refs\n+\tIf set to `true`, .git/shallow can be updated when new refs\n \trequire new shallow roots. Otherwise those refs are rejected.\ndiff --git a/Documentation/config/remote.adoc b/Documentation/config/remote.adoc\nindex 91e46f66f5..2f440cce62 100644\n--- a/Documentation/config/remote.adoc\n+++ b/Documentation/config/remote.adoc\n@@ -38,7 +38,7 @@ remote.<name>.push::\n \tlinkgit:git-push[1].\n \n remote.<name>.mirror::\n-\tIf true, pushing to this remote will automatically behave\n+\tIf `true`, pushing to this remote will automatically behave\n \tas if the `--mirror` option was given on the command line.\n \n remote.<name>.skipDefaultUpdate::\n@@ -47,7 +47,7 @@ remote.<name>.skipDefaultUpdate::\n \tvalues, the value of the last occurrence will be used).\n \n remote.<name>.skipFetchAll::\n-\tIf true, this remote will be skipped when updating\n+\tIf `true`, this remote will be skipped when updating\n \tusing linkgit:git-fetch[1], the `update` subcommand of\n \tlinkgit:git-remote[1], and ignored by the prefetch task\n \tof `git maintenance`.\n@@ -73,13 +73,13 @@ remote.<name>.vcs::\n \tthe remote with the git-remote-<vcs> helper.\n \n remote.<name>.prune::\n-\tWhen set to true, fetching from this remote by default will also\n+\tWhen set to `true`, fetching from this remote by default will also\n \tremove any remote-tracking references that no longer exist on the\n \tremote (as if the `--prune` option was given on the command line).\n \tOverrides `fetch.prune` settings, if any.\n \n remote.<name>.pruneTags::\n-\tWhen set to true, fetching from this remote by default will also\n+\tWhen set to `true`, fetching from this remote by default will also\n \tremove any local tags that no longer exist on the remote if pruning\n \tis activated in general via `remote.<name>.prune`, `fetch.prune` or\n \t`--prune`. Overrides `fetch.pruneTags` settings, if any.\n@@ -88,7 +88,7 @@ See also `remote.<name>.prune` and the PRUNING section of\n linkgit:git-fetch[1].\n \n remote.<name>.promisor::\n-\tWhen set to true, this remote will be used to fetch promisor\n+\tWhen set to `true`, this remote will be used to fetch promisor\n \tobjects.\n \n remote.<name>.partialclonefilter::\ndiff --git a/Documentation/config/repack.adoc b/Documentation/config/repack.adoc\nindex e9e78dcb19..b421ceb9c7 100644\n--- a/Documentation/config/repack.adoc\n+++ b/Documentation/config/repack.adoc\n@@ -7,29 +7,29 @@ repack.useDeltaBaseOffset::\n \tnative protocol are unaffected by this option.\n \n repack.packKeptObjects::\n-\tIf set to true, makes `git repack` act as if\n+\tIf set to `true`, makes `git repack` act as if\n \t`--pack-kept-objects` was passed. See linkgit:git-repack[1] for\n \tdetails. Defaults to `false` normally, but `true` if a bitmap\n \tindex is being written (either via `--write-bitmap-index` or\n \t`repack.writeBitmaps`).\n \n repack.useDeltaIslands::\n-\tIf set to true, makes `git repack` act as if `--delta-islands`\n+\tIf set to `true`, makes `git repack` act as if `--delta-islands`\n \twas passed. Defaults to `false`.\n \n repack.writeBitmaps::\n-\tWhen true, git will write a bitmap index when packing all\n+\tWhen `true`, git will write a bitmap index when packing all\n \tobjects to disk (e.g., when `git repack -a` is run).  This\n \tindex can speed up the \"counting objects\" phase of subsequent\n \tpacks created for clones and fetches, at the cost of some disk\n \tspace and extra time spent on the initial repack.  This has\n \tno effect if multiple packfiles are created.\n-\tDefaults to true on bare repos, false otherwise.\n+\tDefaults to `true` on bare repos, `false` otherwise.\n \n repack.updateServerInfo::\n-\tIf set to false, linkgit:git-repack[1] will not run\n-\tlinkgit:git-update-server-info[1]. Defaults to true. Can be overridden\n-\twhen true by the `-n` option of linkgit:git-repack[1].\n+\tIf set to `false`, linkgit:git-repack[1] will not run\n+\tlinkgit:git-update-server-info[1]. Defaults to `true`. Can be overridden\n+\twhen `true` by the `-n` option of linkgit:git-repack[1].\n \n repack.cruftWindow::\n repack.cruftWindowMemory::\n@@ -41,8 +41,8 @@ repack.cruftThreads::\n \tvariables for defaults and meaning.\n \n repack.midxMustContainCruft::\n-\tWhen set to true, linkgit:git-repack[1] will unconditionally include\n+\tWhen set to `true`, linkgit:git-repack[1] will unconditionally include\n \tcruft pack(s), if any, in the multi-pack index when invoked with\n-\t`--write-midx`. When false, cruft packs are only included in the MIDX\n+\t`--write-midx`. When `false`, cruft packs are only included in the MIDX\n \twhen necessary (e.g., because they might be required to form a\n-\treachability closure with MIDX bitmaps). Defaults to true.\n+\treachability closure with MIDX bitmaps). Defaults to `true`.\ndiff --git a/Documentation/config/rerere.adoc b/Documentation/config/rerere.adoc\nindex 3a78b5ebb1..20eb3ba870 100644\n--- a/Documentation/config/rerere.adoc\n+++ b/Documentation/config/rerere.adoc\n@@ -1,7 +1,7 @@\n rerere.autoUpdate::\n-\tWhen set to true, `git-rerere` updates the index with the\n+\tWhen set to `true`, `git-rerere` updates the index with the\n \tresulting contents after it cleanly resolves conflicts using\n-\tpreviously recorded resolutions.  Defaults to false.\n+\tpreviously recorded resolutions.  Defaults to `false`.\n \n rerere.enabled::\n \tActivate recording of resolved conflicts, so that identical\ndiff --git a/Documentation/config/revert.adoc b/Documentation/config/revert.adoc\nindex 802d6faca2..da2b66dc58 100644\n--- a/Documentation/config/revert.adoc\n+++ b/Documentation/config/revert.adoc\n@@ -1,3 +1,3 @@\n revert.reference::\n-\tSetting this variable to true makes `git revert` behave\n+\tSetting this variable to `true` makes `git revert` behave\n \tas if the `--reference` option is given.\ndiff --git a/Documentation/config/stash.adoc b/Documentation/config/stash.adoc\nindex a1197ffd7d..c4c998d575 100644\n--- a/Documentation/config/stash.adoc\n+++ b/Documentation/config/stash.adoc\n@@ -7,8 +7,8 @@ ifdef::git-stash[]\n endif::git-stash[]\n \n `stash.index`::\n-\tIf this is set to true, `git stash apply` and `git stash pop` will\n-\tbehave as if `--index` was supplied. Defaults to false.\n+\tIf this is set to `true`, `git stash apply` and `git stash pop` will\n+\tbehave as if `--index` was supplied. Defaults to `false`.\n ifndef::git-stash[]\n See the descriptions in linkgit:git-stash[1].\n +\n@@ -18,15 +18,15 @@ linkgit:git-pull[1].\n endif::git-stash[]\n \n `stash.showIncludeUntracked`::\n-\tIf this is set to true, the `git stash show` command will show\n-\tthe untracked files of a stash entry. Defaults to false. {see-show}\n+\tIf this is set to `true`, the `git stash show` command will show\n+\tthe untracked files of a stash entry. Defaults to `false`. {see-show}\n \n `stash.showPatch`::\n-\tIf this is set to true, the `git stash show` command without an\n-\toption will show the stash entry in patch form.  Defaults to false.\n+\tIf this is set to `true`, the `git stash show` command without an\n+\toption will show the stash entry in patch form.  Defaults to `false`.\n \t{see-show}\n \n `stash.showStat`::\n-\tIf this is set to true, the `git stash show` command without an\n-\toption will show a diffstat of the stash entry.  Defaults to true.\n+\tIf this is set to `true`, the `git stash show` command without an\n+\toption will show a diffstat of the stash entry.  Defaults to `true`.\n \t{see-show}\ndiff --git a/Documentation/config/status.adoc b/Documentation/config/status.adoc\nindex 8caf90f51c..fe0d44e617 100644\n--- a/Documentation/config/status.adoc\n+++ b/Documentation/config/status.adoc\n@@ -5,24 +5,24 @@ status.relativePaths::\n \tprior to v1.5.4).\n \n status.short::\n-\tSet to true to enable --short by default in linkgit:git-status[1].\n+\tSet to `true` to enable --short by default in linkgit:git-status[1].\n \tThe option --no-short takes precedence over this variable.\n \n status.branch::\n-\tSet to true to enable --branch by default in linkgit:git-status[1].\n+\tSet to `true` to enable --branch by default in linkgit:git-status[1].\n \tThe option --no-branch takes precedence over this variable.\n \n status.aheadBehind::\n-\tSet to true to enable `--ahead-behind` and false to enable\n+\tSet to `true` to enable `--ahead-behind` and `false` to enable\n \t`--no-ahead-behind` by default in linkgit:git-status[1] for\n-\tnon-porcelain status formats.  Defaults to true.\n+\tnon-porcelain status formats.  Defaults to `true`.\n \n status.displayCommentPrefix::\n-\tIf set to true, linkgit:git-status[1] will insert a comment\n+\tIf set to `true`, linkgit:git-status[1] will insert a comment\n \tprefix before each output line (starting with\n \t`core.commentChar`, i.e. `#` by default). This was the\n \tbehavior of linkgit:git-status[1] in Git 1.8.4 and previous.\n-\tDefaults to false.\n+\tDefaults to `false`.\n \n status.renameLimit::\n \tThe number of files to consider when performing rename detection\n@@ -37,9 +37,9 @@ status.renames::\n \tDefaults to the value of diff.renames.\n \n status.showStash::\n-\tIf set to true, linkgit:git-status[1] will display the number of\n+\tIf set to `true`, linkgit:git-status[1] will display the number of\n \tentries currently stashed away.\n-\tDefaults to false.\n+\tDefaults to `false`.\n \n status.showUntrackedFiles::\n \tBy default, linkgit:git-status[1] and linkgit:git-commit[1] show\n@@ -63,8 +63,8 @@ This variable can be overridden with the -u|--untracked-files option\n of linkgit:git-status[1] and linkgit:git-commit[1].\n \n status.submoduleSummary::\n-\tDefaults to false.\n-\tIf this is set to a non-zero number or true (identical to -1 or an\n+\tDefaults to `false`.\n+\tIf this is set to a non-zero number or `true` (identical to -1 or an\n \tunlimited number), the submodule summary will be enabled and a\n \tsummary of commits for modified submodules will be shown (see\n \t--summary-limit option of linkgit:git-submodule[1]). Please note\ndiff --git a/Documentation/config/submodule.adoc b/Documentation/config/submodule.adoc\nindex 74f1659a91..a9ed5f923e 100644\n--- a/Documentation/config/submodule.adoc\n+++ b/Documentation/config/submodule.adoc\n@@ -66,9 +66,9 @@ submodule.active::\n \n submodule.recurse::\n \tA boolean indicating if commands should enable the `--recurse-submodules`\n-\toption by default. Defaults to false.\n+\toption by default. Defaults to `false`.\n +\n-When set to true, it can be deactivated via the\n+When set to `true`, it can be deactivated via the\n `--no-recurse-submodules` option. Note that some Git commands\n lacking this option may call some of the above commands affected by\n `submodule.recurse`; for instance `git remote update` will call\n@@ -92,7 +92,7 @@ submodule.propagateBranches::\n \tEnabling this will allow certain commands to accept\n \t`--recurse-submodules` and certain commands that already accept\n \t`--recurse-submodules` will now consider branches.\n-\tDefaults to false.\n+\tDefaults to `false`.\n \n submodule.fetchJobs::\n \tSpecifies how many submodules are fetched/cloned at the same time.\ndiff --git a/Documentation/config/trace2.adoc b/Documentation/config/trace2.adoc\nindex 05639ce33f..897244ac48 100644\n--- a/Documentation/config/trace2.adoc\n+++ b/Documentation/config/trace2.adoc\n@@ -20,19 +20,19 @@ trace2.eventTarget::\n include::../trace2-target-values.adoc[]\n \n trace2.normalBrief::\n-\tBoolean.  When true `time`, `filename`, and `line` fields are\n+\tBoolean.  When `true` `time`, `filename`, and `line` fields are\n \tomitted from normal output.  May be overridden by the\n-\t`GIT_TRACE2_BRIEF` environment variable.  Defaults to false.\n+\t`GIT_TRACE2_BRIEF` environment variable.  Defaults to `false`.\n \n trace2.perfBrief::\n-\tBoolean.  When true `time`, `filename`, and `line` fields are\n+\tBoolean.  When `true` `time`, `filename`, and `line` fields are\n \tomitted from PERF output.  May be overridden by the\n-\t`GIT_TRACE2_PERF_BRIEF` environment variable.  Defaults to false.\n+\t`GIT_TRACE2_PERF_BRIEF` environment variable.  Defaults to `false`.\n \n trace2.eventBrief::\n-\tBoolean.  When true `time`, `filename`, and `line` fields are\n+\tBoolean.  When `true` `time`, `filename`, and `line` fields are\n \tomitted from event output.  May be overridden by the\n-\t`GIT_TRACE2_EVENT_BRIEF` environment variable.  Defaults to false.\n+\t`GIT_TRACE2_EVENT_BRIEF` environment variable.  Defaults to `false`.\n \n trace2.eventNesting::\n \tInteger.  Specifies desired depth of nested regions in the\n@@ -58,7 +58,7 @@ trace2.envVars::\n \tdefault.\n \n trace2.destinationDebug::\n-\tBoolean.  When true Git will print error messages when a\n+\tBoolean.  When `true` Git will print error messages when a\n \ttrace target destination cannot be opened for writing.\n \tBy default, these errors are suppressed and tracing is\n \tsilently disabled.  May be overridden by the\ndiff --git a/Documentation/config/transfer.adoc b/Documentation/config/transfer.adoc\nindex f1ce50f4a6..f3f5faf27e 100644\n--- a/Documentation/config/transfer.adoc\n+++ b/Documentation/config/transfer.adoc\n@@ -39,7 +39,7 @@ data in git's configuration files. If you do want to use this, set\n transfer.fsckObjects::\n \tWhen `fetch.fsckObjects` or `receive.fsckObjects` are\n \tnot set, the value of this variable is used instead.\n-\tDefaults to false.\n+\tDefaults to `false`.\n +\n When set, the fetch or receive will abort in the case of a malformed\n object or a link to a nonexistent object. In addition, various other\n@@ -113,8 +113,8 @@ transfer.unpackLimit::\n \tThe default value is 100.\n \n transfer.advertiseSID::\n-\tBoolean. When true, client and server processes will advertise their\n-\tunique session IDs to their remote counterpart. Defaults to false.\n+\tBoolean. When `true`, client and server processes will advertise their\n+\tunique session IDs to their remote counterpart. Defaults to `false`.\n \n transfer.bundleURI::\n \tWhen `true`, local `git clone` commands will request bundle\n@@ -124,4 +124,4 @@ transfer.bundleURI::\n \n transfer.advertiseObjectInfo::\n \tWhen `true`, the `object-info` capability is advertised by\n-\tservers. Defaults to false.\n+\tservers. Defaults to `false`.\ndiff --git a/Documentation/config/uploadarchive.adoc b/Documentation/config/uploadarchive.adoc\nindex e0698e8c1d..ade9fb2258 100644\n--- a/Documentation/config/uploadarchive.adoc\n+++ b/Documentation/config/uploadarchive.adoc\n@@ -1,5 +1,5 @@\n uploadarchive.allowUnreachable::\n-\tIf true, allow clients to use `git archive --remote` to request\n+\tIf `true`, allow clients to use `git archive --remote` to request\n \tany tree, whether reachable from the ref tips or not. See the\n \tdiscussion in the \"SECURITY\" section of\n \tlinkgit:git-upload-archive[1] for more details. Defaults to\ndiff --git a/Documentation/config/worktree.adoc b/Documentation/config/worktree.adoc\nindex a248076ea5..5eec006f77 100644\n--- a/Documentation/config/worktree.adoc\n+++ b/Documentation/config/worktree.adoc\n@@ -2,7 +2,7 @@\n \tIf no branch is specified and neither `-b` nor `-B` nor\n \t`--detach` is used, then `git worktree add` defaults to\n \tcreating a new branch from HEAD.  If `worktree.guessRemote` is\n-\tset to true, `worktree add` tries to find a remote-tracking\n+\tset to `true`, `worktree add` tries to find a remote-tracking\n \tbranch whose name uniquely matches the new branch name.  If\n \tsuch a branch exists, it is checked out and set as \"upstream\"\n \tfor the new branch.  If no such match can be found, it falls\n\nbase-commit: 7c02d39fc2ed2702223c7674f73150d9a7e61ba4\n-- \ngitgitgadget\n"}]}