docs: rename index.mdx to README.mdx

Author: LukasGentele

…s/pages/configuration/commands/index.mdx …/pages/configuration/commands/README.mdxdocs/pages/configuration/commands/index.mdx renamed to docs/pages/configuration/commands/README.mdx docs/pages/configuration/commands/index.mdx renamed to docs/pages/configuration/commands/README.mdx

@@ -107,7 +107,7 @@ deployments:
 </Tabs>
 
 :::info Sequential and Concurrent Deployment
-Deployments, like images, will be processed in parallel by default. To process deployments sequentially, you can specify it as a dependency, or override the pipeline and call [create_deployments](../../configuration/functions/index.mdx#create_deployments) sequentially.
+Deployments, like images, will be processed in parallel by default. To process deployments sequentially, you can specify it as a dependency, or override the pipeline and call [create_deployments](../../configuration/functions/README.mdx#create_deployments) sequentially.
 :::
 
 ## Run Deployments

…ges/configuration/dependencies/index.mdx …es/configuration/dependencies/README.mdxdocs/pages/configuration/dependencies/index.mdx renamed to docs/pages/configuration/dependencies/README.mdx docs/pages/configuration/dependencies/index.mdx renamed to docs/pages/configuration/dependencies/README.mdx

@@ -135,7 +135,7 @@ deployments:
 ```
 
 ### `updateImageTags`
-The `updateImageTags` option expects a boolean stating if DevSpace should do [Image Tag Replacement](../index.mdx#3-tag-replacement).
+The `updateImageTags` option expects a boolean stating if DevSpace should do [Image Tag Replacement](../README.mdx#3-tag-replacement).
 
 When set to `true`, DevSpace searches all your values (specified via `values` or `valuesFiles`) for images that are defined in the `images` section of the `devspace.yaml`. If DevSpace finds an image, it replaces or appends the image tag with the tag it created during the image building process. Image tag replacement makes sure that your application will always be started with the most up-to-date image that DevSpace has built for you.
 
@@ -266,7 +266,7 @@ The `values` option expects an object with values that should be overriding the
 
 Compared to the `valuesFiles` option, using `values` has the following advantages:
 - It is easier to comprehend and faster to find (no references)
-- It allows you to use [dynamic config variables](../../variables/index.mdx)
+- It allows you to use [dynamic config variables](../../variables/README.mdx)
 
 :::info
 Because both, `values` and `valuesFiles`, have advantages and disadvantages, it is often useful to combine them. When setting both, values defined in `values` have precedence over values defined in `valuesFiles`.

…ages/configuration/deployments/index.mdx …ges/configuration/deployments/README.mdxdocs/pages/configuration/deployments/index.mdx renamed to docs/pages/configuration/deployments/README.mdx docs/pages/configuration/deployments/index.mdx renamed to docs/pages/configuration/deployments/README.mdx

@@ -39,7 +39,7 @@ The following flags are available for all commands that trigger image building:
 
 
 ## Development Process
-The development process first runs the [deployment process](../../configuration/deployments/index.mdx) (1. - 4.) and then continues with starting the development-specific features.
+The development process first runs the [deployment process](../../configuration/deployments/README.mdx) (1. - 4.) and then continues with starting the development-specific features.
 
 ### 1. Deploy Dependencies
 
@@ -188,7 +188,7 @@ DevSpace allows you to share commands for common development tasks which can be
 ```bash
 devspace list commands
 ```
-Learn how to [configure shared commands for `devspace run`](../../configuration/commands/index.mdx).
+Learn how to [configure shared commands for `devspace run`](../../configuration/commands/README.mdx).
 
 
 ### `devspace list deployments`