updating TODOs

Author: jschalz

docs/pages/_partials/command_run_watch.mdx

@@ -1,10 +1,10 @@
-TODO: run_watch one-liner description
+The function `run_watch` takes in a path to watch and a subcommand to run on that path.
 
 ## Arguments
 
 ### `--fail-on-error`
 
-If true, the command will fail on an error while running the sub command.
+If true, the command will fail on an error while running the subcommand.
 
 ```
 run_watch --path [MY_PATH] -- [my_command]

docs/pages/_partials/command_xargs.mdx

@@ -1,5 +1,3 @@
-//TODO: Lukas/Fabian, what does this function look like in action?
-
 The function `xargs` allows a user to overwrite current flags and utilities.
 
 ## Usage

docs/pages/configuration/images/basics.mdx

@@ -170,7 +170,6 @@ DevSpace automatically tags all images after building them using a tagging schem
 
 [Learn more about defining a custom tagging schema.](../../configuration/images/image-definition/tags.mdx)
 
-#TODO: is the helm/basics.mdx file correct?
 :::info Tag Replacement
 Before deploying your application, DevSpace will use the newly generated image tags and replace them in-memory in the values for your [Helm charts](../../configuration/deployments/helm/basics.mdx) and [Kubernetes manifests](../../configuration/deployments/kubectl/manifests.mdx), so they will be deployed using the newest image tag.
 :::

docs/pages/configuration/pipelines/basics.mdx

@@ -3,7 +3,7 @@ title: Pipelines
 sidebar_label: pipelines
 ---
 
-Pipelines in DevSpace are ... #TODO
+Pipelines in DevSpace consists of one or more jobs that are run in parallel and can depend on each other. Each job consists of one or more conditional steps that are executed in order.
 
 An example `pipelines` section could look like this in `devspace.yaml`:
 ```yaml

docs/pages/configuration/variables/basics.mdx

@@ -138,7 +138,6 @@ DevSpace allows you to use config variables without explicitly defining them as
 The `source` option of a config variable expects either:
 - `all` means to check environment variables **first** and then ask a question if no env variable is defined (**default**)
 - [`env`](../../configuration/variables/environment.mdx) means to check environment variables **only**
-- #TODO: is this question.mdx file correct?
   [`input`](../../configuration/variables/question.mdx) means to ask the user a question **once** (values will be cached in `.devspace/generated.yaml`)
 - [`command`](../../configuration/variables/command.mdx) means DevSpace will not ask the user a question and instead execute a command to determine the value of the variable.
 :::