edgeforge: fix (#1670) (#1671)

(cherry picked from commit 2692326)

Co-authored-by: Karl Cardenas <[email protected]>

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

@@ -414,14 +414,12 @@ To complete this advanced guide, you will need the following items:
 
 
 * An account with [Docker Hub](https://hub.docker.com/). If you do not have an account with Docker Hub already, refer to the [Create an account](https://docs.docker.com/docker-id/) page for signing-up instructions. 
-<br />
 
-  :::info
+:::info
 
-  This guide uses Docker Hub as an example. You can use any other image registry that suit your requirements.
+This guide uses Docker Hub as an example. You can use any other image registry that suit your requirements.
 
-  :::
-  <br />
+:::
 
 * A public repository named `opensuse-leap` in your image registry. Refer to the [Create a repository](https://docs.docker.com/docker-hub/repos/create/#create-a-repository) instructions for creating a Docker Hub repository and setting the repository's visibility to `public`. 
 
@@ -531,19 +529,20 @@ Use the following instructions on your Linux machine to customize the arguments
   ```
   
   View the newly created file to ensure the customized arguments are set correctly.
+
   <br />
 
   ```bash
   cat .arg
   ```
-  <br />
 
-  :::caution
 
-  Using the arguments defined in the **.arg** file, the final provider image name will have the following naming pattern, `[IMAGE_REGISTRY]/[IMAGE_REPO]:[CUSTOM_TAG]`. Ensure the final artifact name conforms to the Docker Hub image name syntax - `[HOST]/[DOCKER-ID]/[REPOSITORY]:[TAG]`. 
+:::caution
+
+Using the arguments defined in the **.arg** file, the final provider image name will have the following naming pattern, `[IMAGE_REGISTRY]/[IMAGE_REPO]:[CUSTOM_TAG]`. Ensure the final artifact name conforms to the Docker Hub image name syntax - `[HOST]/[DOCKER-ID]/[REPOSITORY]:[TAG]`. 
+
+:::
 
-  :::
-  <br />
 
 11. Use the following command to append the [WireGuard](https://www.wireguard.com/install/) installation instructions to the Dockerfile. You can install more tools and dependencies and configure the image to meet your needs. Add your customizations below the line tagged with the `Add any other image customizations here` comment in the Dockerfile. Do not edit or add any lines before this tagged comment. 
   <br />
@@ -558,13 +557,13 @@ Use the following instructions on your Linux machine to customize the arguments
   ```bash
   cat Dockerfile
   ```
-  <br />  
-  :::caution
 
-  Using the `-y` option with the `sudo zypper install` command is critical to successfully build the images. The default behavior for package installations is to prompt the user for permission to install the package. A user prompt will cause the image creation process to fail. This guidance applies to all dependencies you add through the **Dockerfile**. 
+:::caution
+
+Using the `-y` option with the `sudo zypper install` command is critical to successfully build the images. The default behavior for package installations is to prompt the user for permission to install the package. A user prompt will cause the image creation process to fail. This guidance applies to all dependencies you add through the **Dockerfile**. 
+
+:::
 
-  :::
-  <br />
 
 12. Issue the command below to save your tenant registration token to a local variable. Replace `[your_token_here]` with your actual registration token. 
 <br />
@@ -642,11 +641,11 @@ Use the following instructions on your Linux machine to customize the arguments
   ```
   <br />
 
-  :::info
-  
-  If you plan to build Edge artifacts using a content bundle, use the `+build-provider-images` option instead of the `+build-all-images` option in the command above. The command, `sudo ./earthly.sh +build-provider-images`, will build the provider images but not the Edge installer ISO. 
+:::info
 
-  :::
+If you plan to build Edge artifacts using a content bundle, use the `+build-provider-images` option instead of the `+build-all-images` option in the command above. The command, `sudo ./earthly.sh +build-provider-images`, will build the provider images but not the Edge installer ISO. 
+
+:::
 
 
   This command may take up to 15-20 minutes to finish depending on the resources of the host machine. Upon completion, the command will display the manifest, as shown in the example below, that you will use in your cluster profile later in this tutorial. Note that the `system.xxxxx` attribute values in the manifest example are the same as what you defined earlier in the **.arg** file.