fixed small errors

Author: rkarlin

articles/sentinel/mulitple-tenants-service-providers.md renamed to articles/sentinel/multiple-tenants-service-providers.md

@@ -19,11 +19,11 @@ ms.author: rkarlin
 ---
 # Work with multiple tenants in Azure Sentinel 
 
-If you’re an managed security service provider (MSSP) and you’re using [Azure Lighthouse](../lighthouse/overview.md) to manage your customers’ security operations centers (SOC), you will be able to manage your customers’ Azure Sentinel resources without connecting directly to the customer’s tenant, from your own Azure tenant. 
+If you’re a managed security service provider (MSSP) and you’re using [Azure Lighthouse](../lighthouse/overview.md) to manage your customers’ security operations centers (SOC), you will be able to manage your customers’ Azure Sentinel resources without connecting directly to the customer’s tenant, from your own Azure tenant. 
 
 ## Prerequisites
 - [Onboard Azure Lighthouse](../lighthouse/how-to/onboard-customer.md)
-- For this to work properly, your tenant must be registered to the Azure Sentinel Resource Provider on at least one subscription. If you have a running Azure Sentinel in your tenant you are ready to get started. If not, in the Azure Portal, select **Subscriptions** followed by **Resource providers** and then search for `Microsoft.Security.Insights` and select **Register**.
+- For this to work properly, your tenant must be registered to the Azure Sentinel Resource Provider on at least one subscription. If you have a registered Azure Sentinel in your tenant, you are ready to get started. If not, in the Azure portal, select **Subscriptions** followed by **Resource providers** and then search for `Microsoft.Security.Insights` and select **Register**.
    ![Check resource providers](media/multiple-tenants-service-providers/check-resource-provider.png)
 ## How to access Azure Sentinel from other tenants
 1. Under **Directory + subscription**, select the delegated directories, and the subscriptions where your customer’s Azure Sentinel workspaces are located.

articles/sentinel/offboard.md

@@ -23,7 +23,7 @@ If you no longer want to use the Azure Sentinel, this article explains how to re
 
 ## How to delete Azure Sentinel
 
-In the background when you install Azure Sentinel, the **SecurityInsights** solution is installed on your selected workspace. So the first thing you need to do is remove the solution. In the Azure portal, you need to delete the SecurityInsights solution.
+In the background, when you install Azure Sentinel, the **SecurityInsights** solution is installed on your selected workspace. So the first thing you need to do is remove the solution. In the Azure portal, you need to delete the SecurityInsights solution.
 
 1.  Go to **Workspace settings** and then **Solutions**.
 
@@ -71,7 +71,7 @@ Within the first 48 hours, the data and alert rules (including real-time automat
 
 Your playbooks, saved workbooks, saved hunting queries, and notebooks are not deleted. **Some may brake due to the removed data. You can remove those manually.**
 
-From the time you remove the service, there is a grace period of 30 days during which you can re-enable the solution and your data and alert rules will be restored but the configured connectors that were disconnected must be reconnected.
+After you remove the service, there is a grace period of 30 days during which you can re-enable the solution and your data and alert rules will be restored but the configured connectors that were disconnected must be reconnected.
 
 > [!NOTE]
 > If you remove the solution, your subscription will continue to be registered with the Azure Sentinel resource provider. **You can remove it manually.**

articles/sentinel/roles.md

@@ -36,7 +36,7 @@ In addition to Azure Sentinel dedicated RBAC roles, there are Azure and Log Anal
 
 - **Azure roles:** [Owner](../role-based-access-control/built-in-roles.md#owner), [Contributor](../role-based-access-control/built-in-roles.md#contributor), and [Reader](../role-based-access-control/built-in-roles.md#reader). Azure roles grant access across all your Azure resources, including Log Analytics workspaces and Azure Sentinel resources.
 
--   **Log Analytics roles:** [Log Analytics contributor](..azure/role-based-access-control/built-in-roles.md#log-analytics-contributor), [Log Analytics reader](../role-based-access-control/built-in-roles.md#log-analytics-reader). Log Analytics roles grant access across all your Log Analytics workspaces. 
+-   **Log Analytics roles:** [Log Analytics contributor](../role-based-access-control/built-in-roles.md#log-analytics-contributor), [Log Analytics reader](../role-based-access-control/built-in-roles.md#log-analytics-reader). Log Analytics roles grant access across all your Log Analytics workspaces. 
 
 > [!NOTE]
 > Log Analytics roles also grant read access across all Azure resources but will only assign write permissions to Log Analytics resources.

articles/sentinel/tutorial-investigate-cases.md

@@ -70,7 +70,8 @@ To use the investigation graph:
 
 1. Select an incident, then select **Investigate**. This takes you to the investigation graph. The graph provides an illustrative map of the entities directly connected to the alert and each resource connected further.
 
-   > [!IMPORTANT] You'll only be able to investigate the incident if you used the entity mapping fields when you set up your analytic rule. The investigation graph requires that your original incident includes entities.
+   > [!IMPORTANT] 
+   > You'll only be able to investigate the incident if you used the entity mapping fields when you set up your analytic rule. The investigation graph requires that your original incident includes entities.
 
    ![View map](media/tutorial-investigate-cases/map1.png)