diff options
| author | Caleb Marchent <37041441+calebmarchent@users.noreply.github.com> | 2019-04-10 23:03:02 +0100 |
|---|---|---|
| committer | Éric Araujo <merwok@netwok.org> | 2019-04-10 18:03:02 -0400 |
| commit | 42f55ee50011ae822c0b5d4dabf231df8ea9469f (patch) | |
| tree | dff756a66bbe11ca256932466b0f2d75892cb652 /Doc/extending | |
| parent | d914596a671c4b0f13641359cf43aa0d6fc05070 (diff) | |
| download | cpython-git-42f55ee50011ae822c0b5d4dabf231df8ea9469f.tar.gz | |
fix typo in doc (#12686)
Diffstat (limited to 'Doc/extending')
| -rw-r--r-- | Doc/extending/building.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/extending/building.rst b/Doc/extending/building.rst index 9fe12c2424..9bfad7fc31 100644 --- a/Doc/extending/building.rst +++ b/Doc/extending/building.rst @@ -145,7 +145,7 @@ that distutils gets the invocations right. Distributing your extension modules =================================== -When an extension has been successfully build, there are three ways to use it. +When an extension has been successfully built, there are three ways to use it. End-users will typically want to install the module, they do so by running :: @@ -158,7 +158,7 @@ Module maintainers should produce source packages; to do so, they run :: In some cases, additional files need to be included in a source distribution; this is done through a :file:`MANIFEST.in` file; see :ref:`manifest` for details. -If the source distribution has been build successfully, maintainers can also +If the source distribution has been built successfully, maintainers can also create binary distributions. Depending on the platform, one of the following commands can be used to do so. :: |