merge conflicts

Author: batamig

articles/sentinel/automation/create-playbooks.md

@@ -94,7 +94,7 @@ Do the following to create your playbook:
 
     :::image type="content" source="../media/tutorial-respond-threats-playbook/logic-app-blank.png" alt-text="Screenshot of logic app designer screen with opening trigger." lightbox="../media/tutorial-respond-threats-playbook/logic-app-blank.png":::
 
-1. If you chose the **Microsoft Sentinel entity (Preview)** trigger, select the type of entity you want this playbook to receive as an input.
+1. If you chose the **Microsoft Sentinel entity** trigger, select the type of entity you want this playbook to receive as an input.
 
     :::image type="content" source="../media/tutorial-respond-threats-playbook/entity-trigger-types.png" alt-text="Screenshot of drop-down list of entity types to choose from to set playbook schema.":::
 

articles/sentinel/automation/playbook-triggers-actions.md

@@ -35,7 +35,7 @@ For more information, see [Roles and permissions in Microsoft Sentinel](../roles
 
 The Microsoft Sentinel connector, and therefore Microsoft Sentinel playbooks, support the following triggers:
 
-- **Microsoft Sentinel incident (Preview)**. Recommended for most incident automation scenarios.
+- **Microsoft Sentinel incident**. Recommended for most incident automation scenarios.
 
     The playbook receives incident objects, including both entities and alerts. This trigger allows you to attach a playbook to an automation rule that can be triggered whenever an incident is created or updated in Microsoft Sentinel, applying all the [benefits of automation rules](../automate-incident-handling-with-automation-rules.md) to the incident.
 
@@ -44,7 +44,7 @@ The Microsoft Sentinel connector, and therefore Microsoft Sentinel playbooks, su
     - This trigger can't be used to automate responses for alerts generated by *Microsoft security* analytics rules.
     - Playbooks using this trigger can't be called by automation rules.
 
-- **Microsoft Sentinel entity (Preview)**. Recommended for playbooks that must be run manually on specific entities from an investigation or threat hunting context. Playbooks using this trigger can't be called by automation rules.
+- **Microsoft Sentinel entity**. Recommended for playbooks that must be run manually on specific entities from an investigation or threat hunting context. Playbooks using this trigger can't be called by automation rules.
 
 The schemas used by these flows aren't identical. We recommend using the **Microsoft Sentinel incident trigger** flow for most scenarios.