Fixing more link errors

docs/docs/setting-up/other-specifications/engines/wasm.md

@@ -8,15 +8,15 @@ sidebar_label: Wasm
 
 ## `WASM` Engine Parameters
 
-- **EntryModule** `(`[`InputSource`](../../job-specification/input-source.md)` : required)`: Specifies the WASM module that contains the start function or the main execution code of the task. The InputSource should point to the location of the WASM binary.
+- **EntryModule** `(`[`InputSource`](../../jobs/job-specification/input-source.md)` : required)`: Specifies the WASM module that contains the start function or the main execution code of the task. The InputSource should point to the location of the WASM binary.
 
 - **Entrypoint** `(string: <optional>)`: The name of the function within the EntryModule to execute. For WASI jobs, this should typically be `_start`. The entrypoint function should have zero parameters and zero results.
 
 - **Parameters** `(string[]: <optional>)`: An array of strings containing arguments that will be supplied to the program as ARGV. This allows parameterized execution of the WASM task.
 
 - **EnvironmentVariables** `(map[string]string: <optional>)`: A mapping of environment variable keys to their values, made available within the executing WASM environment.
 
-- **ImportModules** `(`[`InputSource`](../../job-specification/input-source.md)`[] : optional)`: An array of InputSources pointing to additional WASM modules. The exports from these modules will be available as imports to the EntryModule, enabling modular and reusable WASM code.
+- **ImportModules** `(`[`InputSource`](../../jobs/job-specification/input-source.md)`[] : optional)`: An array of InputSources pointing to additional WASM modules. The exports from these modules will be available as imports to the EntryModule, enabling modular and reusable WASM code.
 
 ### Example
 

docs/docs/setting-up/running-node/job-selection.md

@@ -15,7 +15,7 @@ policy.
 | Node.Compute.JobSelection.ProbeExec | `--job-selection-probe-exec` | unused | Use the result of an external program to decide if we should take on the job. |
 | Node.Compute.JobSelection.ProbeHttp | `--job-selection-probe-http` | unused | Use the result of a HTTP POST to decide if we should take on the job. |
 | Node.Compute.JobSelection.RejectStatelessJobs | `--job-selection-reject-stateless` | False | Reject jobs that don't specify any [input data](../data-ingestion/index.md). |
-| Node.Compute.JobSelection.AcceptNetworkedJobs | `--job-selection-accept-networked` | False | Accept jobs that require [network connections](../next-steps/networking.md). |
+| Node.Compute.JobSelection.AcceptNetworkedJobs | `--job-selection-accept-networked` | False | Accept jobs that require [network connections](../networking-instructions/networking.md). |
 
 ## Job selection probes
 

docs/docs/setting-up/workload-onboarding/python-script/index.md

@@ -17,7 +17,7 @@ To get started, you need to install the Bacalhau client, see more information [h
 
 ## Executing Bacalhau Jobs with Python Scripts
 
-To demonstrate this example, I will use the data generated from the [ethereum analysis example](../../data-engineering/blockchain-etl/index.md). This produced a list of hashes that I will iterate over and execute a job for each one.
+To demonstrate this example, I will use the data generated from a Ethereum example. This produced a list of hashes that I will iterate over and execute a job for each one.
 
 
 ```python
@@ -191,4 +191,4 @@ Success! We've now executed a bunch of jobs in parallel using Python. This is a
 
 You might also be interested in the following examples:
 
-* [Analysing Ethereum Data with Python](../../data-engineering/blockchain-etl/index.md)
+* [Analysing Data with Python Pandas](../python-pandas/index.md)