A couple of more tweaks

Author: StacySpectro

_partials/_canvos-edge-arg-file.mdx

@@ -17,7 +17,7 @@ Specify the system architecture, OS distribution, and version. These configurati
 
 
    For example, if your `.arg` file contains the following arguments, the full image reference would be
-   `ttl.sh/ubuntu:k3s-1.33.5-v4.8.5-demo`.
+   `ttl.sh/ubuntu:k3s-1.33.5-v4.7.2-demo`.
 
    ```text
    IMAGE_REGISTRY=ttl.sh
@@ -31,4 +31,4 @@ Specify the system architecture, OS distribution, and version. These configurati
 
 The `.arg` file uses the default values for any remaining arguments. Refer to [Edge Artifact Build Configurations](/clusters/edge/edgeforge-workflow/palette-canvos/arg/) for all available `.arg` configuration parameters.
 
-Using the arguments defined in the `.arg` file, the final provider images you generate will have the following naming convention, `[IMAGE_REGISTRY]/[IMAGE_REPO]:[CUSTOM_TAG]`. For example, one of the provider images might be `spectrocloud/ubuntu:k3s-1.33.5-v4.8.5-palette-learn`.
+Using the arguments defined in the `.arg` file, the final provider images you generate will have the following naming convention, `[IMAGE_REGISTRY]/[IMAGE_REPO]:[CUSTOM_TAG]`. For example, one of the provider images might be `spectrocloud/ubuntu:k3s-1.33.5-v4.7.2-palette-learn`.

_partials/_canvos-edge-user-data.mdx

@@ -8,13 +8,12 @@ From the CanvOS directory, copy the **user-data.template** file and name the cop
 	- paletteEndpoint
 	- projectName
 
-The `user-data` file uses the `cloud-init` `cloud-config` format. The first line of your file must be `#cloud-config` to ensure that `cloud-init` recognizes and applies the configuration correctly.
+The `user-data` file uses the `cloud-init` `cloud-config` format. The first line of your file must be `#cloud-config` to ensure that `cloud-init` recognizes and applies the configuration correctly. Delete any unused arguments. 
 
 ```shell
 #cloud-config
 stylus:
   site:
     ...
 ```
-Refer to [Cloud Init Stages](/clusters/edge/edge-configuration/cloud-init/) and the [Edge Installer Configuration Reference](/clusters/edge/edge-configuration/installer-reference/) for supported keys and stages.
-
+Refer to [Prepare User Data and Argument Files](/clusters/edge/edgeforge-workflow/prepare-user-data/) for more information about configuring your `user-data` file and to see sample files for different use cases. Refer to [Cloud Init Stages](/clusters/edge/edge-configuration/cloud-init/), and the [Edge Installer Configuration Reference](/clusters/edge/edge-configuration/installer-reference/) for supported keys and stages. 

docs/docs-content/clusters/edge/edgeforge-workflow/palette-canvos/palette-canvos.md

@@ -118,10 +118,10 @@ customization.
 5. If you are using a self-hosted instance of Palette and have determined a specific CanvOS version, checkout out the
    corresponding tag.
 
-   Otherwise, check out the newest available tag. This guide uses the tag **v4.8.5** as an example.
+   Otherwise, check out the newest available tag. This guide uses the tag **v4.7.2** as an example.
 
    ```shell
-   git checkout v4.8.5
+   git checkout v4.7.2
    ```
 
 6. Review the files relevant for this guide.
@@ -144,6 +144,8 @@ customization.
    - IMAGE_REPO
    - CUSTOM_TAG
 
+For more information about preparing the `.arg` file and full sample files, refer to [Prepare User Data and Argument Files](/clusters/edge/edgeforge-workflow/prepare-user-data/).
+
 8. <PartialsComponent category="palette-edge-canvos-version" name="canvos-edge-arg-file" />
 
    :::preview
@@ -283,7 +285,7 @@ customization.
       system.repo: ubuntu
       system.k8sDistribution: k3s
       system.osName: ubuntu
-      system.peVersion: v4.8.5
+      system.peVersion: v4.7.2
       system.customTag: palette-learn
       system.osVersion: 22
     ```
@@ -297,7 +299,7 @@ customization.
 
     ```hideClipboard bash
     REPOSITORY                   TAG                                    IMAGE ID       CREATED          SIZE
-    spectrocloud/ubuntu          k3s-1.33.5-v4.8.5-palette-learn       075134ad5d4b   10 minutes ago   4.11GB
+    spectrocloud/ubuntu          k3s-1.33.5-v4.7.2-palette-learn       075134ad5d4b   10 minutes ago   4.11GB
     ```
 
 14. To use the provider image with your Edge deployment, push it to the image registry specified in the `.arg` file. Log
@@ -312,7 +314,7 @@ customization.
     cluster deployment.
 
     ```bash
