[doc] Improve grammar/fix missing word (GH-102060)

This commit is contained in:
VMan 2023-02-26 13:15:27 +00:00 committed by GitHub
parent bcadcde712
commit 6daf42b28e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions

View File

@ -70,7 +70,7 @@ Click on the "New issue" button in the top bar to report a new issue.
The submission form has two fields, "Title" and "Comment". The submission form has two fields, "Title" and "Comment".
For the "Title" field, enter a *very* short description of the problem; For the "Title" field, enter a *very* short description of the problem;
less than ten words is good. fewer than ten words is good.
In the "Comment" field, describe the problem in detail, including what you In the "Comment" field, describe the problem in detail, including what you
expected to happen and what did happen. Be sure to include whether any expected to happen and what did happen. Be sure to include whether any

View File

@ -2538,7 +2538,7 @@ should be logged, or the ``extra`` keyword parameter to indicate additional
contextual information to be added to the log). So you cannot directly make contextual information to be added to the log). So you cannot directly make
logging calls using :meth:`str.format` or :class:`string.Template` syntax, logging calls using :meth:`str.format` or :class:`string.Template` syntax,
because internally the logging package uses %-formatting to merge the format because internally the logging package uses %-formatting to merge the format
string and the variable arguments. There would no changing this while preserving string and the variable arguments. There would be no changing this while preserving
backward compatibility, since all logging calls which are out there in existing backward compatibility, since all logging calls which are out there in existing
code will be using %-format strings. code will be using %-format strings.