Windows guide edits

Author: sus-admin

_posts/2025-04-14-Cobbler-v3.3.7-Windows-Deployment-Guide.md

@@ -156,7 +156,7 @@ cobbler sync
 
 The **PXE Client** VM can now be powered on, and should automatically boot to PXE and install Windows 10 to the VM HDD using the "autounattended.xml" answerfile template.
 
-    - See the Tips & Troubleshooting section below for a fix for an issue encountered on the PXE client during the start-net.cmd script on both VirualBox and VMWare VMs
+- See the Tips & Troubleshooting section below for a fix for an issue encountered on the PXE client during the start-net.cmd script on both VirualBox and VMWare VMs
 
 ## Windows 11 PXE Deployment
 
@@ -186,7 +186,7 @@ cobbler sync
 
 The **PXE Client** VM can now be powered on, and should automatically boot to PXE and install Windows 11 to the VM HDD using the "autounattended.xml" answerfile template.
 
-    - See the Tips & Troubleshooting section below for a fix for an issue encountered on the PXE client during the start-net.cmd script on both VirualBox and VMWare VMs
+- See the Tips & Troubleshooting section below for a fix for an issue encountered on the PXE client during the start-net.cmd script on both VirualBox and VMWare VMs
 
 ## Tips & Troubleshooting
 
@@ -226,7 +226,9 @@ The **PXE Client** VM can now be powered on, and should automatically boot to PX
 
     - The `smb` linux service used to host the installation files for the PXE client  on the Cobbler server would be unresponsive during some installations, primarily when running the `startnet.cmd` script on the PXE client to start Windows Setup, which caused the installation to stall and error-out occasionally.
 
-        - After reading through the manpage (`man smb.conf`) and trying several different configurations the problem persisted; make the following edit to the `startnet.template` file to account for this occasional unresponsiveness/lag from the SMB server when booting into setup by first probing the SMB share until it responds.
+        - After reading through the manpage (`man smb.conf`) and trying several different configurations the problem persisted
+
+        - Make the following edit to the `startnet.template` file to account for this occasional unresponsiveness/lag from the SMB server when booting into setup by first probing the SMB share until it responds.
 
           ```shell
           CMD=$(echo 'dir \$distros_dir || GOTO wno20' | unix2dos)