fix tables formatting

Author: Andra Mircioiu

content/minfraud/api-documentation/requests.md

@@ -278,9 +278,8 @@ transaction.
 
   {{< minfraud-schema-row key="type" type="request" valueType="string" valueTypeNote="format: enum" >}}
   The type of event being scored. The valid types are:
-
-  | Transaction type	                         | Description                                                                                          |
-  | ---------------------------- | ------------------------------------------------------------------------------------------------------ |
+  | Transaction type	                   | Description                                                                                          |
+  | ---------------------------- | ------------------------------------------------------------------- |
   | `account_creation`         | The transactor is attempting to create an account in your system.    |
   | `account_login`    | The transactor is attempting to log in to an account in your system.  |
   | `credit_application`              | The transactor is attempting to submit an application for credit. |
@@ -293,7 +292,6 @@ transaction.
   | `referral`  | The transactor is sending you referral traffic, for example referring someone to an e-commerce site with an ad. |
   | `sim_swap`  | For mobile network operators. A new SIM card or eSIM is being issued to activate service on a customer's existing phone number. |
   | `survey`  | The transactor is attempting to begin or complete a survey. |
-  
   [Learn more about the /event/type input on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/event-and-account-inputs-minfraud#transaction-identifier)
   {{</minfraud-schema-row>}}
 
@@ -549,7 +547,7 @@ process that was used for the event.
   {{< minfraud-schema-row key="method" type="request" valueType="string" valueTypeNote="format: enum" >}}
   The payment method associated with the transaction. The valid values are:
   | Payment method	                         | Description                                                                                          |
-  | ---------------------------- | ------------------------------------------------------------------------------------------------------ |
+  | ---------------------------- | ---------------- -------------------------------------------------- |
   | `bank_debit`                | A direct debit of the customer's bank account.    |
   | `bank_redirect`    | The customer authorizes payment after authentication via their bank.  |
   | `bank_transfer`              | The customer pushes funds directly from their bank account.  |
@@ -560,7 +558,6 @@ process that was used for the event.
   | `gift_card`  | Payment via a merchant sponsored gift card.   | 
   | `real_time_payment`  | The customer pushes funds directly from their bank account or other funding source using an intermediary to authenticate, such as a phone number or other account (e.g. Pix, PayNow, Swish, etc.).  | 
   | `rewards`  | Payment via rewards or loyalty program incentives. |
-
   [Learn more about event and account inputs on our Knowledge Base.](https://support.maxmind.com/knowledge-base/articles/event-and-account-inputs-minfraud)
 
 

content/minfraud/api-documentation/responses.md

@@ -992,16 +992,14 @@ minFraud response.
 
   {{< minfraud-schema-row key="status" type="response" valueType="string" insights="true" factors="true" >}}
   A classification of the status of the domain (or the last domain visited after following redirects, if these are present and can be followed) based on an automated visit at a previous point in time. This field may be initially unavailable for a newly sighted domain and populated at a future time after a visit is conducted. Pair with the `/email/domain/visit/last_visited_on` to determine the recency of the visit. One of the following values. Additional values may be added in the future.
-
 | Status                        | Description                                                                                          |
-  | ---------------------------- | ------------------------------------------------------------------------------------------------------ |
+  | ---------------------------- | ----------------------------------------------------------------- |
   | `live`                | The domain is reachable and serving content normally.    |
   | `dns_error`    | The domain is missing, expired, or DNS is misconfigured.  |
   | `network_error`              | The domain is offline, blocked, or unreachable.  |
   | `http_error`        | The domain is reachable but the web application had a problem or denied the request. |
   | `parked`            | The domain is live and is in a parked state. |
   | `pre_development` | The domain is live and is in a pre-development state.  |
-
   [Learn more about the email domain visit status on our Knowledge Base.](https://support.maxmind.com/knowledge-base/minfraud-domain-risk-data#domain-visit)
   {{</minfraud-schema-row>}}
 
@@ -1239,24 +1237,20 @@ then this object will not be present in the response.
 
   {{< minfraud-schema-row key="action" type="response" valueType="string" valueTypeNote="format: enum" score="true" insights="true" factors="true" >}}
   This describes how the request was handled. The valid values are:
-
   | Action         | Explanation                                                                            |
   | -------------- | -------------------------------------------------------------------------------------- |
   | `accept`         | This is the default value that is used if none of your custom rules match the request. |
   | `reject`         |                                                                                        |
   | `manual_review` |                                                                                        |
   | `test`           | This value can be used to test custom rules.                                           |
   {{</minfraud-schema-row>}}
-
   {{< minfraud-schema-row key="reason" type="response" valueType="string" valueTypeNote="format: enum" score="true" insights="true" factors="true" >}}
   This describes why the `action` was set to a particular value. The valid values are:
-
   | Reason       | Explanation                                   |
   | ------------ | --------------------------------------------- |
   | `default`      | No custom rules matched the request.          |
   | `custom_rule` | A custom rule was applied and set the action. |
   {{</minfraud-schema-row>}}
-
   {{< minfraud-schema-row key="rule_label" type="response" valueType="string" score="true" insights="true" factors="true" >}}
   The custom rule that was triggered. If you do not have custom rules set up, the triggered custom rule does not have a label, or no custom rule was triggered, the field will not be included in the response.
   {{</minfraud-schema-row>}}