Apply suggestions from code review

Co-authored-by: Bjorn Neergaard <bjorn@neersighted.com>
python-poetry · Sep 24, 2022 · b0a1144 · b0a1144
1 parent 24dbaab
commit b0a1144
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/docs/plugins.md b/docs/plugins.md
@@ -119,7 +119,7 @@ This will help keep the performances of Poetry good.
 {{% /note %}}
 
 The plugin also must be declared in the `pyproject.toml` file of the plugin package
-as an `poetry.application.plugin` plugin:
+as a `poetry.application.plugin` plugin:
 
 ```toml
 [tool.poetry.plugins."poetry.application.plugin"]

diff --git a/docs/pyproject.md b/docs/pyproject.md
@@ -414,7 +414,7 @@ Dependencies listed in [dependency groups]({{< relref "managing-dependencies#dep
 
 ## `plugins`
 
-Poetry supports arbitrary plugins which work similarly to `setuptools` entry points.
+Poetry supports arbitrary plugins, which are exposed as the ecosystem-standard [entry points](https://packaging.python.org/en/latest/specifications/entry-points/) and discoverable using `importlib.metadata`. This is similar to (and compatible with) the entry points feature of `setuptools`.
 The syntax for registering a plugin is:
 
 ```toml
@@ -427,8 +427,8 @@ Which are:
 
 - `A` - type of the plugin, for example `poetry.plugin` or `flake8.extension`
 - `B` - name of the plugin
-- `C` - pythonic path to module containing plugin class
-- `D` - name of plugin class
+- `C` - python module import path
+- `D` - the entry point of the plugin (a function or class)
 
 ## `urls`