Updating doc to include path to built demo tools (#34)

docs/demos.md

@@ -12,7 +12,7 @@ These demos showcase three main features of the sandbox: reporting file accesses
 This demo is able to run an arbitrary process and report back all the file accesses that the process (and its child processes) made. For example, one can run:
 
 ```
-E:\temp>dotnet ReportAccesses.dll notepad myFile.txt
+E:\temp>dotnet <repo_root>\bin\[Debug|Release]\ReportAccesses.dll notepad myFile.txt
 ```
 
 This will actually open notepad.exe and myFile.txt will be created. After exiting notepad, the tool reports:
@@ -96,7 +96,7 @@ E:\TEST
 
 And let's see what happens if we run:
 
-```dotnet BlockAccesses.dll e:\test e:\test\bin e:\test\obj```
+```dotnet <repo_root>\bin\[Debug|Release]\BlockAccesses.dll e:\test e:\test\bin e:\test\obj```
 
 Here we are trying to enumerate ``e:\test`` recursively, but block any access under ``e:\test\obj`` and ``e:\test\bin``. The result is:
 
@@ -175,7 +175,7 @@ The last demo shows how the sandbox can be used to retrieve the process tree of
 
 For example, let's run a git fetch on an arbitrary repo:
 
-```dotnet ProcessTree.dll git fetch```
+```dotnet <repo_root>\bin\[Debug|Release]\ProcessTree.dll git fetch```
 
 The result is: