From c5ccea2bb102798640447438bb52018edb568d6d Mon Sep 17 00:00:00 2001 From: Marco Barbosa Date: Wed, 29 Jan 2025 11:17:31 -0300 Subject: [PATCH] doc typo: unnecessary backslashes to represent brackets in markdown (#11059) There is a small typo in the doc which could mislead users: reference to a table in `pyproject.toml` currently appears as [`\[project.entry-points\]`](https://packaging.python.org/en/latest/guides/creating-and-discovering-plugins/#using-package-metadata) while it should be [`[project.entry-points]`](https://packaging.python.org/en/latest/guides/creating-and-discovering-plugins/#using-package-metadata). Backslashes are appearing because they weren't supposed to be used on code representation in Markdown. --- docs/concepts/projects/config.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/projects/config.md b/docs/concepts/projects/config.md index 39bbf9213..6b3f4eb66 100644 --- a/docs/concepts/projects/config.md +++ b/docs/concepts/projects/config.md @@ -71,7 +71,7 @@ hello = "example:app" ### Plugin entry points Projects may define entry points for plugin discovery in the -[`\[project.entry-points\]`](https://packaging.python.org/en/latest/guides/creating-and-discovering-plugins/#using-package-metadata) +[`[project.entry-points]`](https://packaging.python.org/en/latest/guides/creating-and-discovering-plugins/#using-package-metadata) table of the `pyproject.toml`. For example, to register the `example-plugin-a` package as a plugin for `example`: