Doc allow non fips packs in vertex pem 3652

docs/docs-content/vertex/system-management/enable-non-fips-settings/enable-non-fips-settings.md

@@ -12,12 +12,12 @@ tags: ["vertex", "non-fips"]
 
 Palette VerteX is FIPS-enforced by default, incorporating the Spectro Cloud Cryptographic Module into the Kubernetes Management Platform and the infrastructure components of target clusters. To learn more about our cryptographic library, check out [FIPS 140-2 Certification](../../../compliance.md#fips-140-2).
 
-If desired, you can allow the consumption of certain non-FIPS functionality in Palette VerteX at the tenant level. **Platform Settings** at the tenant level provide toggles to allow non-FIPS-compliant add-on packs and non-FIPS features such as scans, backup, and restore. You can also allow importing clusters created external to Palette.
+If desired, you can allow the consumption of certain non-FIPS functionality in Palette VerteX at the tenant level. **Platform Settings** at the tenant level provide toggles to allow non-FIPS-compliant packs and non-FIPS features such as scans, backup, and restore. You can also allow importing clusters created external to Palette.
 
 
 ## Resources
 
-- [Use non-FIPS Add-On Packs](../../system-management/enable-non-fips-settings/use-non-fips-addon-packs.md)
+- [Use non-FIPS Packs](../../system-management/enable-non-fips-settings/use-non-fips-addon-packs.md)
 
 
 - [Use non-FIPS Features](../../system-management/enable-non-fips-settings/use-non-fips-features.md)

docs/docs-content/vertex/system-management/enable-non-fips-settings/use-non-fips-addon-packs.md

@@ -1,7 +1,7 @@
 ---
-sidebar_label: "Use non-FIPS Add-On Packs"
-title: "Use non-FIPS Add-On Packs"
-description: "Add non-FIPS add-on packs to VerteX cluster profiles."
+sidebar_label: "Use non-FIPS Packs"
+title: "Use non-FIPS Packs"
+description: "Add non-FIPS packs to VerteX cluster profiles."
 icon: ""
 hide_table_of_contents: false
 sidebar_position: 0
@@ -12,79 +12,83 @@ tags: ["vertex", "non-fips"]
 
 
 Palette VerteX provides the following FIPS-compliant infrastructure components in Kubernetes clusters it deploys. Review [FIPS-Compliant Components](../../fips/fips-compliant-components.md) to learn more.
-
-<br />
-
 
 - Operating System (OS)
-
 - Kubernetes
-
 - Container Network Interface (CNI)
-
 - Container Storage Interface (CSI)
 
-As shown in the screenshot below, the FIPS-compliant icon used to indicate full FIPS compliance is displayed next to Palette VerteX infrastructure components in the cluster profile stack. To learn about other icons Palette VerteX applies, refer to [FIPS Status Icons](../../fips/fips-status-icons.md).
+VerteX also provides the flexibility to utilize non-FIPS infrastructure packs. To do this, you must add the **Non-fips pack registry** to the tenant. Our support team will provide you with the registry URL.
+
+You can allow tenant users to use non-FIPS infrastructure packs and to customize their cluster profiles by using non-FIPS add-on packs. Add-on packs enhance cluster functionality by adding profile layers such as system apps, authentication, security, monitoring, logging, and more.
+
+The screenshot below shows the icon that VerteX displays next to FIPS-compliant infrastructure components to indicate full FIPS compliance. Other icons are used to indicate profile layers with partial, unknown, or non-FIPS compliant status. To learn about other icons VerteX applies, refer to [FIPS Status Icons](../../fips/fips-status-icons.md).
+
+<!-- As shown in the screenshot below, the FIPS-compliant icon that is used to indicate full FIPS compliance is displayed next to VerteX infrastructure components in the cluster profile stack. To learn about other icons VerteX applies, refer to [FIPS Status Icons](../../fips/fips-status-icons.md). -->
 
 ![Diagram showing FIPS-compliant icons in profile stack.](/vertex_fips-status-icons_icons-in-profile-stack.png) 
 
-You can allow tenant users to customize their cluster profiles by using add-on packs, which *may not* be FIPS compliant. Add-on packs enhance cluster functionality by adding profile layers such as system apps, authentication, security, monitoring, logging, and more.
 
+Use the following steps to enable non-FIPS packs.
 
 ## Prerequisites
 
 - You need tenant admin permission to enable this feature.
 
+- To use non-FIPS infrastructure packs, add the **Non-fips pack registry**.
 
-## Allow Non-FIPS Add-On Packs
 
+## Allow Non-FIPS Packs
 
 1. Log in to [Palette VerteX](https://console.spectrocloud.com/) as a tenant admin.
 
-
 2. Navigate to the left **Main Menu** and click on **Tenant Settings**. 
 
-
 3. On the **Tenant Settings Menu**, select **Platform Settings**.
 
-
-4. Enable the **Allow non-FIPS add-on packs** option. When you enable this option, you are prompted to confirm the use of non-FIPS add-on packs for the tenant.
+4. Enable the **Allow non-FIPS packs** option. When you enable this option, you are prompted to confirm the use of non-FIPS packs for the tenant.
 
 
-![Diagram showing the Allow non-FIPS add-on packs toggle enabled.](/vertex_use-non-fips-settings_nonFips-addon-packs.png)
+![Diagram showing the Allow non-FIPS packs toggle enabled.](/vertex_use-non-fips-settings_nonFips-packs.png)
 
 
 To disable the setting, toggle this option off and confirm you want to disable it.
 
-When you or other users add a pack to a cluster profile. Palette VerteX will apply the appropriate icon next to packs and imported clusters to indicate their FIPS compliance status.   
+When packs are added to a cluster profile, VerteX applies the appropriate icon next to packs and imported clusters to indicate their FIPS compliance status.   
 
 
 ## Validate
 
+Use these steps to verify non-FIPS packs are available.
 
 1. Log in to [Palette VerteX](https://console.spectrocloud.com/).
 
+2. Navigate to the left **Main Menu** and select **Profiles**. 
+
+3. To confirm non-FIPS infrastructure packs are available, Click the **Add Cluster Profile** button and fill out the input values. Select **Infrastructure** for the profile type.
 
-2. Navigate to the left **Main Menu** and select **Profiles**. When you select a profile, the **Add New Pack** option is available.
+4. Select the infrastructure provider or managed Kubernetes for your environment and click **Next**.
 
+5. Select the **Non-fips pack registry** registry in the **drop-down Menu**. Non-FIPS Operating System (OS) packs are listed.
 
-
-3. Navigate back to the **Main Menu** and re-select **Profiles**. 
+6. As you continue creating the profile, non-FIPS infrastructure packs are available for each infrastructure layer:  Kubernetes, network, and storage.
 
+7. To confirm non-FIPS add-on packs are available, select **Profiles** in the **Main Menu** and select the profile you created. 
 
-4. Click the **Add Cluster Profile** button. The **Add-on** option is available in the wizard. 
+8. Click on **Add New Pack**.
 
+9. Select the **Spectro Public Packs** registry in **drop-down Menu**. Several non-FIPS packs are listed. 
 
-Palette VerteX will display the appropriate FIPS status icon next to the pack layer and in the profile stack.
+VerteX will display the appropriate FIPS status icon next to each pack layer.
 
 
 ## Resources
 
 - [Packs List](../../../integrations/integrations.mdx)
 
+- [Create an Infrastructure Profile](../../../profiles/cluster-profiles/create-cluster-profiles/create-infrastructure-profile.md)
 
-- [Create an Add-on Profile](../../../profiles/cluster-profiles/create-cluster-profiles/create-addon-profile/create-addon-profile.md
-
+- [Create an Add-on Profile](../../../profiles/cluster-profiles/create-cluster-profiles/create-addon-profile/create-addon-profile.md)
 
 - [FIPS Status Icons](../../fips/fips-status-icons.md)