diff --git a/README.md b/README.md
index 60d5a6aa3f..90e08f2b5d 100644
--- a/README.md
+++ b/README.md
@@ -436,13 +436,8 @@ Result
![Result](static/assets/docs/images/hide_copy_button.png)
-### Admonitions - Warning / Info / Tip / Dange
+### Admonitions - Warning / Info / Tip / Danger
-:::note
-
-Some **content** with _Markdown_ `syntax`.
-
-:::
:::caution
diff --git a/docs/docs-content/registries-and-packs/deploy-pack.md b/docs/docs-content/registries-and-packs/deploy-pack.md
index 80e6437df3..4c9b54e670 100644
--- a/docs/docs-content/registries-and-packs/deploy-pack.md
+++ b/docs/docs-content/registries-and-packs/deploy-pack.md
@@ -1,7 +1,7 @@
---
-sidebar_label: 'Deploy an Add-On Pack'
-title: 'Deploy an Add-On Pack'
-description: 'How to create and deploy an add-on pack using the manifest files or Helm charts in Spectro Cloud.'
+sidebar_label: 'Deploy a Custom Pack'
+title: 'Deploy a Custom Pack'
+description: 'How to create and deploy a custom pack using the manifest files or Helm charts in Spectro Cloud.'
icon: ''
hide_table_of_contents: false
toc_min_heading_level: 2
@@ -11,8 +11,6 @@ tags: ["packs", "tutorial"]
---
-# Deploy an Add-On Pack
-
Custom add-on packs allow you to deploy Kubernetes applications in clusters and reuse them in multiple deployments. This ensures uniformity across your clusters. The primary use cases for creating custom packs are:
- Aggregated configuration and application dependencies simplify deployment and consumption.
@@ -210,11 +208,10 @@ Ensure you have the following files in the current directory.
### Pack File Structure
Go ahead and review each of the following five files in the pack.
-
-* **pack.json** - This file contains the pack metadata such as `addonType`, `cloudTypes`, and the `kubeManifests` array that contains the list of manifest files: `layer`, `name`, and `version`. Refer to the [JSON Schema](add-custom-packs#json-schema) for a list of attributes and respective data types. The schema validation will happen when you push a pack to the registry.
+* **pack.json** - This file contains the pack metadata such as `addonType`, `cloudTypes`, and the `kubeManifests` array that contains the list of manifest files: `layer`, `name`, and `version`. Refer to the [JSON Schema](add-custom-packs.md#json-schema) for a list of attributes and respective data types. The schema validation will happen when you push a pack to the registry.
-
+
```json
{