diff --git a/docs/aurora/data-management/moving_data_to_aurora/scp.md b/docs/aurora/data-management/moving_data_to_aurora/scp.md
index d346f78e5..14c19ce25 100644
--- a/docs/aurora/data-management/moving_data_to_aurora/scp.md
+++ b/docs/aurora/data-management/moving_data_to_aurora/scp.md
@@ -5,14 +5,16 @@
 Use scp and SFTP to transfer data to/from Aurora. 
 
 ### Transferring files from Aurora (Flare) to Sunspot (Gila)
-From an Aurora login-node, you can transfer files to Sunspot's `Gila` filesystem using the scp command. But first, you need to create SSH keys on Aurora and copy the public key (*.pub) to the ~/.ssh/authorized_keys file on Sunspot.
+From an Aurora login-node, you can transfer files to Sunspot's `gila` filesystem using the `scp` command. But first, you need to create an SSH keypair on Aurora and copy the public key (`*.pub`) to the `~/.ssh/authorized_keys` file on Sunspot.
 1. Create SSH keys on the laptop/desktop/remote machine. See "Creating SSH Keys" section on [this page](https://help.cels.anl.gov/docs/linux/ssh/).
 2. Copy the public key (*.pub) from ~/.ssh folder on Aurora to ~/.ssh/authorized_keys file on Sunspot (sunspot.alcf.anl.gov)
 3. Run the scp command on Aurora to transfer files to Sunspot
+2. Copy the contents of the public key file (`*.pub`) located in the `~/.ssh/` folder on Aurora, and append it to the `~/.ssh/authorized_keys` file on Sunspot (`sunspot.alcf.anl.gov`)
+3. Run the `scp` command on Aurora to transfer files to Sunspot
 ```
-haritha@aurora-uan-0010:~> scp test_file haritha@sunspot.alcf.anl.gov://lus/gila/projects/Aurora_deployment/haritha
+username@aurora-uan-0010:~> scp test_file username@sunspot.alcf.anl.gov://lus/gila/projects/Aurora_deployment/username
 ...
-haritha@uan-0001:/gila/Aurora_deployment/haritha> cat test_file
+username@uan-0001:/gila/Aurora_deployment/username> cat test_file
 this is a test file
 
 ```
@@ -23,18 +25,18 @@ With the bastion pass-through nodes currently used to access both Sunspot and Au
 
 ```
 $ cat .ssh/config
-knight@aurora-uan-0009:~> cat .ssh/config
+username@aurora-uan-0009:~> cat .ssh/config
 Host bastion.alcf.anl.gov
-    User knight
+    User username
 
 Host polaris.alcf.anl.gov
     ProxyJump bastion.alcf.anl.gov
     DynamicForward 3142
-    user knight
+    user username
 ```
 
 ```
-knight@aurora-uan-0009:~> scp knight@polaris.alcf.anl.gov:/eagle/catalyst/proj-shared/knight/test.txt ./
+username@aurora-uan-0009:~> scp username@polaris.alcf.anl.gov:/eagle/catalyst/proj-shared/username/test.txt ./
 ---------------------------------------------------------------------------
                             Notice to Users
 ...
@@ -43,7 +45,7 @@ knight@aurora-uan-0009:~> scp knight@polaris.alcf.anl.gov:/eagle/catalyst/proj-s
                             Notice to Users
 ... 
 [Password:
-knight@aurora-uan-0009:~> cat test.txt 
+username@aurora-uan-0009:~> cat test.txt 
 from_polaris eagle
 ```
 
diff --git a/docs/polaris/workflows/mig-compute.md b/docs/polaris/workflows/mig-compute.md
index 4adde4683..ec75595a5 100644
--- a/docs/polaris/workflows/mig-compute.md
+++ b/docs/polaris/workflows/mig-compute.md
@@ -63,7 +63,7 @@ ascovel@polaris-login-02:~>
 The following example demonstrates the use of MIG compute instances via the `CUDA_VISIBLE_DEVICES` environment variable:
 
 ```shell
-ascovel@polaris-login-02:~/polaris-mig> qsub -l mig_config=/home/ascovel/polaris-mig/mig_config.json -l select=1 -l walltime=60:00 -l filesystems=home:eagle:swift -A Operations -q R639752 -k doe -I
+ascovel@polaris-login-02:~/polaris-mig> qsub -l mig_config=/home/ascovel/polaris-mig/mig_config.json -l select=1 -l walltime=60:00 -l filesystems=home:eagle -A Operations -q R639752 -k doe -I
 qsub: waiting for job 640002.polaris-pbs-01.hsn.cm.polaris.alcf.anl.gov to start
 qsub: job 640002.polaris-pbs-01.hsn.cm.polaris.alcf.anl.gov ready
 
diff --git a/docs/policies/data-and-software-policies/data-policy.md b/docs/policies/data-and-software-policies/data-policy.md
index 2c226fa55..e179057ad 100644
--- a/docs/policies/data-and-software-policies/data-policy.md
+++ b/docs/policies/data-and-software-policies/data-policy.md
@@ -32,7 +32,7 @@ All principal investigators using ALCF resources and ALCF staff members working
 Data stored for any length of time on ALCF resources should only be data directly related to work done on any of the ALCF leadership computing systems. Specific policies apply to the three types of data storage systems maintained at ALCF. Read these policies carefully and plan accordingly in terms of space, usage, and data protection.
 
 ### Home File System Space
-**swift-home**
+**agile-home**
 
 The home file system (/home) is intended to hold your executable files, configuration files, etc. It is NOT meant to hold the output from your application runs (use the data/parallel file system for that purpose). The home file system space is generally moderate in size and is the best protected. Because of its size, backups are practical to accomplish.  The system performs tape backups, enabling the recovery of files more than seven days old or recovery from a catastrophic disk failure. Users should email [support@alcf.anl.gov](mailto:support@alcf.anl.gov) if they need assistance. The table below indicates the capabilities and characteristics of each file system.