Update Workflows/Windows/Windows Server/Roles/DFS/Creating and Configuring DFS Namespaces with Replication.md

Workflows/Windows/Windows Server/Roles/DFS/Creating and Configuring DFS Namespaces with Replication.md

@@ -25,10 +25,10 @@ Create (or identify) the folders you want to publish in the namespace, and share
 Additionally, it is recommended (if possible) to set the share names to be hidden.  For example `\\LAB-FPS-01\Projects$`, that way it ensures that users access the share via DFS at `\\bunny-lab.io\Projects` and users don't accidentally access the file servers directly, bypassing DFS.  For example, the local path would be `Z:\Projects` but the network share would be `\\LAB-FPS-01\Projects$`.  *This wouldn't break things like replication, but it would muck things up a little bit organizationally.*
 
 !!! warning "What must match vs. what can differ"
-- **Must exist on each server:** a shared folder to act as the *folder target* (path can differ per server).
-- **Share permissions:** are **not replicated**; set them on each server.
-- **NTFS permissions inside the replicated folder:** **are replicated** by DFSR and should be consistent.
-- Targets do **not** have to use identical share names/paths, but keeping them consistent simplifies things.
+    - **Must exist on each server:** a shared folder to act as the *folder target* (path can differ per server).
+    - **Share permissions:** are **not replicated**; set them on each server.
+    - **NTFS permissions inside the replicated folder:** **are replicated** by DFSR and should be consistent.
+    - Targets do **not** have to use identical share names/paths, but keeping them consistent simplifies things.
 
 | **Permission Type** | **User / Group** | **Access** | Level** |
 | :---- | :---- | :---- | :---- |