cleanup prereqs a bit

Author: austinmccollum

articles/sentinel/ci-cd-custom-content.md

@@ -27,11 +27,11 @@ The Microsoft Sentinel repositories feature provides a central experience for th
 Microsoft Sentinel repositories require careful planning to ensure you have the proper permissions from your workspace to the repository (repo) you want connected. 
 
 - Only connections to GitHub and Azure DevOps repositories are supported.
-- Contributor access to the repository is required. 
+- Collaborator access to your GitHub repository or Project Administrator access to your Azure DevOps repository is required. 
 - The Microsoft Sentinel application needs authorization to your repo.
 - Actions must be enabled for GitHub.
 - Pipelines must be enabled for Azure DevOps.
-- An Azure DevOps connection must be in the same tenant as your Microsoft Sentinel workspace
+- An Azure DevOps connection must be in the same tenant as your Microsoft Sentinel workspace.
 
 Creating a connection to a repository requires an **Owner** role in the resource group that contains your Microsoft Sentinel workspace. If you're unable to use the Owner role in your environment, use the combination of **User Access Administrator** and **Sentinel Contributor** roles to create the connection.
 

articles/sentinel/ci-cd-custom-deploy.md

@@ -29,16 +29,16 @@ There are two primary ways to customize the deployment of your repository conten
 > The Microsoft Sentinel **Repositories** feature is currently in **PREVIEW**. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for more legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
 
 
-## Prerequisites and scope
+## Prerequisites
 
-Microsoft Sentinel supports connections to GitHub and Azure DevOps repositories. Before connecting your Microsoft Sentinel workspace to your source control repository, make sure that you have:
+In order to customize a repositories deployment, a repository connection must exist. For more information on creating the connection, see [Deploy custom content from your repository](ci-cd.md#prerequisites).
+After the connection is made, the following prerequisites apply:
 
-- An **Owner** role in the resource group that contains your Microsoft Sentinel workspace *or* a combination of **User Access Administrator** and **Sentinel Contributor** roles to create the connection
 - Collaborator access to your GitHub repository or Project Administrator access to your Azure DevOps repository
 - Actions enabled for GitHub and Pipelines enabled for Azure DevOps
 - Ensure custom content files you want to deploy to your workspaces are in a supported format. For supported formats, see [Plan your repository content](ci-cd-custom-content.md#plan-your-repository-content).
 
-For more information, see [Validate your content](ci-cd-custom-content.md#validate-your-content).
+For more information on deployable content types, see [Validate your content](ci-cd-custom-content.md#validate-your-content).
 
 ## Customize the workflow or pipeline
 

articles/sentinel/ci-cd.md

@@ -24,7 +24,7 @@ When creating custom content, you can manage it from your own Microsoft Sentinel
 > - The Microsoft Sentinel **Repositories** feature is currently in **PREVIEW**. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
 > - [!INCLUDE [unified-soc-preview](includes/unified-soc-preview-without-alert.md)]
 
-## Prerequisites and scope
+## Prerequisites
 
 Microsoft Sentinel currently supports connections to GitHub and Azure DevOps repositories. Before connecting your Microsoft Sentinel workspace to your source control repository, make sure that you have:
 
@@ -35,7 +35,7 @@ Microsoft Sentinel currently supports connections to GitHub and Azure DevOps rep
 - An Azure DevOps connection must be in the same tenant as your Microsoft Sentinel workspace
 - Ensure custom content files you want to deploy to your workspaces are in a supported format. For supported formats, see [Plan your repository content](ci-cd-custom-content.md#plan-your-repository-content).
 
-For more information, see [Validate your content](ci-cd-custom-content.md#validate-your-content).
+For more information on deployable content types, see [Validate your content](ci-cd-custom-content.md#validate-your-content).
 
 ## Connect a repository