Updating wording for uninstall + adding k3s

restart step

Author: kianaharris4

articles/azure-arc/container-storage/includes/multi-node-ubuntu.md

@@ -41,3 +41,9 @@ Then, perform the following steps in your Kubernetes cluster:
    echo "vm.nr_hugepages=$HUGEPAGES_NR" | sudo tee /etc/sysctl.d/99-hugepages.conf
    ```
 
+1. Restart K3s using:
+   
+   ```bash
+   sudo systemctl restart k3s || sudo systemctl restart k3s-agent
+   ```
+   

articles/azure-arc/container-storage/prepare-linux-edge-volumes.md

@@ -23,24 +23,28 @@ The article describes how to prepare Linux for Edge Volumes using AKS enabled by
 
 ### Uninstall previous instance of Azure Container Storage enabled by Azure Arc extension
 
-If you previously installed Azure Container Storage enabled by Azure Arc, you must uninstall the previous instance.
+If you previously installed a version of Azure Container Storage enabled by Azure Arc before version 2.1.0-preview, you must uninstall that previous instance in order to install the newer version. Versions after 2.1.0-preview will be upgradable and will not require this uninstall. 
 
-1. Before you delete the extension, delete your configPod, Persistent Volume Claim (PVC), and Persistent Volume (PV) using the following commands. You must maintain the order of these delete commands. Replace `YOUR_POD_FILE_NAME_HERE`, `YOUR_PVC_FILE_NAME_HERE`, and `YOUR_PV_FILE_NAME_HERE` with your respective file names:
+1. In order to delete the old version of the extension, the Kubernetes resources holding references to old version of the extension must be cleaned up. Any pending resources will hold the clean-up of the extension. There are at least two ways to clean up these resources, either using `kubectl delete <resource_type> <resource_name>` or by 'un-applying' the YAML files used to create the resources. The resources that need to be deleted are typically the 'pod(s)', the PVC referenced, and the subvolume CRD (if *Cloud Ingest Edge Volume* was configured). Alternatively, the 4 following YAML files can be be fed to 'kubectl delete -f' using the following commands in the specified order. These variables must be updated with your information:
+
+   - `YOUR_DEPLOYMENT_FILE_NAME_HERE`: Add your deployment file name(s). In this documentation, the file name used was `deploymentExample.yaml`. If you created multiple deployments, each one must be deleted on a separte line. 
+   - `YOUR_PVC_FILE_NAME_HERE`: Add your Persistent Volume Claim file name(s). In this documentation, if you used the *Cloud Ingest Edge Volume*, the file name used was `cloudIngestPVC.yaml`. If you used the *Local Shared Edge Volume*, the file name used was `localSharedPVC.yaml`. If you created multiple PVCs, each one must be deleted on a separate line. 
+   - `YOUR_EDGE_SUBVOLUME_FILE_NAME_HERE`: Add your Edge Subvolume file name(s). In this documentation, the file name used was `edgeSubvolume.yaml`. If you created multiple subvolumes, each one must be deleted on a separate line. 
+   - `YOUR_EDGE_STORAGE_CONFIGURATION_FILE_NAME_HERE`: Add your Edge Storage Configuration file name here. In this documentation, the file name used was `edgeConfig.yaml`.
 
    ```bash
-   kubectl delete -f "YOUR_POD_FILE_NAME_HERE.yaml"
-   kubectl delete -f "YOUR_PVC_FILE_NAME_HERE.yaml"
-   kubectl delete -f "YOUR_PV_FILE_NAME_HERE.yaml"
+   kubectl delete -f "<YOUR_DEPLOYMENT_FILE_NAME_HERE.yaml>"
+   kubectl delete -f "<YOUR_PVC_FILE_NAME_HERE.yaml>"   
+   kubectl delete -f "<YOUR_EDGE_SUBVOLUME_FILE_NAME_HERE.yaml>"
+   kubectl delete -f "<YOUR_EDGE_STORAGE_CONFIGURATION_FILE_NAME_HERE.yaml>"
    ```
 
-1. After you delete your configPod, PVC, and PV from the previous step, uninstall the extension using the following command. Replace `YOUR_RESOURCE_GROUP_NAME_HERE`, `YOUR_CLUSTER_NAME_HERE`, and `YOUR_EXTENSION_NAME_HERE` with your respective information:
+1. After you delete the files for your deployment(s), PVC(s), Edge Subvolume(s), and Edge Storage Configuration from the previous step, you can uninstall the extension using the following command. Replace `YOUR_RESOURCE_GROUP_NAME_HERE`, `YOUR_CLUSTER_NAME_HERE`, and `YOUR_EXTENSION_NAME_HERE` with your respective information:
 
    ```azurecli
    az k8s-extension delete --resource-group YOUR_RESOURCE_GROUP_NAME_HERE --cluster-name YOUR_CLUSTER_NAME_HERE --cluster-type connectedClusters --name YOUR_EXTENSION_NAME_HERE
    ```
 
-1. If you installed the extension prior to the 1.1.0-preview release (released on 4/19/24) and have a preexisting `config.json` file, be aware that the `config.json` schema changed. Remove the old `config.json` file using `rm config.json`. You can find the new values in the instructions for your specific environment (Arc-connected AKS on Azure, Edge Essentials, or Ubuntu).
-
 [!INCLUDE [prepare-linux-content](includes/prepare-linux-content.md)]
 
 ## Next steps