Update CONTRIBUTING.md

Author: ourownstory

CONTRIBUTING.md

@@ -10,20 +10,7 @@ They can be done somewhat in isolation from other tasks and will take a couple h
 Please come join us on our [Slack](https://join.slack.com/t/neuralprophet/shared_invite/zt-sgme2rw3-3dCH3YJ_wgg01IXHoYaeCg), you can message any core dev there.
 
 ## Process
-In summary, follow the steps below to make your first contribution. If you want to have more details on every step, check out this [beginner's guide to contributing to a GitHub project](https://akrabat.com/the-beginners-guide-to-contributing-to-a-github-project/#to-sum-up). 
-
-1. Setup your development environment for NeuralProphet following [this tutorial](https://github.com/ourownstory/neural_prophet/edit/1166-shorten-contributing.md/CONTRIBUTING.md#dev-install) 
-2. Find an issue to work on by filtering on the label https://github.com/ourownstory/neural_prophet/labels/good%20first%20issue. Comment under the issue, you wish to take over to prevent multiple people working on the same issue. 
-3. Pull the latest changes from remote: `git pull upstream main`
-4. Push changes to your fork: `git push origin main`
-5. Create a new branch from main to work on: `git checkout -b BRANCH_NAME`
-6. Make some changes in your local repository 
-7. Stage the changes: `git add -A`
-8. Commit the changes: `git commit -m "DESCRIPTION OF CHANGES"`
-9. Do a pull request: If you visit https://github.com/ourownstory/neural_prophet now, there should be a green button saying "Compare & pull request", click on it and describe the changes you did. Now you only need to wait for a review and respond to any feedback.
-
-Congratulations, you just contributed your first pull request. For your next issue just follow the steps starting from number 2.
-
+If this is your first time contributing to NeuralProphet, please read our [wiki summary](https://github.com/ourownstory/neural_prophet/wiki#contributing-process) of the steps involved.
 ## Dev Install
 Before starting it's a good idea to first create and activate a new virtual environment:
 ```
@@ -62,15 +49,11 @@ We follow a set of guidelines and methodologies to ensure that code is of high q
 * [Continuous Integration](https://github.com/ourownstory/neural_prophet/wiki#continous-integration): Github Actions is used to set up a CI pipeline
 * [Code Style](https://github.com/ourownstory/neural_prophet/wiki#style): Deploy Black, so there is no need to worry about code style and formatting.
 
-# Github issues and pull requests
-
-# Github issues and pull requests
-
-## Pull requests
+## Prefixes and labels for pull requests and issues
 
 ### Prefixes for pull requests
+All pull requests (PR) should have one of the following prefixes:
 
-All pull requests should have one of the following prefixes:
 * [breaking] Breaking changes, which require user action (e.g. breaking API changes)
 * [major] Major features worth mentioning (e.g. uncertainty prediction)
 * [minor] Minor features which are nice to know about (e.g. add sorting to labels in plots)
@@ -82,14 +65,14 @@ All pull requests should have one of the following prefixes:
 Those prefixed are then used to generate the changelog and decide which version number change is necessary for a release.
 
 ### Labels for pull requests
+Once your PR needs attention, please add an appropriate label:
 
-Once the development of a new feature is 
 - https://github.com/ourownstory/neural_prophet/labels/status%3A%20blocked
 - https://github.com/ourownstory/neural_prophet/labels/status%3A%20needs%20review
 - https://github.com/ourownstory/neural_prophet/labels/status%3A%20needs%20update
 - https://github.com/ourownstory/neural_prophet/labels/status%3A%20ready
 
-## Issue labels
+### Issue labels
 
 Issues should always have a type and a priority. Other labels are optional.