docs fix broken link

Signed-off-by: Amarachi Iheanacho <amarachi.iheanacho@siderolabs.com>

Author: Iheanacho-ai

public/omni/cluster-management/scale-your-cluster/scale-a-cluster-up-or-down.mdx

@@ -6,7 +6,7 @@ title: Scale a Cluster Up or Down
 
 To delete machines in a cluster, click the “Clusters” menu item on the left, then the name of the cluster you wish to delete nodes from. Click the “Nodes” menu item on the left. Now, select “Destroy” from the menu under the elipsis:
 
-<img src="./images/scale-cluster-up-or-down-destroy.png" alt="Scale your cluster"/>
+<img src="../images/scale-cluster-up-or-down-destroy.png" alt="Scale your cluster"/>
 
 The cluster will now scale down.
 

public/omni/getting-started/getting-started.mdx

@@ -2,7 +2,7 @@
 title: Getting Started with Omni
 ---
 
-import { release } from '/snippets/custom-variables.mdx';
+import { version } from '/snippets/custom-variables.mdx';
 
 This guide walks you through creating a high-availability Kubernetes cluster managed by [Omni](https://www.siderolabs.com/omni/) using [Talos Linux](https://talos.dev).  
 While the example uses UTM/QEMU for local virtualization, the same process applies to bare metal machines, cloud instances, or edge devices.
@@ -41,8 +41,7 @@ You must have the following to create a cluster with Omni:
   brew install siderolabs/tap/sidero-tools
   ```
 
-  For manual and Windows installation, refer to the <a href="../../talos/${latest}/getting-started/talosctl#alternative-installation-methods">alternate installation methods</a> in the Talos documentation.
-
+  For manual and Windows installation, refer to the <a href={`../../talos/${version}/getting-started/talosctl#alternative-install`}>alternate installation methods</a> in the Talos documentation.
 
 - `talosconfig` **and** `omniconfig` **files**: Download the `talosconfig` and `omniconfig` configuration files from your Omni dashboard.
 
@@ -219,7 +218,7 @@ From here, you can explore what else Omni can do, such as:
 * [etcd backup and restores](../cluster-management/etcd-backups)
 * [Omni cluster upgrades](../cluster-management/upgrading-clusters)
 * [Expose an HTTP sevice from a cluster](../cluster-management/expose-an-http-service-from-a-cluster)
-* [Scale your clusters up or down](../cluster-management/scale-a-cluster-up-or-down)
+* [Scale your clusters up or down](../cluster-management/scale-your-cluster/scale-a-cluster-up-or-down)
 * [Machine classes](../omni-cluster-setup/create-a-machine-class)
 * [Cluster templates](../reference/cluster-templates)
 * [Infrastructure providers](../infrastructure-and-extensions/infrastructure-providers)

public/omni/infrastructure-and-extensions/modify-kernel-arguments.mdx

@@ -18,7 +18,7 @@ On the overview page, click **Download installation media** on the right.
 
 Add the kernel arguments you want to pass to Talos Linux in the **Additional kernel arguments** field:
 
-<img src="images/modify-kernel-arguments-download-installation-media.png" alt="Download installation media"/>
+<img src="./images/modify-kernel-arguments-download-installation-media.png" alt="Download installation media"/>
 
 Click **Download**.
 
@@ -68,13 +68,13 @@ spec:
 
     2. Click the three dots next to the machine you want to modify and select **Update kernel args**.
 
-    <img src="images/modify-kernel-arguments-update-kernel-args.png" alt="Update kernel args" style={{width: "30%"}}/>
+    <img src="./images/modify-kernel-arguments-update-kernel-args.png" alt="Update kernel args" style={{width: "30%"}}/>
 
     3. In the popup, click the pencil icon to edit the current kernel arguments.
 
     4. Click **Update**.
 
-    <img src="images/modify-kernel-arguments-update.png" alt="Update kernel args popup" style={{width: "60%"}}/>
+    <img src="./images/modify-kernel-arguments-update.png" alt="Update kernel args popup" style={{width: "60%"}}/>
   </Tab>
 
   <Tab title="CLI">

public/omni/infrastructure-and-extensions/self-hosted/install-image-factory-on-prem.mdx

@@ -4,7 +4,7 @@ title: Run Image Factory On-prem
 
 The [Image Factory](https://github.com/siderolabs/image-factory) is a way for you to dynamically create Talos Linux images. There is a public, hosted version of the Image Factory at [factory.talos.dev](https://factory.talos.dev) and it can also be run in your environment.
 
-The Image Factory is a critical component of [Omni](../overview/what-is-omni) to generate installation media and update Talos nodes, but it is not required to use Omni to use the Image Factory. It is a web interface and API for the `imager` command which is used to customize Talos from the command line.
+The Image Factory is a critical component of [Omni](../../overview/what-is-omni) to generate installation media and update Talos nodes, but it is not required to use Omni to use the Image Factory. It is a web interface and API for the `imager` command which is used to customize Talos from the command line.
 
 ## Prerequisites
 
@@ -187,4 +187,4 @@ Add these flags to your docker command.
   -v /dev:/dev --privileged
 ```
 
-After the image factory is running you can continue to the [Omni documentation for a self-hosted installation](./self-hosted/deploy-omni-on-prem).
+After the image factory is running you can continue to the [Omni documentation for a self-hosted installation](../self-hosted/deploy-omni-on-prem).

public/talos/v1.11/platform-specific-installations/virtualized-platforms/proxmox.mdx

@@ -362,7 +362,7 @@ If nodes fail to obtain IP addresses or show "network is unreachable" errors:
 
 ### Secure Boot
 
-For Secure Boot setup, see the [Secure Boot documentation](../../security/secure-boot).
+For Secure Boot setup, see the [Secure Boot documentation](../../platform-specific-installations/bare-metal-platforms/secureboot).
 
 ## Cleaning Up
 

public/talos/v1.12/networking/configuration/time.mdx

@@ -18,7 +18,7 @@ ntp:
         - 1.pool.ntp.org
 ```
 
-See [Time Sync](../../configure-your-talos-cluster/time-sync) for more details about time synchronization in Talos Linux.
+See [Time Sync](../../configure-your-talos-cluster/system-configuration/time-sync) for more details about time synchronization in Talos Linux.
 
 ## Observing Status
 

public/talos/v1.12/platform-specific-installations/bare-metal-platforms/metal-network-configuration.mdx

@@ -14,7 +14,7 @@ Talos Linux when running on a cloud platform (e.g. AWS or Azure), uses the platf
 When running on bare-metal, there is no metadata server, so there are several options to provide initial network configuration (before machine configuration is acquired):
 
 - use automatic network configuration via DHCP (Talos default)
-- use initial boot [kernel command line parameters](../reference/kernel) to configure networking
+- use initial boot [kernel command line parameters](../../reference/kernel) to configure networking
 - use automatic network configuration via DHCP just enough to fetch machine configuration and then use machine configuration to set desired advanced configuration.
 
 If DHCP option is available, it is by far the easiest way to configure networking.
@@ -24,7 +24,7 @@ Talos starting with version 1.4.0 offers a new option to configure networking on
 
 > Note: `META`-based network configuration is only available on Talos Linux `metal` platform.
 
-Talos [dashboard](../deploy-and-manage-workloads/interactive-dashboard) provides a way to configure `META`-based network configuration for a machine using the console, but
+Talos [dashboard](../../deploy-and-manage-workloads/interactive-dashboard) provides a way to configure `META`-based network configuration for a machine using the console, but
 it doesn't support all kinds of network configuration.
 
 ## Network Configuration Format
@@ -122,7 +122,7 @@ timeServers: []
 ```
 
 Every section is optional, so you can configure only the parts you need.
-The format of each section matches the respective network [`*Spec` resource](../learn-more/networking-resources) `.spec` part, e.g the `addresses:`
+The format of each section matches the respective network [`*Spec` resource](../../learn-more/networking-resources) `.spec` part, e.g the `addresses:`
 section matches the `.spec` of `AddressSpec` resource:
 
 ```yaml
@@ -386,7 +386,7 @@ talosctl meta write 0xa "$(cat network.yaml)"
 
 ### Supplying Network Configuration to a Talos Disk Image
 
-Following the [boot assets](../platform-specific-installations/boot-assets) guide, create a disk image passing the network configuration as a `--meta` flag:
+Following the [boot assets](../../platform-specific-installations/boot-assets) guide, create a disk image passing the network configuration as a `--meta` flag:
 
 <CodeBlock lang="sh">
 {`

public/talos/v1.12/platform-specific-installations/virtualized-platforms/proxmox.mdx

@@ -363,7 +363,7 @@ If nodes fail to obtain IP addresses or show "network is unreachable" errors:
 
 ### Secure Boot
 
-For Secure Boot setup, see the [Secure Boot documentation](../../security/secure-boot).
+For Secure Boot setup, see the [Secure Boot documentation](../bare-metal-platforms/secureboot).
 
 ## Cleaning Up
 

public/talos/v1.12/troubleshooting/troubleshooting.mdx

@@ -53,7 +53,7 @@ The client will automatically retry on other endpoints if there are unavailable
 
 Worker nodes should not be used as the endpoint, as they are not able to forward request to other nodes.
 
-The [VIP](../networking/vip) should never be used as Talos API endpoint.
+The [VIP](../networking/advanced/vip) should never be used as Talos API endpoint.
 
 ### TCP Loadbalancer
 
@@ -399,7 +399,7 @@ As mentioned above, this can be achieved by a number of strategies, including:
 
 - an external load balancer
 - DNS records
-- Talos-builtin shared IP ([VIP](../networking/vip))
+- Talos-builtin shared IP ([VIP](../networking/advanced/vip))
 - BGP peering of a shared IP (such as with [kube-vip](https://kube-vip.io))
 
 Using a DNS name here is a good idea, since it allows any other option, while offering