fix mdx problems

docs/docs-content/clusters/cluster-groups/create-cluster-group.md

@@ -40,7 +40,7 @@ Use the instructions below to create a cluster group.
 2. Click **+New Cluster Groups** to create a new cluster group and provide the following information to the creation wizard.
 
 
-   * **Basic Information: **
+   * **Basic Information**: 
 
   |         Parameter           | Description  |
   |-------------------------------|-----------------|

docs/docs-content/devx/palette-virtual-clusters/palette-virtual-clusters.md

@@ -26,7 +26,7 @@ To create your new Palette Virtual Cluster complete the following actions.
 
  <br />
 
- |**Palette Virtual Cluster Resource ** | **Default    **   |**Minimum Limit**|
+ |Palette Virtual Cluster Resource | Default      | Minimum Limit |
  |------------------------------|-------------------|-----------------|
  | CPU (per request)            | 4                 | 3               |
  | Memory (per request)         | 4 GiB             | 3 GiB           |

docs/docs-content/devx/services/db-services.md

@@ -25,7 +25,7 @@ You must allocate storage to the database service based on the available storage
 :::caution
 
 
-By default, cluster groups are configured not to back up the disk storage. This default behavior affects database services because a backup would not include the storage disk. To learn more, refer to [Enable Disk Backup on Virtual Clusters](../../clusters/cluster-groups/cluster-group-backups.md.
+By default, cluster groups are configured not to back up the disk storage. This default behavior affects database services because a backup would not include the storage disk. To learn more, refer to [Enable Disk Backup on Virtual Clusters](../../clusters/cluster-groups/cluster-group-backups.md).
 
 :::
 

docs/docs-content/enterprise-version/install-palette/install-on-kubernetes/palette-helm-ref.md

@@ -98,7 +98,7 @@ You can configure Palette to use Single Sign-On (SSO) for user authentication. C
 To configure SSO, you must provide the following parameters.
 
 | **Parameters** | **Description** |  **Type** | **Default value** |
-| --- | --- | --- | --- | --- |
+| --- | --- | --- | --- | 
 | `saml.enabled` | Specifies whether to enable SSO SAML configuration by setting it to true. | Boolean | `false` |
 | `saml.acsUrlRoot` | The root URL of the Assertion Consumer Service (ACS).| String | `myfirstpalette.spectrocloud.com`|
 | `saml.acsUrlScheme` | The URL scheme of the ACS: `http` or `https`. | String | `https` |

docs/docs-content/enterprise-version/install-palette/install-on-vmware/install.md

@@ -92,13 +92,13 @@ The video below demonstrates the installation wizard and the prompts you will en
 <Tabs groupId="mode">
 <TabItem label="Non-Airgap" value="non-airgap">
 
-<video title="palette-cli-install" src="/videos/palette-install.mp4"></video>
+<Video title="palette-cli-install" src="/videos/palette-install.mp4"></Video>
 
 </TabItem>
 <TabItem label="Airgap" value="airgap">
 
 
-<video title="palette-cli-install" src="/videos/palette-airgap-install.mp4"></video>
+<Video title="palette-cli-install" src="/videos/palette-airgap-install.mp4"></Video>
 
 </TabItem>
 

docs/docs-content/enterprise-version/upgrade.md

@@ -67,16 +67,14 @@ Prior versions of Palette installed internal Palette components' ingress resourc
 
 1. Connect to the cluster using the cluster's kubeconfig file.
 
-
-
 2. Identify all Ingress resources that belong to *Hubble* - an internal Palette component.
 
- 	```shell
-  kubectl get ingress --namespace default
-  ```
+   ```shell
+   kubectl get ingress --namespace default
+   ```
 
 3. Remove each Ingress resource listed in the output that starts with the name Hubble. Use the following command to delete an Ingress resource. Replace `REPLACE_ME` with the name of the Ingress resource you are removing.
 
-  ```shell
-  kubectl delete ingress --namespace default <REPLACE_ME>
-  ```
+   ```shell
+   kubectl delete ingress --namespace default <REPLACE_ME>
+   ```

docs/docs-content/palette-cli/commands/login.md

@@ -12,7 +12,7 @@ The `login` command authenticates the Palette CLI with Palette. The `login` comm
 
   <br />
 
-| **Flag**                  | **Description**                                                                          | **Type**    |  |
+| **Flag**                  | **Description**                                                                          | **Type**    | 
 |-----------------------|--------------------------------------------------------------------------------------|---------|
 | `--api-key`           | Palette API key (omit for interactive login).                                         | string  |
 | `--cluster-group-name`| Palette Cluster Group name (optional). Specifies the active Cluster Group.               | string  |

docs/docs-content/profiles/app-profiles/delete-app-profile.md

@@ -28,7 +28,7 @@ If an app profile has more than one version, ensure you delete the appropriate v
 
 4. To delete an app profile and all its versions, click on the **three-dot Menu** in the row of the profile to delete and select **Delete**. 
 
-  To delete a specific profile version, select the profile to display its details. Use the **drop-down Menu** next to the profile name and select the version to delete. Click the trash can icon to delete that version. 
+   To delete a specific profile version, select the profile to display its details. Use the **drop-down Menu** next to the profile name and select the version to delete. Click the trash can icon to delete that version. 
 
 You have successfully deleted an app profile or profile version.
 

docs/docs-content/profiles/cluster-profiles/modify-cluster-profiles/update-cluster-profile.md

@@ -39,7 +39,7 @@ We do not recommend updating a currently deployed cluster profile version to pus
 
   :::
 
-5. Save your changes.
+4. Save your changes.
 
 
 ### Validate

docs/docs-content/registries-and-packs/deploy-pack.md

@@ -874,7 +874,7 @@ In the **Nodes config** section, provide the details for the master and worker p
 Keep the **Cloud Configuration** the same for both master and worker pools.
 
 |**Field** | **Value**|
-|---| --- | ---|
+|---| --- | 
 |Instance Type | General purpose `m4.xlarge` <br />A minimum allocation of four CPU cores is required for the master node. |
 |Availability zones | Choose any *one* availability zone.<br /> This tutorial uses the `us-east-1a` availability zone. | 
 |Disk size | 60 GiB | 

docs/docs-content/registries-and-packs/registries/registries.md

@@ -33,7 +33,7 @@ Registries are automatically synchronized with Palette. Helm registries are diff
 Palette comes with a set of default registries that are available to all SaaS tenants, and non-airgap self-hosted Palette environments. The default registries are listed below:
 
 | **Name** | **Provider** | **Description** | **URL** | **Base Path** |
-| --- | --- | --- | --- | --- | --- |
+| --- | --- | --- | --- | --- |
 | Bitnami | Helm | A Helm Chart registry containing Helm Charts maintained and supported by Bitnami. | `https://charts.bitnami.com/bitnami` | - |
 | Public Spectro Helm Repo | Helm | A Helm Chart registry containing Helm Charts maintained and supported by us. | `https://spectrocloud.github.io/helm-charts` | - |
 | Public Repo | Legacy Packs | A packs registry containing packs maintained and supported by us. |  `https://registry.spectrocloud.com` | - |

docs/docs-content/tenant-settings/api-key-management.md

@@ -16,7 +16,7 @@ Unlike regular user accounts, tenant administrators can view all API keys create
 The following table describes the API key management tasks you can perform as a tenant administrator, and how they differ from non-tenant users.
 
 | **Action** | **Description** | **Tenant Admin** | **Non-tenant User** |
-| --- | --- | --- | --- | --- |
+| --- | --- | --- | --- |
 | **List** | List all API keys in the tenant. | ✅ | ❌ |
 | **Create** | Create a new API key. | ✅ |  ✅ |
 | **Create for User** | Create a new API key for a different user. | ✅ | ❌ |

docs/docs-content/vertex/install-palette-vertex/install-on-kubernetes/vertex-helm-ref.md

@@ -94,7 +94,7 @@ You can configure Palette VerteX to use Single Sign-On (SSO) for user authentica
 To configure SSO, you must provide the following parameters.
 
 | **Parameters** | **Description** |  **Type** | **Default value** |
-| --- | --- | --- | --- | --- |
+| --- | --- | --- | --- | 
 | `saml.enabled` | Specifies whether to enable SSO SAML configuration by setting it to true. | Boolean | `false` |
 | `saml.acsUrlRoot` | The root URL of the Assertion Consumer Service (ACS).| String | `myfirstpalette.spectrocloud.com`|
 | `saml.acsUrlScheme` | The URL scheme of the ACS: `http` or `https`. | String | `https` |