merge comments from PM and diag

Author: austinmccollum

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

@@ -93,7 +93,7 @@ Once the workflow or pipeline is triggered, the deployment supports the followin
 - exclude content from deployment
 - specify ARM template parameter files 
 
-These options are available through a feature of the PowerShell deployment script called from the workflow or pipeline. For more details on how to implement these customizations, see [Customize repository deployments](ci-cd-custom-deploy.md#customize-the-deployment).
+These options are available through a feature of the PowerShell deployment script called from the workflow or pipeline. For more details on how to implement these customizations, see [Customize repository deployments](ci-cd-custom-deploy.md#customize-your-connection-configuration).
 
 
 ## Next steps

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

@@ -36,9 +36,9 @@ For more information, see [Validate your content](ci-cd-custom-content.md#valida
 
 ## Customize the workflow or pipeline
 
-Smart deployments are enabled here by default. This ensures only content that has been modified since the last deployment, based on commits to the repository, is deployed to Sentinel. Customization for the workflow or pipeline is defined in a .yml file.
+The default workflow only deploys content that has been modified since the last deployment based on commits to the repository. But you may want to turn off smart deployments or perform other customizations. For example, you can configure different deployment triggers, or deploy content exclusively from a specific root folder.
 
-Select one of the following tabs depending on your repository connection type:
+Select one of the following tabs depending on your connection type:
 
 # [GitHub](#tab/github)
 

articles/sentinel/ci-cd.md

@@ -111,6 +111,8 @@ After the deployment is complete:
 
     :::image type="content" source="media/ci-cd/deployment-logs-status.png" alt-text="Screenshot of a GitHub repository connection's deployment logs.":::
 
+The default workflow only deploys content that has been modified since the last deployment based on commits to the repository. But you may want to turn off smart deployments or perform other customizations. For example, you can configure different deployment triggers, or deploy content exclusively from a specific root folder. To learn more about how this is done visit [customize repository deployments](ci-cd-custom-deploy.md).
+
 ## Edit content
 
 When you successfully create a connection to your source control repository, your content is deployed to Sentinel. We recommend that you edit content stored in a connected repository *only* in the repository, and not in Microsoft Sentinel. For example, to make changes to your analytics rules, do so directly in GitHub or Azure DevOps.