fix contributing instructions

CONTRIBUTING.md

@@ -12,20 +12,6 @@ If you have an idea for improvement, you can submit your proposal in the *Issues
 
 Please follow instructions specified in the [README](README.md#installation) file and you are good to code!
 
-## Ephemeral development environment
-
-You are more then welcome to contribute to our codebase from the cloud!  
-We set up an ephemeral [Gitpod](https://www.gitpod.io) environment for all the developers who prefer coding from a remote server.
-
-Just click on this cool button below:  
-[![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/AngryMaciek/warlock)
-
-See more information on how to start up a _Gitpod_ environment dedicated to a specific remote branch [here](https://www.gitpod.io/docs/introduction/learn-gitpod/context-url#branch-and-commit-contexts), specific issue [here](https://www.gitpod.io/docs/introduction/learn-gitpod/context-url#issue-context) and a specific pull request [here](https://www.gitpod.io/docs/introduction/learn-gitpod/context-url#pullmerge-request-context).
-
-However, please remember that such luxury is limitted:
-> Gitpod offers a free plan for new users which includes 50 hours of standard workspace usage.
->If you need more hours, you can upgrade to one of the paid plans in your personal settings.
-
 ## Branch naming convention
 
 You can read about git branching [under this address](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging). The branch names should follow the convention specified below: