Fix table issues

Author: ecfan

articles/logic-apps/logic-apps-examples-and-scenarios.md

@@ -26,16 +26,16 @@ Every workflow starts with a single [*trigger*](logic-apps-overview.md#logic-app
 
 | Trigger | Description | More information |
 |---------|-------------|------------------|
-| [**Recurrence** trigger](../connectors/connectors-native-recurrence.md) | Set the recurrence for running your workflow, including the start date and time. For example, you can select the days of the week and times of day. | * [Schedule and run recurring automated tasks, processes, and workflows with Azure Logic Apps](concepts-schedule-automated-recurring-tasks-workflows.md) <br><br>* [Tutorial: Create automated, schedule-based recurring workflows by using Azure Logic Apps](tutorial-build-schedule-recurring-logic-app-workflow.md) |
-| **When an email is received** | Check for new email from any mail provider that's supported by Azure Logic Apps, for example, [Office 365 Outlook](../connectors/connectors-create-api-office365-outlook.md), [Gmail](/connectors/gmail/), [Outlook.com](/connectors/outlook/), and so on. | **Important*: If you want to use the Gmail connector, only G-Suite business accounts can use this connector without restriction in Azure Logic Apps. If you have a Gmail consumer account, you can use this connector with only specific Google-approved services, or you can [create a Google client app to use for authentication with your Gmail connector](/connectors/gmail/#authentication-and-bring-your-own-application). For more information, see [Data security and privacy policies for Google connectors in Azure Logic Apps](../connectors/connectors-google-data-security-privacy-policy.md). <br><br>For tutorials about email-related triggers, see the following documentation: <br><br>* [Tutorial: Create automated approval-based workflows by using Azure Logic Apps](tutorial-process-mailing-list-subscriptions-workflow.md) <br><br>* [Tutorial: Automate tasks to process emails by using Azure Logic Apps, Azure Functions, and Azure Storage](tutorial-process-email-attachments-workflow.md)
+| [**Recurrence** trigger](../connectors/connectors-native-recurrence.md) | Set the recurrence for running your workflow, including the start date and time. For example, you can select the days of the week and times of day. | - [Schedule and run recurring automated tasks, processes, and workflows with Azure Logic Apps](concepts-schedule-automated-recurring-tasks-workflows.md) <br><br>- [Tutorial: Create automated, schedule-based recurring workflows by using Azure Logic Apps](tutorial-build-schedule-recurring-logic-app-workflow.md) |
+| **When an email is received** | Check for new email from any mail provider that's supported by Azure Logic Apps, for example, [Office 365 Outlook](../connectors/connectors-create-api-office365-outlook.md), [Gmail](/connectors/gmail/), [Outlook.com](/connectors/outlook/), and so on. | **Important**: If you want to use the Gmail connector, only G-Suite business accounts can use this connector without restriction in Azure Logic Apps. If you have a Gmail consumer account, you can use this connector with only specific Google-approved services, or you can [create a Google client app to use for authentication with your Gmail connector](/connectors/gmail/#authentication-and-bring-your-own-application). For more information, see [Data security and privacy policies for Google connectors in Azure Logic Apps](../connectors/connectors-google-data-security-privacy-policy.md). <br><br>For tutorials about email-related triggers, see the following documentation: <br><br>- [Tutorial: Create automated approval-based workflows by using Azure Logic Apps](tutorial-process-mailing-list-subscriptions-workflow.md) <br><br>- [Tutorial: Automate tasks to process emails by using Azure Logic Apps, Azure Functions, and Azure Storage](tutorial-process-email-attachments-workflow.md)
 | [**HTTP** trigger](../connectors/connectors-native-http.md) | Call a service endpoint over HTTP or HTTPS. | [Call, trigger, or nest workflows by using HTTP endpoints](logic-apps-http-endpoint.md) |
 
 ### Push trigger examples
 
-| Trigger | Description | More information |
-|---------|-------------|------------------|
-| [**Request** trigger](../connectors/connectors-native-reqres.md) | Receive incoming HTTPS requests. ||
-| [**HTTP Webhook** trigger](../connectors/connectors-native-webhook.md) | Subscribe to a service endpoint by registering a *callback URL* with that service. That way, the service can just notify the trigger when the specified event happens, so that the trigger doesn't need to poll the service. ||
+| Trigger | Description |
+|---------|-------------|
+| [**Request** trigger](../connectors/connectors-native-reqres.md) | Receive incoming HTTPS requests. |
+| [**HTTP Webhook** trigger](../connectors/connectors-native-webhook.md) | Subscribe to a service endpoint by registering a *callback URL* with that service. That way, the service can just notify the trigger when the specified event happens, so that the trigger doesn't need to poll the service. |
 
 After you add the trigger, continue building your workflow by adding one or more actions. The following quickstarts help you build your first Consumption logic app workflow, which runs in global, multi-tenant Azure Logic Apps: