Merge pull request #8300 from microsoft/telemetry

Update instructions for showing telemetry events

Author: ntrogh

docs/configure/telemetry.md

@@ -32,16 +32,14 @@ With the `setting(telemetry.telemetryLevel)` user [setting](/docs/configure/sett
 | crash |            ✓          |        -        |        -       |
 | off   |            -          |        -        |        -       |
 
-For example, if you don't want to send any telemetry data to Microsoft, you can set the `setting(telemetry.telemetryLevel)` user [setting](/docs/configure/settings.md) to `off`.
-
-From **File** > **Preferences** > **Settings**, search for `telemetry`, and set the **Telemetry: Telemetry Level** setting to `off`. This will silence all telemetry events from VS Code going forward. Telemetry information may have been collected and sent up until the point when you disable the setting.
+For example, if you don't want to send any telemetry data to Microsoft, you can set the `setting(telemetry.telemetryLevel)` user [setting](/docs/configure/settings.md) to `off`. This will silence all telemetry events from VS Code going forward. Note that telemetry information may have been collected and sent up until the point when you disable the setting.
 
 ![disable telemetry](images/telemetry/disable-telemetry.png)
 
 If you use the JSON editor for your settings, add the following line:
 
 ```json
-    "telemetry.telemetryLevel": "off"
+"telemetry.telemetryLevel": "off"
 ```
 
 ## Extensions and telemetry
@@ -52,14 +50,16 @@ Extension authors may refer to the ["For Extension Authors"](#for-extension-auth
 
 ## Output channel for telemetry events
 
-If you'd like to review the telemetry events in VS Code as they are sent, you can enable tracing and it will record telemetry events. Using the **Developer: Set Log Level...** command and select log level **Trace**.  To view the logging output, go to the Output panel (`kb(workbench.action.output.toggleOutput)`) and pick **Telemetry** from the dropdown.
+To review the telemetry events in VS Code as they are sent, run the **Developer: Show Telemetry** command from the Command Palette (`kb(workbench.action.showTelemetry)`). This command enables tracing for telemetry events and opens the **Telemetry** output channel in the Output panel (`kb(workbench.action.output.toggleOutput)`). As telemetry events are sent, the output channel shows the event details.
 
 ![output panel log telemetry](images/telemetry/output-log-telemetry.png)
 
-When tracing telemetry events, the events are also logged to a local file `telemetry.log`, which you can view using the **Developer: Open Log File...** command and choosing **Telemetry** from the dropdown.
+When tracing telemetry events, the events are also logged to a local file `telemetry.log`, which you can view using the **Developer: Open Log...** command and choosing **Telemetry** from the dropdown.
 
 ![open telemetry log file](images/telemetry/open-telemetry-log.png)
 
+To disable tracing telemetry events, reload the VS Code window (**Developer: Reload Window** command).
+
 ## Viewing all telemetry events
 
 If you'd like to view all the possible telemetry events that VS Code could send, you can use the `--telemetry` flag in the CLI. This will generate a JSON report that you can then view within VS Code. These reports are generated per build and do not contain extension telemetry unless the extension author adds a `telemetry.json` file to their root build directory.