update docs

Author: gentele

docs/docs/configuration/config.yaml.md

@@ -44,6 +44,8 @@ cluster:
 ```
 A [.devspace/config.yaml](#) contains any public/shared configuration for running a DevSpace for the respective project. It is highly recommended to put this file under version control (e.g. git add).
 
+**Note: You can easily re-configure your DevSpace by running `devspace init -r`.**
+
 ## devspace
 Defines your DevSpace including everything related to portForwarding, sync, and the release config.
 

docs/docs/configuration/overwrite.yaml.md

@@ -2,27 +2,6 @@
 title: /.devspace/overwrite.yaml
 ---
 
-This is an example of the [.devspace/overwrite.yaml](#)
+The [.devspace/overwrite.yaml](#) allows you to define a config that overwrites the config values defined in [.devspace/config.yaml](config.yaml.html). It has the exact same format as the [.devspace/config.yaml](config.yaml.html). 
 
-```yaml
-version: v1
-release:
-  name: devspace-docs
-  namespace: devspace-docs
-  latestBuild: "2018-08-27T17:32:42.5568625+02:00"
-  latestImage: 10.99.117.105:5000/devspace-docs:vkY31ug8IQ
-registry:
-  release:
-    name: devspace-registry
-    namespace: devspace-docs
-  user:
-    username: user-xNAsk
-    password: tY2XpapTMUjt
-cluster:
-  tillerNamespace: devspace-docs
-  useKubeConfig: true
-```
-
-The [.devspace/overwrite.yaml](#) is defined for every developer who wants to use a DevSpace for working on the respective project. This file should **never** be checked into a version control system. Therefore, the DevSpace CLI will automatically create a [.gitignore](#) file within [.devspace/](#) that tells git not to version this file.
-
-**Note: You can easily re-configure your DevSpace by running `devspace init -r`. Therefore, changing this file manually is highly discouraged.**
+**Note: This file should **never** be checked into a version control system. Therefore, the DevSpace CLI will automatically create a [.gitignore](#) file within [.devspace/](#) that tells git not to version this file.**