Update TROUBLESHOOTING.md (#24192)

Author: rakshith91

sdk/monitor/azure-monitor-query/TROUBLESHOOTING.md

@@ -164,9 +164,8 @@ client.query_workspace(
 
 ### Troubleshooting partially successful logs query requests
 
-By default, if the execution of a Kusto query resulted in a partially successful response, the Azure Monitor Query
-client library will throw an exception to indicate to the user that the query was not fully successful. The data and
-the error can be accessed using the `partial_data` and `partial_error` fields.
+If the execution of a Kusto query resulted in a partially successful response, the Azure Monitor Query
+client library will return `partial_data` and `partial_error` indicating that the query was not fully successful.
 
 ```python
 response = client.query_workspace("{workspaceId}", "{kusto-query-string}", timespan="{timespan}")
@@ -211,4 +210,4 @@ As documented in the error message, the supported granularity for metrics querie
 ## Additional azure-core configurations
 
 When calling the methods, some properties including `retry_mode`, `timeout`, `connection_verify` can be configured by passing in as keyword arguments. See
-[configurations](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/core/azure-core/README.md#configurations) for list of all such properties.
+[configurations](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/core/azure-core/README.md#configurations) for list of all such properties.