docs: fix format isse

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

@@ -12,7 +12,7 @@ layers. You can also update basic profile information such as the name, descript
 
 Cluster profile changes will generate an update notification on all the clusters that are created from the profile.
 Update notifications include information about all the changes applied to the profile since the initial creation or
-since the previous update. You can apply cluster updates individually at any time.
+since the previous update.
 
 :::warning
 
@@ -22,15 +22,22 @@ profiles, check out [Version a Cluster Profile](version-cluster-profile.md).
 
 :::
 
-## Prerequisites
+You can apply cluster updates individually at any time. To learn how to apply updates to an active cluster, review the
+[Update a Cluster](../../../clusters/cluster-management/cluster-updates.md) guide.
+
+Refer to the following sections to learn how to update a cluster profile.
+
+## Modify Basic Profile Information
+
+### Prerequisites
 
 - A cluster profile created in Palette.
 
 - Your Palette account role must have the `clusterProfile.update` permission to update a profile. Refer to the
-  [Cluster Profile permissions](../../../user-management/palette-rbac/project-scope-roles-permissions.md#cluster-profile)
-  reference for more information about roles and permissions.
+  [Permissions](../../../user-management/palette-rbac/permissions.md) page for more information about roles and
+  permissions.
 
-## Modify Basic Profile Information
+### Modify Profile Information
 
 1. Log in to [Palette](https://console.spectrocloud.com).
 
@@ -122,8 +129,6 @@ To learn how to apply the changes, review [Apply Profile Updates to Clusters](#a
 
 To learn how to apply the changes, review [Apply Profile Updates to Clusters](#apply-profile-updates-to-clusters).
 
-# <<<<<<< HEAD
-
 ## Accept Updates to a Cluster Profile
 
 Palette will automatically display the **Update** button when a new version of a pack is available. For example, if you
@@ -215,8 +220,6 @@ Review the following steps to accept incoming pack updates to a cluster profile.
 
 5. Click on the pack layer and review its configuration to ensure the changes are applied.
 
-> > > > > > > 38a1cc420 (docs: DOC-1479 DOC-1481 DOC-462 User Management Refactor (#4712))
-
 ## Update the Pack Version
 
 Packs typically contain changes between versions, such as the addition or removal of parameters and policies. The
@@ -227,15 +230,14 @@ following steps will guide you in updating configurations.
 Ensure you follow these practices when updating to a new pack version.
 
 - You should not copy the pack configuration from one version to another, as the newer version often contains
-  customizations. Instead, you should integrate your changes manually in the new version.
+  customizations. Instead, you should integrate your changes manually in the new version. Use the **Keep** button to
+  copy the lines from the current configuration to the new version.
 - Update to a newer Kubernetes version incrementally, one minor version at a time.
 - Select a specific target version instead of a group that ends in `.x`
 - We do not recommend downgrading packs to the previous version.
 
 :::
 
-# <<<<<<< HEAD
-
 ### Prerequisites
 
 - A cluster profile created in Palette.
@@ -248,61 +250,44 @@ Ensure you follow these practices when updating to a new pack version.
 
 ### Update Pack Version
 
-> > > > > > > 38a1cc420 (docs: DOC-1479 DOC-1481 DOC-462 User Management Refactor (#4712))
-
 1. Log in to [Palette](https://console.spectrocloud.com).
 
 2. From the left **Main Menu**, select **Profiles**.
 
-3. Select the profile you want to update. Palette displays profile details and the profile stack.
-
-4. Click on the pack layer to update.
+3. Select the profile you want to update to access the profile details page.
 
-5. In the **Edit Pack** panel, select a specific target version, not a group that ends in `.x`. Palette displays the
+4. In the **Edit Pack** panel, select a specific target version, not a group that ends in `.x`. Palette displays the
    difference between the current version at left and the new version at right. The target version is displayed in the
    header.
 
    Differences between the displayed configurations are as follows:
 
-   - _Red highlight_ indicates text that is not present in the new configuration.
-
-     These may be lines you have added in the current configuration. Use the arrow that displays between the two
-     configurations to transfer the lines to the new pack version.
-
-     These lines may also have been removed because they are no longer valid in the new configuration. If you need them,
-     you should copy the lines to the new version. Similarly, you should copy any settings from the current
-     configuration.
+   - _Yellow highlight_ indicates text that is not present in the new configuration. These may be lines you have added
+     in the current configuration or lines that have been removed because they are no longer valid in the new
+     configuration. If you need them, you can use the **Keep** button to transfer the lines to the new pack version.
+     Otherwise, click on **Next** to proceed.
 
-   - _Green highlight_ indicates additions in the new configuration that are not present in the pack version you are
+   - _Blue highlight_ indicates additions in the new configuration that are not present in the pack version you are
      using.
 
      #### Example of Difference Between Current and New Configurations
 
-     ![Screenshot that shows Palette's pack diff user interface with red highlight at left and green highlight at right](/integrations_pack_diffs.webp)
+     ![Screenshot that shows Palette's pack diff user interface with yellow highlight at left and blue highlight at right](/integrations_pack_diffs.webp)
 
-   - _Contrasting shades_ of red and green highlight within the same line indicates differences occur in only part of
-     the line.
+5. Check for yellow-highlights in the current configuration that are missing in the new configuration. If there are any
+   customizations lines you added, use the **Keep** button to transfer the lines to the new version. Otherwise, click on
+   **Next** to proceed.
 
-     #### Example of Line Changes in Current and New Configurations
-
-     ![Screenshot that shows Palette's pack diff user interface with contrasting shades of red and green highlight in the same line](/integrations_pack_line_diffs.webp)
-
-6. Check for red-highlight in the configuration that is missing in the new configuration.
-
-   - If there are any lines you added, use the arrow to transfer the lines to the new version.
-   - If there are lines you did not add that are red highlighted, they have been removed in the new version, and you
-     should _not_ copy them over.
-
-7. Check for changed settings in the new configuration, and copy settings from the current configuration to the new
+6. Check for changed settings in the new configuration, and copy settings from the current configuration to the new
    configuration.
 
-8. Review new sections in the new configuration. You should adopt them, as they are typically needed to support the new
+7. Review new sections in the new configuration. You should adopt them, as they are typically needed to support the new
    configuration.
 
-9. Check for changes in the same line that have a different value. If it is not a customization you made, you should
+8. Check for changes in the same line that have a different value. If it is not a customization you made, you should
    adopt the new value, as it is known to be compatible with the new version.
 
-10. Confirm your updates.
+9. Confirm your updates.
 
 To learn how to apply the changes, review [Apply Profile Updates to Clusters](#apply-profile-updates-to-clusters).
 
@@ -325,6 +310,26 @@ To learn how to apply the changes, review [Apply Profile Updates to Clusters](#a
 
 ## Apply Profile Updates to Clusters
 
+You can accept changes to a cluster's cluster profile and override the existing profile configurations to update a
+cluster. Accepting these changes will only apply to the cluster you are updating and will not propagate to the cluster
+profile or other clusters using the same profile.
+
+:::warning
+
+We do not recommend updating a currently deployed cluster profile version to push out changes. Instead, we recommend
+creating a _new_ profile version, and then upgrade active clusters to the new version. For information on versioning
+profiles, check out [Version a Cluster Profile](version-cluster-profile.md).
+
+:::
+
+### Prerequisites
+
+- A cluster profile created in Palette.
+
+- A deployed and healthy cluster with an associated cluster profile that has updates available.
+
+### Apply Updates
+
 1. Log in to [Palette](https://console.spectrocloud.com).
 
 2. From the left **Main Menu**, select **Clusters**. Clusters that are eligible for an update will have an **Updates

docs/docs-content/security-bulletins/reports/cve-2022-2879.md

@@ -20,14 +20,15 @@ tags: ["security", "cve"]
 
 10/25/2024
 
-## Third Party Dependency 
+## Third Party Dependency
 
 go
 
-
 ## NIST CVE Summary
 
-Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.
+Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to
+allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits
+the maximum size of header blocks to 1 MiB.
 
 ## CVE Severity
 
@@ -45,11 +46,6 @@ Awaiting Analysis
 
 This CVE is non-impacting as the impacting symbol and/or function is not used in the product
 
-
 ## Revision History
 
 1. 10/27/2024: Impacted versions changed from 4.5.4 to 4.5.4, 4.5.5
-
-
-
-

docs/docs-content/security-bulletins/reports/cve-2022-2880.md

@@ -20,14 +20,18 @@ tags: ["security", "cve"]
 
 10/25/2024
 
-## Third Party Dependency 
+## Third Party Dependency
 
 go
 
-
 ## NIST CVE Summary
 
-Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparsable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with an unparsable value. After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse query parameters continue to forward the original query parameters unchanged.
+Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparsable
+parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with
+an unparsable value. After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound
+request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the
+query parameters. Proxies which do not parse query parameters continue to forward the original query parameters
+unchanged.
 
 ## CVE Severity
 
@@ -45,11 +49,6 @@ Awaiting Analysis
 
 This CVE is non-impacting as the impacting symbol and/or function is not used in the product
 
-
 ## Revision History
 
 1. 10/27/2024: Impacted versions changed from 4.5.4 to 4.5.4, 4.5.5
-
-
-
-

docs/docs-content/security-bulletins/reports/cve-2022-41716.md

@@ -20,14 +20,16 @@ tags: ["security", "cve"]
 
 10/25/2024
 
-## Third Party Dependency 
+## Third Party Dependency
 
 go
 
-
 ## NIST CVE Summary
 
-Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows. In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\\x00C=D" sets the variables "A=B" and "C=D".
+Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows. In
+syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked
+for. A malicious environment variable value can exploit this behavior to set a value for a different environment
+variable. For example, the environment variable string "A=B\\x00C=D" sets the variables "A=B" and "C=D".
 
 ## CVE Severity
 
@@ -45,11 +47,6 @@ Awaiting Analysis
 
 This CVE is non-impacting as the impacting symbol and/or function is not used in the product
 
-
 ## Revision History
 
 1. 10/27/2024: Impacted versions changed from 4.5.4 to 4.5.4, 4.5.5
-
-
-
-

docs/docs-content/security-bulletins/reports/cve-2022-41720.md

@@ -20,14 +20,19 @@ tags: ["security", "cve"]
 
 10/25/2024
 
-## Third Party Dependency 
+## Third Party Dependency
 
 go
 
-
 ## NIST CVE Summary
 
-On Windows, restricted files can be accessed via os.DirFS and http.Dir. The os.DirFS function and http.Dir type provide access to a tree of files rooted at a given directory. These functions permit access to Windows device files under that root. For example, os.DirFS("C:/tmp").Open("COM1") opens the COM1 device. Both os.DirFS and http.Dir only provide read-only filesystem access. In addition, on Windows, an os.DirFS for the directory (the root of the current drive) can permit a maliciously crafted path to escape from the drive and access any path on the system. With fix applied, the behavior of os.DirFS("") has changed. Previously, an empty root was treated equivalently to "/", so os.DirFS("").Open("tmp") would open the path "/tmp". This now returns an error.
+On Windows, restricted files can be accessed via os.DirFS and http.Dir. The os.DirFS function and http.Dir type provide
+access to a tree of files rooted at a given directory. These functions permit access to Windows device files under that
+root. For example, os.DirFS("C:/tmp").Open("COM1") opens the COM1 device. Both os.DirFS and http.Dir only provide
+read-only filesystem access. In addition, on Windows, an os.DirFS for the directory (the root of the current drive) can
+permit a maliciously crafted path to escape from the drive and access any path on the system. With fix applied, the
+behavior of os.DirFS("") has changed. Previously, an empty root was treated equivalently to "/", so
+os.DirFS("").Open("tmp") would open the path "/tmp". This now returns an error.
 
 ## CVE Severity
 
@@ -45,11 +50,6 @@ Awaiting Analysis
 
 This CVE is non-impacting as the impacting symbol and/or function is not used in the product
 
-
 ## Revision History
 
 1. 10/27/2024: Impacted versions changed from 4.5.4 to 4.5.4, 4.5.5
-
-
-
-

docs/docs-content/security-bulletins/reports/cve-2022-41722.md

@@ -20,14 +20,16 @@ tags: ["security", "cve"]
 
 10/25/2024
 
-## Third Party Dependency 
+## Third Party Dependency
 
 go
 
-
 ## NIST CVE Summary
 
-A path traversal vulnerability exists in filepath.Clean on Windows. On Windows, the filepath.Clean function could transform an invalid path such as "a/../c:/b" into the valid path "c:\\b". This transformation of a relative (if invalid) path into an absolute path could enable a directory traversal attack. After fix, the filepath.Clean function transforms this path into the relative (but still invalid) path ".\\c:\\b".
+A path traversal vulnerability exists in filepath.Clean on Windows. On Windows, the filepath.Clean function could
+transform an invalid path such as "a/../c:/b" into the valid path "c:\\b". This transformation of a relative (if
+invalid) path into an absolute path could enable a directory traversal attack. After fix, the filepath.Clean function
+transforms this path into the relative (but still invalid) path ".\\c:\\b".
 
 ## CVE Severity
 
@@ -45,11 +47,6 @@ Awaiting Analysis
 
 This CVE is non-impacting as the impacting symbol and/or function is not used in the product
 
-
 ## Revision History
 
 1. 10/27/2024: Impacted versions changed from 4.5.4 to 4.5.4, 4.5.5
-
-
-
-

docs/docs-content/security-bulletins/reports/cve-2023-29402.md

@@ -20,14 +20,16 @@ tags: ["security", "cve"]
 
 10/25/2024
 
-## Third Party Dependency 
+## Third Party Dependency
 
 go
 
-
 ## NIST CVE Summary
 
-The go command may generate unexpected code at build time when using cgo. This may result in unexpected behavior when running a go program which uses cgo. This may occur when running an untrusted module which contains directories with newline characters in their names. Modules which are retrieved using the go command, i.e. via "go get", are not affected (modules retrieved using GOPATH-mode, i.e. GO111MODULE=off, may be affected).
+The go command may generate unexpected code at build time when using cgo. This may result in unexpected behavior when
+running a go program which uses cgo. This may occur when running an untrusted module which contains directories with
+newline characters in their names. Modules which are retrieved using the go command, i.e. via "go get", are not affected
+(modules retrieved using GOPATH-mode, i.e. GO111MODULE=off, may be affected).
 
 ## CVE Severity
 
@@ -45,11 +47,6 @@ Awaiting Analysis
 
 This CVE is non-impacting as the impacting symbol and/or function is not used in the product
 
-
 ## Revision History
 
 1. 10/27/2024: Impacted versions changed from 4.5.4 to 4.5.4, 4.5.5
-
-
-
-