When we converted our manual page source files from the Ronn format to
the AsciiDoc format in commit 0c66dcf
of PR git-lfs#5054, a few terms were accidentally dropped if they were delimited
with angle brackets but not also enclosed with backtick characters.

In commit 219518e of PR git-lfs#5414 we
restored one such missing term in the git-lfs-logs(1) manual page.

We now restore another missing term, this time in the description section
of the git-lfs-checkout(1) manual page, where the "<glob-pattern>"
term was accidentally removed.

We also take the opportunity to rephrase the sentence containing this
term slightly so as to avoid the use of a trailing plural "s" character,
as that causes formatting errors when rendering the AsciiDoc source into
HTML or roff.

When we converted our manual page source files from the Ronn format to
the AsciiDoc format in commit 0c66dcf
of PR git-lfs#5054, a few terms were accidentally dropped if they were delimited
with angle brackets but not also enclosed with backtick characters.

In commit 219518e of PR git-lfs#5414 we
restored one such missing term in the git-lfs-logs(1) manual page,
and in a prior commit in this PR we restored another in the
git-lfs-checkout(1) manual page.

We now restore another missing term, this time in the git-lfs-config(5)
manual page, in the entry for the "lfs.customtransfer.<name>.path"
configuration option, where the "<name>" term was accidentally removed
from a sentence in which it was the first word.

We also take the opportunity to add a leading definite article to the
sentence so to make it slightly more idiomatic and readable.

When we converted our manual page source files from the Ronn format to
the AsciiDoc format in commit 0c66dcf
of PR git-lfs#5054, a few terms were accidentally dropped if they were delimited
with angle brackets but not also enclosed with backtick characters.

In commit 219518e of PR git-lfs#5414 we
restored one such missing term in the git-lfs-logs(1) manual page, and
in prior commits in this PR we restored several others in the
git-lfs-checkout(1) and git-lfs-config(5) manual pages.

We now restore another missing term, this time in the description
section of the git-lfs-smudge(1) manual page, where the "<path>" term
was removed from the sentence which explained the purpose of the
"git lfs smudge" command's optional progress log file path argument.

When we converted our manual page source files from the Ronn format to
the AsciiDoc format in commit 0c66dcf
of PR git-lfs#5054, a few terms were accidentally dropped if they were delimited
with angle brackets but not also enclosed with backtick characters.

In commit 219518e of PR git-lfs#5414 we
restored one such missing term in the git-lfs-logs(1) manual page.

We now restore another missing term, this time in the description section
of the git-lfs-checkout(1) manual page, where the "<glob-pattern>"
term was accidentally removed.

We also take the opportunity to rephrase the sentence containing this
term slightly so as to avoid the use of a trailing plural "s" character,
as that causes formatting errors when rendering the AsciiDoc source into
HTML or roff.

When we converted our manual page source files from the Ronn format to
the AsciiDoc format in commit 0c66dcf
of PR git-lfs#5054, a few terms were accidentally dropped if they were delimited
with angle brackets but not also enclosed with backtick characters.

In commit 219518e of PR git-lfs#5414 we
restored one such missing term in the git-lfs-logs(1) manual page,
and in a prior commit in this PR we restored another in the
git-lfs-checkout(1) manual page.

We now restore another missing term, this time in the git-lfs-config(5)
manual page, in the entry for the "lfs.customtransfer.<name>.path"
configuration option, where the "<name>" term was accidentally removed
from a sentence in which it was the first word.

We also take the opportunity to add a leading definite article to the
sentence so to make it slightly more idiomatic and readable.

When we converted our manual page source files from the Ronn format to
the AsciiDoc format in commit 0c66dcf
of PR git-lfs#5054, a few terms were accidentally dropped if they were delimited
with angle brackets but not also enclosed with backtick characters.

In commit 219518e of PR git-lfs#5414 we
restored one such missing term in the git-lfs-logs(1) manual page, and
in prior commits in this PR we restored several others in the
git-lfs-checkout(1) and git-lfs-config(5) manual pages.

We now restore another missing term, this time in the description
section of the git-lfs-smudge(1) manual page, where the "<path>" term
was removed from the sentence which explained the purpose of the
"git lfs smudge" command's optional progress log file path argument.