docs: fix doc page nesting

- Fixed over nesting of doc pages and image folders
- Edited the first part of the docs.

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

Author: Iheanacho-ai

docs.json

@@ -44,11 +44,11 @@
               {
                 "group": "Self Hosted",
                 "pages": [
-                  "omni/infrastructure-and-extensions/self-hosted/overview",
-                  "omni/infrastructure-and-extensions/self-hosted/deploy-omni-on-prem",
-                  "omni/infrastructure-and-extensions/self-hosted/configure-keycloak-for-omni/configure-keycloak-for-omni",
-                  "omni/infrastructure-and-extensions/self-hosted/how-to-back-up-on-prem-omni-db",
-                  "omni/infrastructure-and-extensions/self-hosted/expose-omni-with-nginx-https"
+                    "omni/infrastructure-and-extensions/self-hosted/overview",
+                    "omni/infrastructure-and-extensions/self-hosted/deploy-omni-on-prem",
+                    "omni/infrastructure-and-extensions/self-hosted/configure-keycloak-for-omni",
+                    "omni/infrastructure-and-extensions/self-hosted/how-to-back-up-on-prem-omni-db",
+                    "omni/infrastructure-and-extensions/self-hosted/expose-omni-with-nginx-https"
                 ]
               },
               "omni/infrastructure-and-extensions/install-airgapped-omni",
