diff --git a/Scripts/Batch/Robocopy.md b/Scripts/Batch/Robocopy.md
index 05b3e99..09c5274 100644
--- a/Scripts/Batch/Robocopy.md
+++ b/Scripts/Batch/Robocopy.md
@@ -18,9 +18,10 @@ robocopy "E:\Source" "Z:\Destination" /Z /B /R:5 /W:5 /MT:4 /COPYALL /E
 - `/E` : Directs Robocopy to include all subdirectories in the copy operation, ensuring even empty directories are replicated in the destination.
 
 !!! tip "Usage of Administrative Shares"
-    Whenever dealing with copying data from one server to another, try to leverage "Administrative Shares", sometimes referred to as "Default Shares".  These exist in such a way that, if the server exists in a Windows-based domain, you can type something like `\\SERVER\C$` or `\\SERVER\E$` to access files and bypass most file access restrictions (Generally for reading data, writing works too, but not in all circumstances).  
+    Whenever dealing with copying data from one server to another, try to leverage "Administrative Shares", also referred to as "Default Shares".  These exist in such a way that, if the server exists in a Windows-based domain, you can type something like `\\SERVER\C$` or `\\SERVER\E$` to access files and bypass most file access restrictions (ACLs).  This generally only applies to read-access, write-access may be denied in some circumstances. 
     
-    An adjusted example can be seen below to account for this usage.  **This example assumes you are running robocopy from the source computer**.
+    An adjusted example can be seen below to account for this usage.  **This example assumes you are running robocopy from the destination computer**.
+    **Remember**: You are always **PULLING** data with administrative shares, not pushing it, the source should be the administrative share, and the destination should always be local.
     ```
-    robocopy "E:\Source" "\\DESTINATION-SERVER\E$\Destination" /Z /B /R:5 /W:5 /MT:4 /COPYALL /E
+    robocopy "\\SERVER\E$\SOURCE" "E:\DESTINATION"  /Z /B /R:5 /W:5 /MT:4 /COPYALL /E
     ```
\ No newline at end of file