|
7 | 7 | [](https://github.com/python-poetry/poetry-core/actions?query=workflow%3ATests) |
8 | 8 |
|
9 | 9 | A [PEP 517](https://www.python.org/dev/peps/pep-0517/) build backend implementation developed for |
10 | | -[Poetry](https://github.com/python-poetry/poetry). This project is intended to be a light weight, fully compliant, |
11 | | -self-contained package allowing PEP 517 compatible build frontends to build Poetry managed projects. |
| 10 | +[Poetry](https://github.com/python-poetry/poetry). This project is intended to be a lightweight, fully compliant, |
| 11 | +self-contained package allowing PEP 517-compatible build frontends to build Poetry-managed projects. |
12 | 12 |
|
13 | 13 | ## Usage |
14 | | -In most cases, the usage of this package is transparent to the end-user as it is either made use by Poetry itself |
| 14 | +In most cases, the usage of this package is transparent to the end-user as it is either used by Poetry itself |
15 | 15 | or a PEP 517 frontend (eg: `pip`). |
16 | 16 |
|
17 | | -In order to enable the use `poetry-core` as your build backend, the following snippet must be present in your |
| 17 | +In order to enable the use of `poetry-core` as your build backend, the following snippet must be present in your |
18 | 18 | project's `pyproject.toml` file. |
19 | 19 |
|
20 | 20 | ```toml |
@@ -43,4 +43,4 @@ project. |
43 | 43 |
|
44 | 44 | In order to improve the above situation, `poetry-core` was created. Shared functionality pertaining to PEP 517 build |
45 | 45 | backends, including reading `pyproject.toml` and building wheel/sdist, were implemented in this package. This |
46 | | -makes PEP 517 builds extremely fast for Poetry managed packages. |
| 46 | +makes PEP 517 builds extremely fast for Poetry-managed packages. |
0 commit comments