From c51dd35ea7e0df0751af9c4a533ae4513b5a0048 Mon Sep 17 00:00:00 2001
From: helena <48861601+helenanull@users.noreply.github.com>
Date: Sat, 3 Apr 2021 19:05:35 +0300
Subject: [PATCH] Update README.md

---
 README.md | 17 ++++++++---------
 1 file changed, 8 insertions(+), 9 deletions(-)

diff --git a/README.md b/README.md
index cbf9bfd..e014ce2 100644
--- a/README.md
+++ b/README.md
@@ -30,18 +30,17 @@
     - import **`cypress-example`** folder and you are good to go
 
 ## :bulb: Information
+#### :test_tube: Tests:
+:file_folder: Tests are located in `cypress/integration` folder
 
-Tests are located in `cypress/integration` folder
+:file_folder: Custom commands are located in `cypress/support` folder (`.cmd.js` suffix)
 
-Configuration files:
-1. `cypress.json`
-2. `plugins/index.js`
-
-Custom commands (shortcuts) are located in `cypress/support` folder (`.cmd.js` suffix)
-
-Selectors are located in `cypress/selectors` folder [only difference from cypress default project structure]
-- __not__ using page objects pattern but keeping selectors (only selectors) separately as they are not easily readable and sometimes we need to share selectors between tests
+:file_folder: Selectors (CSS selectors) are located in `cypress/selectors` folder [only difference from cypress default project structure] - __not__ using page objects pattern but keeping selectors (only selectors) separately [Read more](https://github.com/helenanull/cypress-example#grey_question-qa)
 
+#### :hammer_and_wrench: Configuration
+Config files:
+1. `cypress.json` - Main config file where default behavior of Cypress can be modified. [More info](https://docs.cypress.io/guides/references/configuration#cypress-json)
+2. `plugins/index.js` - Plugins file is where we can programmatically alter the resolved configuration [More info](https://docs.cypress.io/guides/tooling/plugins-guide#Use-Cases)
 
 ## :grey_question: Q&A
 1. Why keep selectors separately (not hard-coded to tests)