diff --git a/.github/workflows/a11y-scan.yml b/.github/workflows/a11y-scan.yml
index ec26e4bc..1db76dbf 100644
--- a/.github/workflows/a11y-scan.yml
+++ b/.github/workflows/a11y-scan.yml
@@ -9,6 +9,19 @@ jobs:
         with:
           urls: | # Provide a newline-delimited list of URLs to scan; more information below.
             https://southernmethodistuniversity.github.io/hpc_docs/
+            https://southernmethodistuniversity.github.io/hpc_docs/coldfront/qs_instructor.html
+            https://southernmethodistuniversity.github.io/hpc_docs/coldfront/qs_student.html
+            https://southernmethodistuniversity.github.io/hpc_docs/coldfront/add_change_project.html
+            https://southernmethodistuniversity.github.io/hpc_docs/coldfront/add_class.html
+            https://southernmethodistuniversity.github.io/hpc_docs/coldfront/add_remove_users.html
+            https://southernmethodistuniversity.github.io/hpc_docs/coldfront/request_change_allocation.html
+            https://southernmethodistuniversity.github.io/hpc_docs/coldfront/add_metadata.html
+            https://southernmethodistuniversity.github.io/hpc_docs/coldfront/usage_stats.html
+            https://southernmethodistuniversity.github.io/hpc_docs/coldfront/archive_project.html
+            https://southernmethodistuniversity.github.io/hpc_docs/coldfront/renewals.html
+            https://southernmethodistuniversity.github.io/hpc_docs/coldfront/running_jobs.html
+            https://southernmethodistuniversity.github.io/hpc_docs/coldfront/faq.html
+            https://southernmethodistuniversity.github.io/hpc_docs/coldfront/optout.html
           repository: "SouthernMethodistUniversity/hpc_docs" 
           token: ${{ secrets.A11Y_SCAN_ACCESS_TOKEN }} 
           cache_key: "hpc_docs_a11y_scan" # Provide a filename that will be used when caching results. We recommend including the name or domain of the site being scanned.
diff --git a/docs/_config.yml b/docs/_config.yml
index 189db228..bdb787fb 100644
--- a/docs/_config.yml
+++ b/docs/_config.yml
@@ -21,4 +21,4 @@ sphinx:
       numfig: True
       numfig_secnum_depth: 0
       numfig_format:
-        code-block: "%s"
+        code-block: "%s"
\ No newline at end of file
diff --git a/docs/tutorials/globus_box_transfers.md b/docs/tutorials/globus_box_transfers.md
index d85fd660..6f59f09b 100644
--- a/docs/tutorials/globus_box_transfers.md
+++ b/docs/tutorials/globus_box_transfers.md
@@ -66,15 +66,15 @@ Click the start button above the side the data is coming from to start the trans
 
 You may want to adjust the transfer settings (for example, to only update new or changed files)
 
-:::{Note}
+:::{note}
 You do not have to stay on the Globus site while the transfer is happening. It will send an email when completed.
 :::
 
-:::{Note}
+:::{note}
 The transfers can be slow. We typically see between 1-5 MBPS between Box and M3 (connection speeds to other services may vary).
 :::
 
-:::{Note}
+:::{note}
 Box has a file size limit of 50GB
 :::
 
diff --git a/docs/tutorials/slurm/best_practices.md b/docs/tutorials/slurm/best_practices.md
index cbf7e1d6..3d6e1765 100644
--- a/docs/tutorials/slurm/best_practices.md
+++ b/docs/tutorials/slurm/best_practices.md
@@ -80,7 +80,7 @@ $ reportseff -u $USER --since d=1
   3575979  CANCELLED    00:00:43   1.2%     14.0%    12.6%  
 ```
 
-:::{Note}
+:::{note}
 If you command outputs a large number of jobs, the formatting is sometimes not clean.
 :::
 
@@ -100,7 +100,7 @@ If your program is behaving as expected, consider reducing the number of cores y
 
 The memory efficiency represents the percentage of the requested memory that was used by your job. Realistically, anything about `50%` memory efficiency is good. Due to how memory is measured, programs that dynamically allocate and deallocate memory may fail as a result of running out of memory even if the reported usage is "low." If you know your program allocates most of the memory it uses at the beginning, aiming for `80-90%` efficiency is a good target.
 
-:::{Note}
+:::{note}
 Memory efficiency is hard to measure. SLURM periodically samples memory usage, so it often misses large spikes of increased memory usage that occurs between samples. It is not unsual for jobs to temporarily use 2x or more memory than reported.
 :::