Skip to content

Commit d2514e5

Browse files
authored
Docs: remove redundant "adverb-adjective" hyphens from compound modifiers (python/cpython#94551)
Discussion: https://discuss.python.org/t/17021
1 parent 7980ac5 commit d2514e5

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Doc/howto/clinic.rst

+3-3
Original file line numberDiff line numberDiff line change
@@ -541,7 +541,7 @@ Let's dive in!
541541

542542
16. Compile, then run the relevant portions of the regression-test suite.
543543
This change should not introduce any new compile-time warnings or errors,
544-
and there should be no externally-visible change to Python's behavior.
544+
and there should be no externally visible change to Python's behavior.
545545

546546
Well, except for one difference: ``inspect.signature()`` run on your function
547547
should now provide a valid signature!
@@ -1117,7 +1117,7 @@ Here's the syntax for cloning a function::
11171117
``module.class`` in the sample just to illustrate that you must
11181118
use the full path to *both* functions.)
11191119

1120-
Sorry, there's no syntax for partially-cloning a function, or cloning a function
1120+
Sorry, there's no syntax for partially cloning a function, or cloning a function
11211121
then modifying it. Cloning is an all-or nothing proposition.
11221122

11231123
Also, the function you are cloning from must have been previously defined
@@ -1315,7 +1315,7 @@ to specify in your subclass. Here's the current list:
13151315
there is no default, but not specifying a default may
13161316
result in an "uninitialized variable" warning. This can
13171317
easily happen when using option groups—although
1318-
properly-written code will never actually use this value,
1318+
properly written code will never actually use this value,
13191319
the variable does get passed in to the impl, and the
13201320
C compiler will complain about the "use" of the
13211321
uninitialized value. This value should always be a

0 commit comments

Comments
 (0)