diff --git a/TraceScripts/README.md b/TraceScripts/README.md
index da6b4d5..337214d 100644
--- a/TraceScripts/README.md
+++ b/TraceScripts/README.md
@@ -7,9 +7,17 @@ Please follow the instructions below to capture trace logs generated by PlayFab
 - Open an administrator command prompt or powershell session
     - the script is unsigned, so unless your powershell is setup to with an "Unrestricted" execution policy, you will have to pass that along as well.
 - Run the `Trace-PlayFabParty.ps1` script. The script requires one parameter which is a label to describe the trace attempt, for example "try1", e.g.:
-```
-powershell -ExecutionPolicy Unrestricted .\Trace-PlayFabParty.ps1 try1
-```
+
+    ```
+    powershell -ExecutionPolicy Unrestricted .\Trace-PlayFabParty.ps1 try1
+    ```
+    
+    - If you need more low-level connectivity information, add `-IncludeTransport` switch.
+
+    ```
+    powershell -ExecutionPolicy Unrestricted .\Trace-PlayFabParty.ps1 try1 -IncludeTransport
+    ```
+
 - Run your game and get into the state to reproduce the issue
 - Hit enter in the command prompt to stop the trace. It will tell you the name of the generated `.etl` file which contains the trace