Break down contribute (#638)

* update contribute index

* update contribute

Author: solegalli

docs/contribute/contribute_code.rst

@@ -90,11 +90,11 @@ It is optional but highly advisable that you create a virtual environment. A vir
 is a "separate space", where you can install Feature-engine's dependencies. To create a virtual
 environment, use any virtual environment tool of your choice. Some examples include:
 
-    1. `venv <https://docs.python.org/3/library/venv.html>`_
-    2. `conda environments <https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html>`_
+1. `venv <https://docs.python.org/3/library/venv.html>`_
+2. `conda environments <https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html>`_
 
-In the previous links, you find details on how to create the environments as well. We also
-provide some guidelines below.
+In the previous links, you find details on how to create the environments. We provide
+some guidelines below.
 
 venv
 ~~~~
@@ -201,7 +201,7 @@ To commit changes do the following::
     $ git commit -m "my commit message"
 
 and make sure to include an informative but succinct commit message in the present tense,
-for example "fixes style in imputation error message".
+for example "fix style in imputation error message".
 
 The previous commands will commit all files that have changes. If you want to commit just 1
 or 2 files, you can do so as follows::
@@ -259,9 +259,9 @@ We have tests for:
 2. Code style, using flake8
 3. Typehints, using mypy
 4. Documentation, using sphinx.
+5. Coverage using coverage
 
-In the following paragraphs, we will take you through how to test each of the above individually,
-and then altogether.
+In the following paragraphs, we will take you through how to test each of the above.
 
 Test functionality
 ~~~~~~~~~~~~~~~~~~
@@ -277,13 +277,16 @@ feature-engine folder. Then run::
 
     $ pytest
 
-These command will run all the test scripts within the test folder.
+These command will run all the test scripts within the test folder. It will take a few
+minutes.
 
 Alternatively, you can run a specific script as follows::
 
-    $ pytest tests/test_encoding/test_categorical_encoder.py
+    $ pytest tests/test_encoding/test_onehot_encoder.py
 
-So if you just want to run the code you created, you would do::
+The previous command will just run the tests for the one hot encoder.
+
+It will be faster if you just test the code you created, in which case you would do::
 
     $ pytest tests/test_my_new_feature_folder/test_my_new_feature.py
 
@@ -292,9 +295,16 @@ test_my_new_feature_folder.
 
 If you are using Pycharm, this is even easier:
 
-1. In your project directory (where you have all the files and scripts), click with the mouse right button on the folder "tests".
+1. In your project directory (where you have all the files and scripts), right click with the mouse on the folder "tests".
 2. Select "Run pytest in tests".
-3. Done!!
+
+This will run all tests.
+
+To run your specific tests:
+
+1. Locate your test file
+2. Right click with the mouse on the test file.
+3. Select "Run pytest in tests".
 
 Sweet, isn't it?
 
@@ -345,7 +355,7 @@ You can fix code style by running::
 Black and isort may make changes to your file. Don't forget to commit those changes::
 
     $ git add my_new_script.py
-    $ git commit -m "fixes code styling"
+    $ git commit -m "fix code style"
     $ git push origin my_feature_branch
 
 Now, you can go ahead and test that your scripts pass the code styling tests. To do so,

docs/contribute/index.rst

@@ -5,12 +5,13 @@ Contribute
 ==========
 
 Feature-engine is an open source project, originally designed to support the online
-course `Feature Engineering for Machine Learning <https://courses.trainindata.com/p/feature-engineering-for-machine-learning>`_,
+course `Feature Engineering for Machine Learning <https://www.trainindata.com/p/feature-engineering-for-machine-learning>`_,
 but has now gained popularity and supports transformations beyond those taught in the
 course.
 
-Feature-engine is currently supported by a small community and we will be delighted to
+Feature-engine is currently supported by a growing community and we will be delighted to
 accept contributions, large or small, that you wish to make to the project.
+
 Contributing to open-source is a great way to learn and improve coding skills, and also
 a fun thing to do. If you've never contributed to an open source project, we hope to
 make it easy for you with the following guidelines.
@@ -25,12 +26,12 @@ There are many ways to contribute to Feature-engine:
 - Create a new transformer
 - Enhance functionality of current transformers
 - Fix a bug
-- If you find a bug, let us know by creating an `issues <https://github.com/feature-engine/feature_engine/issues/>`_ on Github.
+- If you find a bug, let us know by creating an `issue <https://github.com/feature-engine/feature_engine/issues/>`_ on Github.
 - If you would like additional functionality or a new feature, create an `issue <https://github.com/feature-engine/feature_engine/issues/>`_ on Github.
-- Add a Jupyter notebook to our `Jupyter notebooks example gallery <https://github.com/feature-engine/feature_engine/tree/master/examples>`_.
+- Add a Jupyter notebook to our `Jupyter notebooks example gallery <https://github.com/feature-engine/feature-engine-examples>`_.
 - Improve our documentation, i.e., fix typos, improve grammar, or add more code examples.
 - Write a blog, tweet, or share our project with others.
-- Use Feature-engine in your lectures if you teach
+- Use Feature-engine in your lectures if you teach.
 - `Sponsor us <https://github.com/sponsors/feature-engine>`_.
 
 With plenty of ways to get involved, we would be happy for you to support the project.