[Documetation] Combine limits, timeouts and windows, remove redundant pages

docs/docs/setting-up/running-node/resource-limits.md

@@ -1,9 +1,11 @@
 ---
-sidebar_label: 'Resource Limits'
+sidebar_label: 'Limits & Timeouts'
 sidebar_position: 150
 ---
 
-# Resource Limits
+# Limits and Timeouts
+
+## Resource Limits
 
 These are the flags that control the capacity of the Bacalhau node, and the limits for jobs that might be run.
 
@@ -24,3 +26,58 @@ Resource limits are not supported for Docker jobs running on Windows. Resource
 limits will be applied at the job bid stage based on reported job requirements
 but will be silently unenforced. Jobs will be able to access as many resources
 as requested at runtime.
+
+## Windows support
+Running a Windows-based node is not officially supported, so your mileage may vary. Some features (like [resource limits](#resource-limits)) are not present in Windows-based nodes.
+
+Bacalhau currently makes the assumption that all containers are Linux-based. Users of the Docker executor will need to manually ensure that their Docker engine is running and [configured appropriately](https://docs.docker.com/desktop/install/windows-install/) to support Linux containers, e.g. using the WSL-based backend.
+
+## Timeouts
+
+Bacalhau can limit the total time a job spends executing. A job that spends too
+long executing will be cancelled and no results will be published.
+
+By default, a Bacalhau node does not enforce any limit on job execution time.
+Both node operators and job submitters can supply a maximum execution time
+limit. If a job submitter asks for a longer execution time than permitted by a
+node operator, their job will be rejected.
+
+Applying job timeouts allows node operators to more fairly distribute the work
+submitted to their nodes. It also protects users from transient errors that
+results in their jobs waiting indefinitely.
+
+### Configuring execution time limits for a job
+
+Job submitters can pass the `--timeout` flag to any Bacalhau job submission CLI
+to set a maximum job execution time. The supplied value should be a whole number
+of seconds with no unit.
+
+The timeout can also be added to an existing job spec by adding the `Timeout`
+property to the `Spec`.
+
+### Configuring execution time limits for a node
+
+Node operators can pass the `--max-job-execution-timeout` flag to `bacalhau serve` to
+configure the maximum job time limit. The supplied value should be a numeric
+value followed by a time unit (one of `s` for seconds, `m` for minutes or `h`
+for hours).
+
+Node operators can also use configuration properties to configure execution
+limits.
+
+Compute nodes will use the properties:
+
+| Config property | Meaning |
+|---|---|
+| `Node.Compute.JobTimeouts.MinJobExecutionTimeout` | The minimum acceptable value for a job timeout. A job will only be accepted if it is submitted with a timeout of longer than this value. |
+| `Node.Compute.JobTimeouts.MaxJobExecutionTimeout` | The maximum acceptable value for a job timeout. A job will only be accepted if it is submitted with a timeout of shorter than this value. |
+| `Node.Compute.JobTimeouts.DefaultJobExecutionTimeout` | The job timeout that will be applied to jobs that are submitted without a timeout value.  |
+
+Requester nodes will use the properties:
+
+| Config property | Meaning |
+|---|---|
+| `Node.Requester.Timeouts.MinJobExecutionTimeout` | If a job is submitted with a timeout less than this value, the default job execution timeout will be used instead. |
+| `Node.Requester.Timeouts.DefaultJobExecutionTimeout` | The timeout to use in the job if a timeout is missing or too small. |
+
+