pull base content,head:MicrosoftDocs:main,into:wwlpublishsync

Author: wwlpublish

learn-pr/advocates/govern-ai-azure-policy/index.yml

@@ -10,7 +10,7 @@ metadata:
   ms.topic: module
   ms.collection: ce-advocates-ai-copilot
 title: Govern AI services with Azure Policy
-summary: TBD
+summary: Learn how to govern AI services on Azure with Azure Policy including how to apply policy definitions and assess AI workload compliance.
 abstract: |
     After completing this module, you'll be able to:
     -	Set up policy and initiative assignments to Azure AI services, Azure AI Foundry, and Azure Machine Learning

learn-pr/dot-net-maui/build-mobile-and-desktop-apps/includes/2-describe-maui-architecture.md

@@ -1,4 +1,4 @@
-A common pattern used for cross-platform app development is to factor the business logic from the user interface, and then develop separate user interfaces and UI logic for each platform. While the business logic remains unchanged for each type of device, the code that drives the app and presents the data can vary. This variance is because of the differing capabilities, APIs, and features the devices provide. Building a multiplatform app in this way involves dealing with not only separate Software Development Kits (SDKs), but altogether different languages and toolsets.
+A common pattern used for cross-platform app development is to factor the business logic separate from the user interface, and then develop separate user interfaces and UI logic for each platform. While the business logic remains unchanged for each type of device, the code that drives the app and presents the data can vary. This variance is because of the differing capabilities, APIs, and features the devices provide. Building a multiplatform app in this way involves dealing with not only separate Software Development Kits (SDKs), but altogether different languages and toolsets.
 
 The purpose of .NET MAUI (Multi-platform Application User Interface) is to simplify multiplatform app development. Using .NET MAUI, you create multiplatform apps using a single project, but you can add platform-specific source code and resources if necessary. The key aim of .NET MAUI is to enable you to implement as much of your application logic and UI layout as possible in a single codebase.
 

learn-pr/github/codebase-representation-codeql/1-introduction.yml

@@ -5,7 +5,7 @@ metadata:
   unitType: Introduction 
   title: Introduction
   description: Learn how to use CodeQL to identify security vulnerabilities in your codebase.
-  ms.date: 05/01/2024
+  ms.date: 07/01/2025
   author: a-a-ron
   ms.author: aastewar
   ms.topic: unit

learn-pr/github/codebase-representation-codeql/2-how-prepare-database-codeql.yml

@@ -5,7 +5,7 @@ metadata:
   unitType: Prepare a database for CodeQL
   title: Prepare a database for CodeQL
   description: Learn how to create a CodeQL database.
-  ms.date: 05/01/2024
+  ms.date: 07/01/2025
   author: a-a-ron
   ms.author: aastewar
   ms.topic: unit

learn-pr/github/codebase-representation-codeql/3-run-codeql-database.yml

@@ -5,7 +5,7 @@ metadata:
   unitType: Run CodeQL in a database 
   title: Run CodeQL in a database 
   description: Learn how to analyze your database by using CodeQL queries.
-  ms.date: 05/01/2024
+  ms.date: 07/01/2025
   author: a-a-ron
   ms.author: aastewar
   ms.topic: unit

learn-pr/github/codebase-representation-codeql/4-understand-results.yml

@@ -4,8 +4,8 @@ title: Understand CodeQL results
 metadata:
   unitType: Understand CodeQL results 
   title: Understand CodeQL results 
-  description: View CodeQL results and determine if there are security vulnerabilities to address.
-  ms.date: 05/01/2024
+  description: View your CodeQL results and determine if there are security vulnerabilities to address.
+  ms.date: 07/01/2025
   author: a-a-ron
   ms.author: aastewar
   ms.topic: unit

learn-pr/github/codebase-representation-codeql/5-troubleshoot-your-results.yml

@@ -5,7 +5,7 @@ metadata:
   unitType:  Troubleshoot CodeQL results
   title:  Troubleshoot CodeQL results
   description: Learn about common tips for troubleshooting your CodeQL queries.
-  ms.date: 05/01/2024
+  ms.date: 07/01/2025
   author: a-a-ron
   ms.author: aastewar
   ms.topic: unit

learn-pr/github/codebase-representation-codeql/6-knowledge-check.yml

@@ -5,7 +5,7 @@ metadata:
   unitType: knowledge_check
   title: Module assessment
   description: Check your knowledge about CodeQL.
-  ms.date: 04/08/2024
+  ms.date: 07/01/2025
   author: rmcmurray
   ms.author: robmcm
   ms.topic: unit

learn-pr/github/codebase-representation-codeql/7-summary.yml

@@ -5,7 +5,7 @@ metadata:
   unitType:  Summary
   title:  Summary
   description: Review what you learned in this module.
-  ms.date: 05/01/2024
+  ms.date: 07/01/2025
   author: a-a-ron
   ms.author: aastewar
   ms.topic: unit

learn-pr/github/codebase-representation-codeql/includes/2-how-prepare-database-codeql.md

@@ -1,4 +1,3 @@
-
 CodeQL treats code like data. You create a database by using queryable data that you extract from your codebase. Then you can run CodeQL queries on this database to identify security vulnerabilities, bugs, and other errors. You can write your own queries or run standard CodeQL queries written by GitHub researchers and community contributors.
 
 In this unit, you learn how to create a database. This step is required before you can analyze your code. You need to create a CodeQL database that contains all the data necessary to run queries on your code.