chat/moderation: extract common fields for before-publish rules

Author: owenpearson

src/pages/docs/chat/moderation/custom/index.mdx

@@ -13,15 +13,7 @@ Before publish moderation is where your moderation logic is invoked before the m
 
 ### Integration configuration <a id="configuration"/>
 
-To fine-tune how Ably handles messages according to your use-case, you can configure before publish rule behavior using the following fields:
-
-| Field | Description |
-| ----- | ----------- |
-| Retry timeout | Maximum duration (in milliseconds) that an attempt to invoke the rule may take (including any retries). |
-| Max retries | Maximum number of retries after the first attempt at invoking the rule. |
-| Failed action | The action to take in the event that a rule fails to invoke. Options are reject the request or publish anyway. |
-| Too many requests action | The action to take if your endpoint returns `429 Too Many Requests`, which may happen if your endpoint is overloaded. The options are to fail moderation, or retry. |
-| Room filter (optional) | A regular expression to match to specific chat rooms. |
+To fine-tune how Ably handles messages according to your use-case, see the [common configuration fields](/docs/chat/moderation#common-config) shared across all before-publish moderation rules.
 
 ### The API <a id="api"/>
 

src/pages/docs/chat/moderation/direct/bodyguard.mdx

@@ -19,11 +19,8 @@ The following are the fields specific to Bodyguard configuration:
 | Channel ID | The ID of your Bodyguard channel where moderation rules are configured. |
 | Default Language (optional) | The default language to use for content analysis. This will be used as a fallback in case automatic language detection fails. |
 | Model URL (optional) | A custom URL if using a custom moderation model. |
-| Retry timeout | Maximum duration (in milliseconds) that an attempt to invoke the rule may take (including any retries). The possible range is 0 - 5000ms. |
-| Max retries | Maximum number of retries after the first attempt at invoking the rule. |
-| Failed action | The action to take in the event that a rule fails to invoke. Options are reject the request or publish anyway. |
-| Too many requests action | The action to take in the event that Bodyguard returns a 429 (Too Many Requests Response). Options are to fail rule invocation, or retry. |
-| Room filter (optional) | A regular expression to match to specific chat rooms. |
+
+For additional configuration options shared across all before-publish moderation rules, see the [common configuration fields](/docs/chat/moderation#common-config).
 
 Messages will be rejected if Bodyguard's analysis returns a `REMOVE` recommended action based on the moderation rules configured in your Bodyguard channel.
 

src/pages/docs/chat/moderation/direct/hive-model-only.mdx

@@ -18,11 +18,8 @@ The following are the fields specific to Hive (model only) configuration:
 | Hive API key | The API key for your Hive account. |
 | Thresholds | A map of text [text moderation classes](https://docs.thehive.ai/reference/text-moderation) to [severity](https://docs.thehive.ai/docs/detailed-class-descriptions-text-moderation). When moderating text, any message deemed to be at or above a specified threshold will be rejected and not published to the chat room. |
 | Model URL (optional) | A custom URL if using a custom moderation model. |
-| Retry timeout | Maximum duration (in milliseconds) that an attempt to invoke the rule may take (including any retries). The possible range is 0 - 5000ms. |
-| Max retries | Maximum number of retries after the first attempt at invoking the rule. |
-| Failed action | The action to take in the event that a rule fails to invoke. Options are reject the request or publish anyway. |
-| Too many requests action | The action to take in the event that Hive returns a 429 (Too Many Requests Response). Options are to fail rule invocation, or retry. |
-| Room filter (optional) | A regular expression to match to specific chat rooms. |
+
+For additional configuration options shared across all before-publish moderation rules, see the [common configuration fields](/docs/chat/moderation#common-config).
 
 ## Text length <a id="text-length"/>
 

src/pages/docs/chat/moderation/direct/tisane.mdx

@@ -19,11 +19,8 @@ The following are the fields specific to Tisane configuration:
 | Thresholds | A map of [text moderation categories](https://docs.tisane.ai/apis/tisane-api-response-guide#supported-types) to severity levels (`low`, `medium`, `high`, `extreme`). When moderating text, any message deemed to be at or above a specified threshold will be rejected and not published to the chat room. |
 | Default Language | The language to use for content analysis. |
 | Model URL (optional) | A custom URL if using a custom moderation model. |
-| Retry timeout | Maximum duration (in milliseconds) that an attempt to invoke the rule may take (including any retries). The possible range is 0 - 5000ms. |
-| Max retries | Maximum number of retries after the first attempt at invoking the rule. |
-| Failed action | The action to take in the event that a rule fails to invoke. Options are reject the request or publish anyway. |
-| Too many requests action | The action to take in the event that Tisane returns a 429 (Too Many Requests Response). Options are to fail rule invocation, or retry. |
-| Room filter (optional) | A regular expression to match to specific chat rooms. |
+
+For additional configuration options shared across all before-publish moderation rules, see the [common configuration fields](/docs/chat/moderation#common-config).
 
 ## Handling rejections <a id="rejections"/>
 

src/pages/docs/chat/moderation/index.mdx

@@ -19,6 +19,18 @@ When using before publish moderation, a message is reviewed by an automated mode
 
 This approach provides additional safety guarantees, but may come at the cost of a small amount of latency, as messages must be vetted prior to being published.
 
+#### Common Configuration Fields <a id="common-config"/>
+
+All before-publish moderation rules share the following configuration fields:
+
+| Field | Description |
+| ----- | ----------- |
+| Retry timeout | Maximum duration (in milliseconds) that an attempt to invoke the rule may take (including any retries). The possible range is 0 - 5000ms. |
+| Max retries | Maximum number of retries after the first attempt at invoking the rule. |
+| Failed action | The action to take in the event that a rule fails to invoke. Options are reject the request or publish anyway. |
+| Too many requests action | The action to take in the event that the moderation provider returns a 429 (Too Many Requests Response). Options are to fail rule invocation, or retry. |
+| Room filter (optional) | A regular expression to match to specific chat rooms. |
+
 ### After publish <a id="after-publish"/>
 
 When using after publish moderation, a message is published as normal, but is forwarded to a moderation engine after the fact. This enables you to avoid the latency penalty of vetting content prior to publish, at the expense of bad content being visible in the chat room (at least briefly). Many automated moderation solutions are able to process and delete offending messages within a few seconds of publication.