Update outdated list-processes command on diagnostics tutorials doc

documentation/tutorial/app_is_leaking_memory_eventual_crash.md

@@ -13,7 +13,7 @@ Next, lets run the webapi (dotnet run) and before hitting the above URL that wil
 > dotnet-counters monitor --refresh-interval 1 -p 4807
 > ```
 
-4807 is the process identifier which can be found using dotnet-trace list-processes. The refresh-interval is the number of seconds before refreshes. 
+4807 is the process identifier which can be found using dotnet-trace ps. The refresh-interval is the number of seconds before refreshes.
 
 The output should be similar to the below:
 
@@ -45,7 +45,7 @@ Most commonly when analyzing possible memory leaks, we need access to as much of
 > sudo ./dotnet-dump collect -p 4807
 > ```
 
-4807 is the process identifier which can be found using dotnet-trace list-processes. The result is a core dump located in the same folder. Please note that to generate core dumps, dotnet-dump requires sudo.  
+4807 is the process identifier which can be found using dotnet-trace ps. The result is a core dump located in the same folder. Please note that to generate core dumps, dotnet-dump requires sudo.
 
 
 ### Analyzing the core dump

documentation/tutorial/app_running_slow_highcpu.md

@@ -13,7 +13,7 @@ Lets run the webapi (dotnet run) and before hitting the above URL that will caus
 > dotnet-counters monitor --refresh-interval 1 -p 22884
 > ```
 
-22884 is the process identifier which can be found using dotnet-trace list-processes. The refresh-interval is the number of seconds before refreshes. 
+22884 is the process identifier which can be found using dotnet-trace ps. The refresh-interval is the number of seconds before refreshes.
 
 The output should be similar to the below:
 
@@ -49,7 +49,7 @@ In order to generate profiler traces of a .net core application, we can use the
 > dotnet-trace collect -p 2266  --providers Microsoft-DotNETCore-SampleProfiler
 > ```
 
-2266 is the process identifier which can be found using dotnet-trace list-processes. Let dotnet-trace run for about 20-30 seconds and then hit enter to exit the collection. The result is a nettrace file located in the same folder. nettrace files are a great way to use existing analysis tools on Windows (such as PerfView) to diagnose performance problems. 
+2266 is the process identifier which can be found using dotnet-trace ps. Let dotnet-trace run for about 20-30 seconds and then hit enter to exit the collection. The result is a nettrace file located in the same folder. nettrace files are a great way to use existing analysis tools on Windows (such as PerfView) to diagnose performance problems.
 
 Alternatively, you can get the perf and LTTng trace data in nettrace format by using the perfcollect tool (please see Installing the tools section). Once installed, run the following command:
 

documentation/tutorial/hung_app.md

@@ -25,7 +25,7 @@ http://localhost:5000/api/diagscenario/deadlock
 Let the request run for about 10-15 seconds. The first thing we need in order to generate a core dump is to find the process identifier of our webapi process:
 
 > ```bash
-> $ dotnet-trace list-processes
+> $ dotnet-trace list-ps
 > ...
 > 80926 webapi     /home/marioh/webapi/bin/Debug/netcoreapp3.0/webapi
 > sudo dotnet triggerdump.dll 80926 500

documentation/tutorial/intermittent_memory_spike.md

@@ -15,7 +15,7 @@ Let's run the webapi (dotnet run) and before navigating to the above URL (specif
 > dotnet-counters monitor --refresh-interval 1 -p 4807
 > ```
 
-4807 is the process identifier which can be found using dotnet-trace list-processes. The refresh-interval is the number of seconds before refreshes. 
+4807 is the process identifier which can be found using dotnet-trace ps. The refresh-interval is the number of seconds before refreshes.
 
 The output should be similar to the below:
 
@@ -151,7 +151,7 @@ else
 We can now build the tool (dotnet build) and run it against our application. Once built, restart the test webapi, get the process id from dotnet-trace and run triggerdump:
 
 > ```bash
-> dotnet-trace list-processes
+> dotnet-trace ps
 > ...
 > 80926 webapi     /home/marioh/webapi/bin/Debug/netcoreapp3.0/webapi
 > sudo dotnet triggerdump.dll 80926 500