docs: Fix spelling (#3887)

Co-authored-by: finga <finga@onders.org>

docs/docs/92-development/01-getting-started.md

@@ -46,7 +46,7 @@ To apply it during local development, take a look at [`pre-commit`s documentatio
 
 ### Create a `.env` file with your development configuration
 
-Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` in the root of the Woodpecker project and add any need config to it.
+Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` file in the root of the Woodpecker project and add any needed config to it.
 
 A common config for debugging would look like this:
 

docs/versioned_docs/version-1.0/92-development/01-getting-started.md

@@ -39,7 +39,7 @@ For dependencies installation (node_modules) for the UI and documentation of Woo
 
 ### Create a `.env` file with your development configuration
 
-Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` in the root of the Woodpecker project and add any need config to it.
+Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` file in the root of the Woodpecker project and add any needed config to it.
 
 A common config for debugging would look like this:
 

docs/versioned_docs/version-2.4/92-development/01-getting-started.md

@@ -46,7 +46,7 @@ To apply it during local development, take a look at [`pre-commit`s documentatio
 
 ### Create a `.env` file with your development configuration
 
-Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` in the root of the Woodpecker project and add any need config to it.
+Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` file in the root of the Woodpecker project and add any needed config to it.
 
 A common config for debugging would look like this:
 

docs/versioned_docs/version-2.5/92-development/01-getting-started.md

@@ -46,7 +46,7 @@ To apply it during local development, take a look at [`pre-commit`s documentatio
 
 ### Create a `.env` file with your development configuration
 
-Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` in the root of the Woodpecker project and add any need config to it.
+Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` file in the root of the Woodpecker project and add any needed config to it.
 
 A common config for debugging would look like this:
 

docs/versioned_docs/version-2.6/92-development/01-getting-started.md

@@ -46,7 +46,7 @@ To apply it during local development, take a look at [`pre-commit`s documentatio
 
 ### Create a `.env` file with your development configuration
 
-Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` in the root of the Woodpecker project and add any need config to it.
+Similar to the environment variables you can set for your production setup of Woodpecker, you can create a `.env` file in the root of the Woodpecker project and add any needed config to it.
 
 A common config for debugging would look like this: