From c0abeaa470310cc9d7701f8fad7bef0a4c6c6c78 Mon Sep 17 00:00:00 2001
From: Evgenii Korolevskii <102794661+e-korolevskii@users.noreply.github.com>
Date: Tue, 9 Aug 2022 23:56:17 +0200
Subject: [PATCH] Update docs/contributors.md

Co-authored-by: Ivan <98037481+IvanZosimov@users.noreply.github.com>
---
 docs/contributors.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/contributors.md b/docs/contributors.md
index 20af15e..d277af2 100644
--- a/docs/contributors.md
+++ b/docs/contributors.md
@@ -65,7 +65,7 @@ Pull requests are the easiest way to contribute changes to git repos at GitHub.
 **Learn more about how to implement tests:**
 
 Adding or changing tests is an integral part of making a change to the code. 
-Unit tests are in the `__tests__` folder, and end-to-end tests are in the `workflows` folder (in the particular file [e2e-cache.yml](https://github.com/actions/setup-python/blob/main/.github/workflows/e2e-cache.yml)).
+Unit tests are in the `__tests__` folder, and end-to-end tests are in the `workflows` folder, particularly take a look at the files with `e2e` and `test` prefixes, for instance, [e2e-cache.yml](https://github.com/actions/setup-python/blob/main/.github/workflows/e2e-cache.yml).
 
 - The contributor can add various types of tests (like unit tests or end-to-end tests), which, in his opinion, will be necessary and sufficient for testing new or changed functionality
 - Tests should cover a successful execution, as well as some edge cases and possible errors