Document failed_request_status_codes option better

Author: antonpirker

docs/platforms/python/integrations/fastapi/index.mdx

@@ -134,6 +134,9 @@ You can pass the following keyword arguments to `StarletteIntegration()` and `Fa
 
   A `set` of integers that will determine which status codes should be reported to Sentry.
 
+  The `failed_request_status_codes` option only controls whether [`HTTPException`](https://www.starlette.io/exceptions/#httpexception) exceptions should be
+  reported to Sentry. Other unhandled exceptions, which do not have a `status_code` attribute, are always reported to Sentry.
+
   Examples of valid `failed_request_status_codes`:
 
   - `{500}` will only send events on HTTP 500.

docs/platforms/python/integrations/starlette/index.mdx

@@ -91,6 +91,9 @@ You can pass the following keyword arguments to `StarletteIntegration()`:
 
   A `set` of integers that will determine which status codes should be reported to Sentry.
 
+  The `failed_request_status_codes` option only controls whether [`HTTPException`](https://www.starlette.io/exceptions/#httpexception) exceptions should be
+  reported to Sentry. Other unhandled exceptions, which do not have a `status_code` attribute, are always reported to Sentry.
+
   Examples of valid `failed_request_status_codes`:
 
   - `{500}` will only send events on HTTP 500.