diff --git a/Workflows/Windows/Windows Server/Roles/DFS/Setting Up DFS Across Multiple File Servers.md b/Workflows/Windows/Windows Server/Roles/DFS/Setting Up DFS Across Multiple File Servers.md
index fe5329a..3311eae 100644
--- a/Workflows/Windows/Windows Server/Roles/DFS/Setting Up DFS Across Multiple File Servers.md	
+++ b/Workflows/Windows/Windows Server/Roles/DFS/Setting Up DFS Across Multiple File Servers.md	
@@ -24,16 +24,16 @@ The next step in the process is to ensure that the network shares that will be s
 !!! warning "Replicate Folders and Permissions Across all File Servers"
     It is important for you to understand that every member server of the DFS namespaces and replication need to be configured identically, with the same local drive letters and folder structures.  The data for the shares only needs to exist on one server to ensure it can be replicated across to the other member servers of the DFS namespaces.
 
-| **Permission Type** | **User / Group** | **Access Level** |
-| :--- | :--- | :--- |
-| Share | `Authenticated Users` | Full Control |
-| NTFS | `SYSTEM` | Full Control |
-| NTFS | `Share_Admins` | Full Control |
-| NTFS | *<Any Users / Groups That Need Access>* | Modify |
+| **Permission Type** | **User / Group** | **Access Level** | **Details** |
+| :--- | :--- | :--- | :--- |
+| Share | `Authenticated Users` | Full Control | This is to ensure that only domain authenticated users can access the share. |
+| NTFS | `SYSTEM` | Full Control | This is so DFS replication can properly function. |
+| NTFS | `Share_Admins` | Full Control | This is a security group I created for admins to manage the data on network shares unilaterally. |
+| NTFS | *<Any Users / Groups That Need Access>* | Modify | This is for anyone who needs access to these specific files / folders. |
 
 ### DFS Management 
 #### DFS Breakdown
 At this point, we need to create a DFS "Namespace".  This is basically a logical representation of either a single or a group of individual folders on one or more file servers.  The files and folders appear under a singular location like `\\bunny-lab.io\Projects\Scripting`.  In this example, `Projects` is the namespace (Its not a real folder with data), and `Scripting` is a folder replicated across one or more file servers, mapping to a real (generally hidden) network share like `\\LAB-FPS-01\Projects$\Scripting`.  In this example, there is a network share located at `Projects$` that (organizationally) correlates to the `Projects` DFS namespace, but you should not put files and folders in this root location, as it can cause issues or introduce potential corruption.
 
 #### DFS Configuration
-Now, we need to start working on actually setting up DFS now that the shares exist on both locations.
+Now, we need to start working on actually setting up DFS now that the shares exist (and are configured identically) on both locations.