Fix a few links

Linked to .md files, but mkdocs won't direct us to the proper
page that way, instead it shows 404.

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>

Author: alexellis

docs/examples/cursor-cli-agent.md

@@ -1,6 +1,6 @@
 # Run a Headless Coding Agent with Cursor CLI
 
-Cursor's CLI can be used in a non-interactive way within a script or CI job. That makes it ideal for use as a [one-shot task](/tasks/userdata) with a SlicerVM, or a longer running VM that you connect to with a [remote VSCode IDE](/examples/remote-vscode.md).
+Cursor's CLI can be used in a non-interactive way within a script or CI job. That makes it ideal for use as a [one-shot task](/tasks/userdata) with a SlicerVM, or a longer running VM that you connect to with a [remote VSCode IDE](/examples/remote-vscode).
 
 Using this flow, you could create a powerful agent that uses your existing Cursor subscription, running with the "auto" model so it remains within the free tier.
 

docs/examples/docker.md

@@ -2,8 +2,8 @@
 
 There are three ways to try out a container or Docker within Slicer:
 
-1. Start your VM as per the [walkthrough](/getting-started/walkthrough.md), then connect via `ssh` and install Docker inside the VM.
-2. Use [Userdata](/tasks/userdata.md) to install Docker and pull your image on first boot.
+1. Start your VM as per the [walkthrough](/getting-started/walkthrough), then connect via `ssh` and install Docker inside the VM.
+2. Use [Userdata](/tasks/userdata) to install Docker and pull your image on first boot.
 3. Create a custom base image with Docker pre-installed, and your image pre-pulled, with a systemd service to start it on every boot.
 
 On this page we'll cover options 2 and 3.
@@ -16,7 +16,7 @@ The container we're going to use is a [Docker Registry](https://hub.docker.com/_
 
 ## Install Docker and a container via Userdata
 
-You can use [Userdata](/tasks/userdata.md) to install Docker and pull your image on first boot.
+You can use [Userdata](/tasks/userdata) to install Docker and pull your image on first boot.
 
 The below is only a partial snippet to show you the relevant changes:
 

docs/reference/vfio.md

@@ -4,7 +4,7 @@ VFIO (Virtual Function I/O) is a Linux kernel framework that allows a PCI device
 
 Any device such as a GPU or NIC that is passed through to a VM must first be unbound from its current driver on the host, and is exclusively bound to the VFIO driver.
 
-Slicer supports VFIO passthrough for Nvidia GPUs when using Cloud Hypervisor as the hypervisor as per the example [Ollama with a GPU](/examples/gpu-ollama.md).
+Slicer supports VFIO passthrough for Nvidia GPUs when using Cloud Hypervisor as the hypervisor as per the example [Ollama with a GPU](/examples/gpu-ollama).
 
 Support for NICs for router appliances will be coming shortly.
 

docs/tasks/execute-commands.md

@@ -1,6 +1,6 @@
 # Execute commands in a VM
 
-Just like [copying files in and out of a VM](/tasks/copy-files.md), executing commands can be done in several ways:
+Just like [copying files in and out of a VM](/tasks/copy-files), executing commands can be done in several ways:
 
 * Initially, via a userdata script or userdata file specified in the host group or via the API/CLI create command after Slicer has been started.
 * Through SSH assuming direct network access is available to the VM via the LAN or a VPN.

docs/tasks/nested-virtualization.md

@@ -105,7 +105,7 @@ sudo modprobe kvm && sudo modprobe kvm_intel
 
 ### Step 3: Install Slicer within the slicer0 VM
 
-Perform an [installation](/getting-started/install.md) of Slicer within the slicer0 VM.
+Perform an [installation](/getting-started/install) of Slicer within the slicer0 VM.
 
 Generate a configuration file for slicer1: