Update CONTRIBUTING.md

Author: mms-gianni

CONTRIBUTING.md

@@ -1,26 +1,35 @@
 # How to contribute
 
 All contributions are welcome. For simple typos, just open a PR.
-For bigger ideas it might be better to open a issue first before you put a lot of work into it.
+For bigger ideas it might be better to open a issue first before you put a lot of work into it. 
 
-Want to contribute, but dont know where to start? Have a look into the Roadmap.
+Want to contribute, but don't know where to start? Have a look into the Roadmap.
+
+1. Setup your development environment
+2. Fork the repository
+3. Create a new branch
+4. Make your changes
+5. Open a PR
 
 ## Development setup
+
 ### Requirements
 - docker
+- kind
 - kubectl
 - kubero-cli
 
-
 ### Start a cluster
-run a `kubero install` with the [CLI](https://github.com/kubero-dev/kubero-cli/releases/latest) and select kind. This will install a local cluster with a single node and all required components.
+Run `kubero install` with the [CLI](https://github.com/kubero-dev/kubero-cli/releases/latest) and select kind. 
+This will install a local cluster with a single node and all required components.
 
 ### Export the kubeconfig
 ```bash
 kind export kubeconfig --name kubero-XXX --kubeconfig ./kubeconfig
 ```
 
-### Create a namespace
+### Create a dev namespace
+This will avoid interference with the local kubero-ui instance.
 ```bash
 kubectl create namespace kubero-dev
 ```
@@ -32,23 +41,19 @@ mv .env.template .env
 
 ### Start local node server
 ```bash
+cd server
 yarn install
 yarn dev
 ```
 
 ```bash
 cd client
-npm install
-npm run dev
+yarn install
+yarn watch
 ```
 
+### start optional services 
 If you need any additional services (Gitea, Github ...), just run `docker-compose up -d`, or add it to the `docker-compose.yml` file, if it is missing.
 
 Nope. No extra database is required. All data is stored in the Kubernetes cluster.
 
-## How to contribute your code
-
-1. Fork the repository
-2. Create a new branch
-3. Make your changes
-4. Open a PR