Merge pull request #295523 from austinmccollum/austinmc-cicd-updates

Update documentation to use the current industry term for the repos

Author: Stacyrch140

articles/sentinel/TOC.yml

@@ -109,7 +109,7 @@
     href: migration-convert-dashboards.md
   - name: Update SOC processes      
     href: migration-security-operations-center-processes.md
-- name: Enable solutions and content
+- name: Manage solutions and content
   items:  
   - name: Overview
     href: sentinel-solutions.md
@@ -127,11 +127,11 @@
       href: domain-based-essential-solutions.md
     - name: Monitor Zero Trust 
       href: sentinel-solution.md   
-  - name: Manage custom content from repositories
+  - name: Manage content as code using repositories
     items:
     - name: Overview
       href: ci-cd-custom-content.md
-    - name: Deploy custom content from your repository
+    - name: Deploy content as code from your repository
       href: ci-cd.md   
     - name: Customize repository deployments
       href: ci-cd-custom-deploy.md

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

@@ -15,9 +15,11 @@ ms.collection: usx-security
 
 ---
 
-# Manage custom content with Microsoft Sentinel repositories (public preview)
+# Manage content as code with Microsoft Sentinel repositories (public preview)
 
-The Microsoft Sentinel repositories feature provides a central experience for the deployment and management of Sentinel content as code. Repositories allow connections to an external source control for continuous integration / continuous delivery (CI/CD). This automation removes the burden of manual processes to update and deploy your custom content across workspaces. For more information on Sentinel content, see [About Microsoft Sentinel content and solutions](sentinel-solutions.md).
+The Microsoft Sentinel repositories feature provides a central experience for the deployment and management of Sentinel content as code. Repositories allow connections to an external source control for continuous integration / continuous delivery (CI/CD). This automation removes the burden of manual processes to update and deploy your custom content across workspaces. A subset of content as code is *detections* as code (DaC). Microsoft Sentinel **Repositories** implements DaC as well.
+
+For more information on Sentinel content, see [About Microsoft Sentinel content and solutions](sentinel-solutions.md).
 
 > [!IMPORTANT]
 > 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.

articles/sentinel/ci-cd.md

@@ -16,7 +16,7 @@ ms.collection: usx-security
 
 ---
 
-# Deploy custom content from your repository (Public preview)
+# Deploy content as code from your repository (Public preview)
 
 When creating custom content, you can manage it from your own Microsoft Sentinel workspaces, or an external source control repository. This article describes how to create and manage connections between Microsoft Sentinel and GitHub or Azure DevOps repositories. Managing your content in an external repository allows you to make updates to that content outside of Microsoft Sentinel, and have it automatically deployed to your workspaces. For more information, see [Update custom content with repository connections](ci-cd-custom-content.md).
 

articles/sentinel/sentinel-solutions.md

@@ -14,7 +14,7 @@ appliesto:
 
 ---
 
-# About Microsoft Sentinel content and solutions
+# About Microsoft Sentinel Out-of-the-box content
 
 Microsoft Sentinel *content* is Security Information and Event Management (SIEM) solution components that enable customers to ingest data, monitor, alert, hunt, investigate, respond, and connect with different products, platforms, and services.