add more details to inbound filters integration page.

src/includes/platforms/configuration/options/allow-urls.mdx

@@ -0,0 +1 @@
+A list of strings or regex patterns that match error URLs which should exclusively be sent to Sentry. If you use this option, only errors whose entire file URL contains (string) or matches (regex) at least one entry in the list will be sent. As a result, if you add `'foo.com'` to it, it will also match on `https://bar.com/myfile/foo.com`. Keep in mind that this only applies for captured exceptions, not raw message events. By default, all errors are sent.

src/includes/platforms/configuration/options/deny-urls.mdx

@@ -0,0 +1 @@
+A list of strings or regex patterns that match error URLs that should not be sent to Sentry. Errors whose entire file URL contains (string) or matches (regex) at least one entry in the list will not be sent. As a result, if you add `'foo.com'` to the list, it will also match on `https://bar.com/myfile/foo.com`. Keep in mind that this only applies for captured exceptions, not raw message events. By default, all errors are sent.

src/includes/platforms/configuration/options/ignore-errors.mdx

@@ -0,0 +1 @@
+A list of strings or regex patterns that match error messages that shouldn't be sent to Sentry. Messages that match these strings or regular expressions will be filtered out before they're sent to Sentry. When using strings, partial matches will be filtered out, so if you need to filter by exact match, use regex patterns instead. By default, all errors are sent.

src/includes/platforms/configuration/options/ignore-transactions.mdx

@@ -0,0 +1 @@
+A list of strings or regex patterns that match transaction names that shouldn't be sent to Sentry. Transactions that match these strings or regular expressions will be filtered out before they're sent to Sentry. When using strings, partial matches will be filtered out, so if you need to filter by exact match, use regex patterns instead. By default, all transactions are sent.

src/platforms/common/configuration/options.mdx

@@ -282,25 +282,25 @@ For ASP.NET and ASP.NET Core applications, the value will default to the server'
 
 <ConfigKey name="ignore-errors" supported={["javascript", "node"]} notSupported={[]}>
 
-A list of strings or regex patterns that match error messages that shouldn't be sent to Sentry. Messages that match these strings or regular expressions will be filtered out before they're sent to Sentry. When using strings, partial matches will be filtered out, so if you need to filter by exact match, use regex patterns instead. By default, all errors are sent.
+<Include name="platforms/configuration/options/ignore-errors.mdx" />
 
 </ConfigKey>
 
 <ConfigKey name="ignore-transactions" supported={["javascript", "node"]} notSupported={[]}>
 
-A list of strings or regex patterns that match transaction names that shouldn't be sent to Sentry. Transactions that match these strings or regular expressions will be filtered out before they're sent to Sentry. When using strings, partial matches will be filtered out, so if you need to filter by exact match, use regex patterns instead. By default, all transactions are sent.
+<Include name="platforms/configuration/options/ignore-transactions.mdx" />
 
 </ConfigKey>
 
 <ConfigKey name="deny-urls" supported={["javascript"]} notSupported={["node"]}>
 
-A list of strings or regex patterns that match error URLs that should not be sent to Sentry. Errors whose entire file URL contains (string) or matches (regex) at least one entry in the list will not be sent. As a result, if you add `'foo.com'` to the list, it will also match on `https://bar.com/myfile/foo.com`. By default, all errors are sent.
+<Include name="platforms/configuration/options/deny-urls.mdx" />
 
 </ConfigKey>
 
 <ConfigKey name="allow-urls" supported={["javascript"]} notSupported={["node"]}>
 
-A list of strings or regex patterns that match error URLs which should exclusively be sent to Sentry. If you use this option, only errors whose entire file URL contains (string) or matches (regex) at least one entry in the list will be sent. As a result, if you add `'foo.com'` to it, it will also match on `https://bar.com/myfile/foo.com`. By default, all errors are sent.
+<Include name="platforms/configuration/options/allow-urls.mdx" />
 
 </ConfigKey>
 

src/platforms/javascript/common/configuration/integrations/inboundfilters.mdx

@@ -13,5 +13,33 @@ message, or URLs in a given exception.
 By default, it'll ignore errors that start with `Script error` or `Javascript error: Script error`.
 
 To configure this integration, use the `ignoreErrors`, `ignoreTransactions`, `denyUrls`,
-and `allowUrls` SDK options directly. Keep in mind that `denyURLs` and `allowURLs`
-only work for captured exceptions not raw message events.
+and `allowUrls` SDK options directly. For example:
+
+```javascript
+Sentry.init({
+  ignoreErrors: ["ignore-this-error"],
+});
+```
+
+## Options
+
+<Note>
+  Remember to pass these options to the root Sentry.init call, not the
+  integration!
+</Note>{" "}
+
+- `ignoreErrors` (array)
+
+<Include name="platforms/configuration/options/ignore-errors.mdx" />
+
+- `ignoreTransactions` (array)
+
+<Include name="platforms/configuration/options/ignore-transactions.mdx" />
+
+- `denyUrls` (array)
+
+<Include name="platforms/configuration/options/deny-urls.mdx" />
+
+- `allowUrls` (array)
+
+<Include name="platforms/configuration/options/allow-urls.mdx" />