@@ -96,23 +96,24 @@
           {
             "group": "Security and Authentication",
             "pages": [
-              {
-                "group": "Using SAML With Omni",
-                "pages": [
-                  "omni/security-and-authentication/using-saml-with-omni/overview",
-                  "omni/security-and-authentication/using-saml-with-omni/configure-saml-and-acls",
-                  "omni/security-and-authentication/using-saml-with-omni/configure-okta-for-omni/configure-okta-for-omni",
-                  "omni/security-and-authentication/using-saml-with-omni/add-a-user-to-omni-with-saml-enabled/add-a-user-to-omni-with-saml-enabled",
-                  "omni/security-and-authentication/using-saml-with-omni/auto-assign-roles-to-saml-users",
-                  "omni/security-and-authentication/using-saml-with-omni/configure-unifi-identity-enterprise-for-omni/configure-unifi-identity-enterprise-for-omni",
-                  "omni/security-and-authentication/using-saml-with-omni/configure-workspace-one-access-for-omni/configure-workspace-one-access-for-omni",
-                  "omni/security-and-authentication/using-saml-with-omni/how-to-configure-entraid-for-omni"
-                ]
-              },
+                {
+                    "group": "Using SAML With Omni",
+                    "pages": [
+
+                        "omni/security-and-authentication/using-saml-with-omni/overview",
+                        "omni/security-and-authentication/using-saml-with-omni/configure-saml-and-acls",
+                        "omni/security-and-authentication/using-saml-with-omni/configure-okta-for-omni",
+                        "omni/security-and-authentication/using-saml-with-omni/add-a-user-to-omni-with-saml-enabled",
+                        "omni/security-and-authentication/using-saml-with-omni/auto-assign-roles-to-saml-users",
+                        "omni/security-and-authentication/using-saml-with-omni/configure-unifi-identity-enterprise-for-omni",
+                        "omni/security-and-authentication/using-saml-with-omni/configure-workspace-one-access-for-omni",
+                        "omni/security-and-authentication/using-saml-with-omni/how-to-configure-entraid-for-omni"
+                    ]
+                },
               "omni/security-and-authentication/authentication-and-authorization",
               "omni/security-and-authentication/how-to-manage-acls",
               "omni/security-and-authentication/omni-kms-disk-encryption",
-              "omni/security-and-authentication/rotate-siderolink-join-token/rotate-siderolink-join-token"
+              "omni/security-and-authentication/rotate-siderolink-join-token"
             ]
           },
           {

omni/cluster-management/create-a-hybrid-cluster.mdx

@@ -6,7 +6,7 @@ This guide shows you how to create a cluster consisting of any combination of ba
 
 Refer to the general guide on creating a cluster to get started. To create a hybrid cluster, navigate to the cluster, then apply the following cluster patch by clicking on "Config Patches", and create a new patch with the target of "Cluster":
 
-<img src="./images/create-patch-kubescan-enabled.png" alt="Create Patch"/>
+<img src="./images/create-a-hybrid-cluster-create-patch-kubescan-enabled.png" alt="Create Patch"/>
 
 ```yaml
 machine:

omni/cluster-management/etcd-backups.mdx

@@ -112,7 +112,7 @@ spec:
     nanos: 985220192
 ```
 
-You can also get the overall status of the backup subsystem, where the output will be similar to this:
+You can also get the overall status of the backup subsystem:
 
 ```yaml
 metadata:

omni/cluster-management/expose-an-http-service-from-a-cluster.mdx

@@ -8,7 +8,7 @@ You first need to enable the workload service proxying feature on the cluster yo
 
 If you are creating a new cluster, you can enable the feature by checking the checkbox in the “Cluster Features” section:
 
-<img src="./images/create-a-cluster-http-proxying.png" alt="Enable Workload Service Proxying" />
+<img src="./images/expose-an-http-service-create-a-cluster-http-proxying.png" alt="Enable Workload Service Proxying" />
 
 For an existing cluster, simply check the checkbox in the features section of the cluster overview page.
 
@@ -80,7 +80,7 @@ omni-kube-service-exposer.sidero.dev/label: Sample Nginx
 omni-kube-service-exposer.sidero.dev/icon: H4sICB0B1mQAA25naW54LXN2Z3JlcG8tY29tLnN2ZwBdU8ly2zAMvfcrWPZKwiTANWM5015yyiHdDr1kNLZsa0axvKix8/cFJbvNdCRCEvEAPDxQ8/vLSydem+Op7XeVtGCkaHbLftXuNpX8Pax1kveL+UetxY9919erZiWG/k58+/kgvjb7Xonz+Qyn182RP2DZvyjx0OyaYz30x38o8dhemqP43vfdSWi9+DDnCHFuV8O2ksmY/UWKbdNutsPfz9e2OX/pL5U0wghCvqVgqrtTJbfDsL+bzUrhM0F/3MzQGDPjlHIxH9qhaxbrtmueh7d987zbtLvLfDZtz/f1sBWrSj5aD9klhVswwdfWgLNJXR+GL6sgRwSP6QmRd53yELzCCMmRShCjqyFmLOsWwCiIKS01GJOUA0qZHQUby5ZXlsAGjkv8wmuK00A+gDfxoD1DSREQOm0teBdVgOA4wqdY1i0i+AiG4lOGbFEhg7icZWJIgCMz+It1DA/hYDQXScxVjyyohpCprBt7SswylJze49htVNxQjk6xDuSXTAs12OQgUGLWMRenLj4pTsNb11SSde/uPhmbA2U5e6c3qxBiEdhTOhhO77CIwxvJ55p7NVlN1owX+xkOJhUb3M1OTuShAZpQIoK72mtcSF5bwExLoxECjsqzssgIzdMLB2IdiPViApHbsTwhH1KNkIgFHO2tTOB54pjfXu3k4QLechmK9lCGzfm9s0XbQtmWfqa4NB0Oo1lzVtUsx6wjKxtYBcKSMkJOyGzJBbYxBM0aBypZfdBRJyDCz0zNRjXZKw0D/J75KFApFvPVTt73kv/6b0Lr9bqMp/wziz8W9M/pAwQAAA==
 ```
 
-To expose a service, **only the `omni-kube-service-exposer.sidero.dev/port` annotation is required**.
+To expose a service, only the `omni-kube-service-exposer.sidero.dev/port` annotation is required.
 
 Its value **must be a port that is unused** on the nodes, such as by other exposed Services.
 
@@ -109,23 +109,23 @@ You will notice that the Service you annotated will appear under the “Exposed
 
 Clicking it will open the exposed service in Omni.
 
-<img src="./images/accessing-exposed-service.png" alt="Exposed services" width="500" />
+<img src="./images/expose-an-http-service-accessing-exposed-service.png" alt="Exposed services" width="500" />
 
 The URL will either contain a randomly-generated alphanumeric prefix, or the user-defined prefix if the `omni-kube-service-exposer.sidero.dev/prefix` annotation was set.
 
 <Info>
 This feature only works with HTTP services. **Raw TCP or UDP are not supported**.
 </Info>
 
-The services are only accessible to users **authenticated to Omni and that have at least`Reader`level access** to the cluster containing the Service.
+The services are only accessible to users authenticated to Omni and that have at least`Reader`level access to the cluster containing the Service.
 
 ### Examples
 
 Some common examples include running cluster services such as monitoring that require Omni access.
 
 #### Grafana
 
-Grafana is a popular dashboarding tool that can be installed as a helm chart and exposed with the following values.yaml.
+Grafana is a popular dashboarding tool that can be installed as a helm chart and exposed with the following `values.yaml`.
 
 ```
 service:
@@ -145,7 +145,7 @@ helm install -f values.yaml grafana grafana/grafana
 
 #### Kubernetes Dashboard
 
-The Kubernetes dashboard can be deployed via helm into a cluster and exposed with the workload proxy using the following values.yaml.
+The Kubernetes dashboard can be deployed via helm into a cluster and exposed with the workload proxy using the following `values.yaml`.
 
 ```
 web:

…images/create-patch-kubescan-enabled.png …luster-create-patch-kubescan-enabled.pngomni/cluster-management/images/create-patch-kubescan-enabled.png renamed to omni/cluster-management/images/create-a-hybrid-cluster-create-patch-kubescan-enabled.png omni/cluster-management/images/create-patch-kubescan-enabled.png renamed to omni/cluster-management/images/create-a-hybrid-cluster-create-patch-kubescan-enabled.png

@@ -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.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.
 

…ent/images/accessing-exposed-service.png …tp-service-accessing-exposed-service.pngomni/cluster-management/images/accessing-exposed-service.png renamed to omni/cluster-management/images/expose-an-http-service-accessing-exposed-service.png omni/cluster-management/images/accessing-exposed-service.png renamed to omni/cluster-management/images/expose-an-http-service-accessing-exposed-service.png

@@ -7,7 +7,7 @@ Audit logs are enabled by default for customers on our Omni SaaS.
 </Info>
 
 <Info>
-#### Enabling the audit log for self-hosted Omni
+Enabling the audit log for self-hosted Omni
 
 By default, the audit log is disabled. To enable it, you need to specify the `--audit-log-dir <dir>` when starting the Omni server.