Update error code 429 description with rate limit info

Author: DebLanger

exposure-management/crowdstrike-data-connector.md

@@ -76,7 +76,7 @@ Here are some common issues that might arise when configuring the CrowdStrike Co
 | **Error code 401**: Authorization failure                    | An authorization failure indicates that credentials might not be correct, or there might not be sufficient permissions to access the CrowdStrike data. Check your credentials and make sure they're correct and valid. Also check that your API client has the required permissions. See the CrowdStrike [configuration section](#crowdstrike-falcon-configuration) for details on how to generate the appropriate API client with correct scopes. <br>You can validate your credentials by testing the authentication endpoint with your API client credentials. |
 | **Error code 403:** Access forbidden error                   | This error indicates that the provided credentials lack the necessary permissions to run the requested APIs. Update your credentials with the proper permissions as described in the [configuration section](#crowdstrike-falcon-configuration), and make sure your API client has the **Assets (Read)** and **Vulnerabilities (Read)** permissions. |
 | **Error code 404:** Not found error                          | This error indicates that the requested endpoint wasn't found to be reachable. Verify that your CrowdStrike API Base URL is correct, see the [configuration section](#crowdstrike-falcon-configuration) for details. |
-| **Error code 429** 'Too many requests"                       | The system periodically pulls data from the configured external providers, which might have a limit on the number of concurrent requests. We recommend creating a dedicated API client for the connector to avoid reaching this limit. |
+| **Error code 429** 'Too many requests"                       | The system periodically pulls data from the configured external providers, which might have a limit on the number of concurrent requests. We recommend creating a dedicated API client for the connector to avoid reaching this limit. Make sure you have enough Remaining Rate Limit for api calls. This can be check on the response headers from CrowdStrike API, **X-Ratelimit-Remaining**.|
 | 'Temporary disconnected' or 'Temporary failure' error message | In the case where this error message appears without any additional information, verify the connector configuration (API Base URL and credentials). If these are valid and the issue doesn't resolve on its own, contact Support. |
 | Not seeing my assets or the vulnerabilities reported by CrowdStrike in the ingested data | See [Retrieved data](#retrieved-data) for a description of the data expected to be retrieved by the CrowdStrike connector. If there's still missing data, contact Support. |
 | CrowdStrike allowed IPs need to be configured to enable Exposure Management connectors to access CrowdStrike | Read how to add the set of IPs to add to your allowlist here: [Allowlist IP addresses](configure-data-connectors.md#allowlist-ip-addresses). |