Add information about crash reports

Author: heitortsergent

docs/sources/k6-studio/introduction.md

@@ -16,8 +16,8 @@ For users that have less experience with JavaScript or k6, k6 Studio can help yo
 
 The k6 Studio desktop application consists of three components:
 
-- **Test Recorder**: The Test Recorder can help you generate a HAR file. When you start a recording, the application uses a proxy recorder and launches an instance of Chrome, and records the traffic from your actions on the browser.
-- **Test Generator**: The Test Generator takes the output of a test recording and gives you options to customize the test with a visual interface and generate a test script from it. You can use it to define a list of hosts to allow or remove from your script, include variables in your script, and configure rules to extract values, parameterize requests, and more.
+- **Test Recorder**: The Test Recorder can help you generate a HAR file. When you start a recording, the application uses a proxy recorder and launches an instance of Google Chrome, and records the traffic from your actions on the browser.
+- **Test Generator**: The Test Generator takes the output of a test recording and gives you options to customize the test with a visual interface and generate a test script from it. You can use it to define a list of hosts to allow or remove from your script, include variables or data files in your script, and configure rules to extract values, parameterize requests, and more.
 - **Test Validator**: The Test Validator can help you validate that a test script is working as expected. You can use it to run one iteration of your test, and visualize the request and response of any requests on your test script. The Test Validator works with any k6 test script, not only scripts generated via the Test Generator.
 
 After you create a test script using the Test Generator, you can use that same script to run a load test using the k6 CLI or in Grafana Cloud k6, and start getting more information about how well your systems or applications are performing.

docs/sources/k6-studio/set-up/settings.md

@@ -31,8 +31,12 @@ There are two configuration options for proxy mode:
 
 If you choose the **Upstream** mode, you have to configure a **Server URL** value, and you can optionally provide authentication credentials and a certificate file.
 
-## Usage report
+## Telemetry
 
 ### Send anonymous usage data
 
 k6 Studio sends anonymous usage data of the k6 Studio application to Grafana. This is enabled by default, and you can turn it off if you'd like not to send any data. Refer to [Usage collection](https://grafana.com/docs/k6-studio/set-up/usage-collection/) for more details.
+
+### Send crash reports and error data
+
+k6 Studio sends anonymous crash reports and error data of the k6 Studio application to Grafana. This is enabled by default, and you can turn it off if you'd like not to send any data. Refer to [Usage collection](https://grafana.com/docs/k6-studio/set-up/usage-collection/) for more details.

docs/sources/k6-studio/set-up/usage-collection.md

@@ -6,12 +6,12 @@ weight: 300
 
 # Usage collection
 
-By default, k6 Studio sends an anonymous usage report so that we can track how users are using the product and its features. We use that information to prioritize the roadmap with the features that will benefit a majority of users, and reduce the impact of any changes we make.
+By default, k6 Studio sends an anonymous usage report, and crash reports and error data, so that we can track how users are using the product and its features. We use that information to prioritize the roadmap with the features that will benefit a majority of users, and reduce the impact of any changes we make.
 
-The usage report doesn't contain any information about you or what you are testing. The contents included in the report are:
+The data doesn't contain any information about you or what you are testing. The contents included in the report are:
 
-- The running program’s operating system (`mac` or `win`).
-- The running program’s architecture (`arm64` or `x86_64`).
+- The running program's operating system (`mac` or `win`).
+- The running program's architecture (`arm64` or `x86_64`).
 - The k6 Studio version (for example, `0.4.0`).
 - The timestamp of when the data was collected (for example, `2024-10-22T16:02:56.261Z`).