-    docker push $IMAGE_REGISTRY/ubuntu:k3s-1.33.5-v4.8.5-palette-learn
+    docker push $IMAGE_REGISTRY/ubuntu:k3s-1.33.5-v4.7.2-palette-learn
     ```
 
 16. After pushing the provider images to the image registry, open a web browser and log in to
@@ -362,7 +364,7 @@ customization.
       system.repo: ubuntu
       system.k8sDistribution: k3s
       system.osName: ubuntu
-      system.peVersion: v4.8.5
+      system.peVersion: v4.7.2
       system.customTag: palette-learn
       system.osVersion: 22
     ```
@@ -484,10 +486,10 @@ required Edge artifacts.
 5. If you are using a self-hosted instance of Palette and have determined a specific CanvOS version, checkout out the
    corresponding tag.
 
-   Otherwise, check out the newest available tag. This guide uses **v4.8.5** tag as an example.
+   Otherwise, check out the newest available tag. This guide uses **v4.7.2** tag as an example.
 
    ```shell
-   git checkout v4.8.5
+   git checkout v4.7.2
    ```
 
 6. Review the files relevant for this guide.
@@ -498,6 +500,8 @@ required Edge artifacts.
    - `earthly.sh` - Script to invoke the `Earthfile`, and generate target artifacts.
    - `user-data.template` - A sample file containing user data.
 
+For more information about preparing the `.arg` file, refer to [Prepare User Data and Argument Files](/clusters/edge/edgeforge-workflow/prepare-user-data/)
+
 7. Copy the **.arg.template** file from the **CanvOS** directory and name the copy **.arg**. Edit the `.arg` file to
    include the following arguments. These are the most commonly used arguments.
 
@@ -675,7 +679,7 @@ Refer to the [Edge Configuration Stages](../../edge-configuration/cloud-init.md)
       system.repo: opensuse-leap
       system.k8sDistribution: k3s
       system.osName: opensuse-leap
-      system.peVersion: v4.8.5
+      system.peVersion: v4.7.2
       system.customTag: palette-learn
       system.osVersion:
     ```
@@ -690,7 +694,7 @@ Refer to the [Edge Configuration Stages](../../edge-configuration/cloud-init.md)
 
     ```hideClipboard bash
     REPOSITORY                   TAG                               IMAGE ID       CREATED          SIZE
-    spectrocloud/opensuse-leap   k3s-1.33.5-v4.8.5-palette-learn   2427e3667b2f   24 minutes ago   2.22GB
+    spectrocloud/opensuse-leap   k3s-1.33.5-v4.7.2-palette-learn   2427e3667b2f   24 minutes ago   2.22GB
     ```
 
 14. To use the provider images in your cluster profile, push them to the image registry mentioned in the `.arg` file.
@@ -709,7 +713,7 @@ Refer to the [Edge Configuration Stages](../../edge-configuration/cloud-init.md)
     that the utility created.
 
     ```bash
-    docker push spectrocloud/opensuse-leap:k3s-1.33.5-v4.8.5-palette-learn
+    docker push spectrocloud/opensuse-leap:k3s-1.33.5-v4.7.2-palette-learn
     ```
 
 16. After pushing the provider images to the image registry, open a web browser and log in to
@@ -759,7 +763,7 @@ Refer to the [Edge Configuration Stages](../../edge-configuration/cloud-init.md)
       system.repo: opensuse-leap
       system.k8sDistribution: k3s
       system.osName: opensuse-leap
-      system.peVersion: v4.8.5
+      system.peVersion: v4.7.2
       system.customTag: palette-learn
       system.osVersion:
     ```

docs/docs-content/clusters/edge/edgeforge-workflow/prepare-user-data.md

@@ -95,10 +95,10 @@ subject to change. For production workloads, create the `.arg` and `user-data` f
    git tag
    ```
 
-3. Check out the latest available tag. This guide uses the tag v4.8.5 as an example.
+3. Check out the latest available tag. This guide uses the tag v4.7.2 as an example.
 
    ```bash
-   git checkout v4.8.5
+   git checkout v4.7.2
    ```
 
    ### Prepare .arg File
@@ -158,7 +158,7 @@ information about the deployment lifecycle of locally managed Edge hosts, refer
 
 13. Cloud-init stages allow you to configure your Edge host declaratively. These stages are included in your `user-data`
     file. For more information about cloud-init stages, refer to
-    [Cloud-init Stages](../edge-configuration/cloud-init.md).
+    [Cloud Init Stages](../edge-configuration/cloud-init.md).
 
     To configure cloud-init stages for your Edge host, use the `stages` block. For example, the following configuration
     installs Amazon Systems Manager agent on your Edge host during the `after-install-chroot` stage.