Update `management-tasks.md`

diff --git a/docs/management-tasks.md b/docs/management-tasks.md
index f8deb992f0984c3d73f9189af0a04b2964b6bbca..1ca3765c03caf19ac86b0e83f302bef7b23f9307 100644 (file)
--- a/docs/management-tasks.md
+++ b/docs/management-tasks.md
@@ -90,7 +90,7 @@ A PR should have a specific use case that it is solving.
 * If the PR is for a feature, it should have docs.
     * Unless it's a feature we want to discourage, like support for a corner case that we don't want users to use.
 * The docs should include a source example file, not write Python directly in Markdown.
-* If the source example(s) file can have different syntax for Python 3.8, 3.9, 3.10, there should be different versions of the file, and they should be shown in tabs in the docs.
+* If the source example(s) file can have different syntax for different Python versions, there should be different versions of the file, and they should be shown in tabs in the docs.
 * There should be tests testing the source example.
 * Before the PR is applied, the new tests should fail.
 * After applying the PR, the new tests should pass.