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

Author: wwlpublish

learn-pr/dot-net-maui/separate-ui-and-logic-with-data-binding/includes/2-compare-event-and-data-bound.md

@@ -19,7 +19,7 @@ Consider the example of a weather service app. The following XAML fragment conta
 </VerticalStackLayout>
 ```
 
-:::image type="content" source="../media/2-compare-event-and-data-bound/events-ui-example.png" alt-text="Screenshot of a .NET MAUI app that has an entry control for a postal code, a button with the text refresh. Under those two controls is a label that represents the humidity.":::
+:::image type="content" source="../media/2-compare-event-and-data-bound/events-ui-example.png" alt-text="Screenshot of a .NET MAUI app that has an entry control for a postal code, a button with the text refresh. Under those two controls, is a label that represents the humidity.":::
 
 There are three named controls in this example:
 
@@ -44,7 +44,7 @@ This design works great for small UIs, but as soon as the UI becomes complex, ma
 
 ## Data binding helps
 
-You can implement data bindings in XAML or code, but they're much more common in XAML, where they help to reduce the code-behind file size. By replacing procedural code in event handlers with declarative code or markup, the app is simplified and clarified. Because the bindings don't require code-behind, you can easily create, alter, or redesign the UI to fit how you want to present the data.
+You can implement data bindings in XAML or code, but they're much more common in XAML, where they help to reduce the code-behind file size. When you replace procedural code in event handlers with declarative code or markup, the app is simplified and clarified. Because the bindings don't require code-behind, you can easily create, alter, or redesign the UI to fit how you want to present the data.
 
 Let's take the same example as in the previous section, but update it to use data binding:
 
@@ -69,11 +69,11 @@ The same three controls are declared in the XAML, but none of them are named, be
 
 - **`Label` control**: This `Text` property is bound to a property named `Humidity`.
 
-In this simple UI, all of the code-behind is eliminated. Removing all code-behind isn't the point of data binding, even though it's usually possible. Code-behind still has its place. How much data binding you implement is up to you.
+In this simple UI, all of the code-behind is eliminated. Removing all code-behind isn't the point of data binding, even though it's possible. Code-behind still has its place. How much data binding you implement is up to you.
 
 Now, the UI is loosely coupled to a data object. Why is it loosely coupled instead of tightly coupled? Because of the way bindings are evaluated. Each control has a `BindingContext` property. If the context isn't set, the parent control's context is used, and so on, until the root of the XAML is evaluated. When bindings are evaluated, the context's object instance is checked for the required properties, like the label control's `Text` binding to the context's `Humidity` property. If `Humidity` doesn't exist on the context, nothing happens.
 
-Because the UI is loosely coupled, you can redesign the UI worrying about breaking code. However, you can break functionality. For example, you can delete the button and the app still compiles and runs, but you don't have a way to refresh the weather. On the other hand, you could replace the `Entry` and `Button` controls with the single `SearchBar` control. This control lets you enter text and invoke a command.
+Because the UI is loosely coupled, you can redesign the UI without worrying about breaking code. However, you can break functionality. For example, you can delete the button and the app still compiles and runs, but you don't have a way to refresh the weather. On the other hand, you could replace the `Entry` and `Button` controls with the single `SearchBar` control. This control lets you enter text and invoke a command.
 
 ```xaml
 <SearchBar Text="{Binding Location, Mode=OneWayToSource}" SearchCommand="{Binding RefreshWeather}" />

learn-pr/github/manage-github-actions-enterprise/includes/manage-actions-workflows.md

@@ -95,6 +95,8 @@ Following is the metadata file you would create for the workflow file:
 }
 ```
 
+<!-- INFOMAGNUS UPDATES for sub OD 4.1.1. go here. Source Material:https://docs.github.com/en/enterprise-cloud@latest/actions/sharing-automations/sharing-actions-and-workflows-with-your-enterprise -->
+
 Metadata files use the following parameters:
 
 |   Parameter    |                                                                                                                   Description                                                                                                                   |      Required      |

learn-pr/github/manage-github-actions-enterprise/includes/manage-encrypted-secrets.md

@@ -117,13 +117,6 @@ If you need to access the encrypted secret in your action's code, the action cod
 > [!WARNING]
 > When authoring your own actions, make sure not to include any encrypted secrets in your action's source code, because actions are sharable units of work. If your action needs to use encrypted secrets or other user-supplied inputs, it's best to use the core module from the [Actions Toolkit](https://github.com/actions/toolkit).
 
->
-
-<!-- INFOMAGNUS UPDATES for all of sub OD 4.3 go here! Source Material:https://www.google.com/url?q=https://docs.github.com/en/actions/security-for-github-actions/security-guides/security-hardening-for-github-actions&sa=D&source=editors&ust=1742484244534691&usg=AOvVaw30HJhmh-nnnssWIlwRCI_5 -->
-
-<!-- Test -->
-
-
 ### Access Encrypted Secrets Within Actions and Workflows
 
 #### Example: Using a Secret in a Workflow

learn-pr/student-evangelism/intro-mlops-iot-edge/1-introduction.yml

@@ -1,15 +1,15 @@
-### YamlMime:ModuleUnit
-uid: learn.oxford.intro-mlops-iot-edge.introduction
-title: Introduction
-metadata:
-  title: Introduction
-  description: In this section, we help the learner decide if the product meets their needs by explaining when to use the product and how it works.
-  ms.date: 11/28/2023
-  author: PatAltimore
-  ms.author: leestott
-  ms.topic: unit
-  ms.custom: team=nextgen
-durationInMinutes: 6 # dummy number at present
-content: |
-  [!include[](includes/1-introduction.md)]
-
+### YamlMime:ModuleUnit
+uid: learn.oxford.intro-mlops-iot-edge.introduction
+title: Introduction
+metadata:
+  title: Introduction
+  description: In this section, we help the learner decide if the product meets their needs by explaining when to use the product and how it works.
+  ms.date: 05/12/2025
+  author: PatAltimore
+  ms.author: leestott
+  ms.topic: unit
+  ms.custom: team=nextgen
+durationInMinutes: 6
+content: |
+  [!include[](includes/1-introduction.md)]
+

learn-pr/student-evangelism/intro-mlops-iot-edge/2-what-mlops.yml

@@ -1,15 +1,15 @@
-### YamlMime:ModuleUnit
-uid: learn.oxford.intro-mlops-iot-edge.what-mlops-iot-edge
-title: What is MLOps for IoT Edge?
-metadata:
-  title: What is MLOps for IoT Edge?
-  description: In this section, we provide a definition of the product and discuss the value proposition of the product.
-  ms.date: 11/28/2023
-  author: PatAltimore
-  ms.author: leestott
-  ms.topic: unit
-  ms.custom: team=nextgen
-durationInMinutes: 7 # dummy number at present
-content: |
-  [!include[](includes/2-what-mlops.md)]
-
+### YamlMime:ModuleUnit
+uid: learn.oxford.intro-mlops-iot-edge.what-mlops-iot-edge
+title: What is MLOps for IoT Edge?
+metadata:
+  title: What is MLOps for IoT Edge?
+  description: In this section, we provide a definition of the product and discuss the value proposition of the product.
+  ms.date: 05/12/2025
+  author: PatAltimore
+  ms.author: leestott
+  ms.topic: unit
+  ms.custom: team=nextgen
+durationInMinutes: 7
+content: |
+  [!include[](includes/2-what-mlops.md)]
+

learn-pr/student-evangelism/intro-mlops-iot-edge/3-how-mlops-works.yml

@@ -1,15 +1,15 @@
-### YamlMime:ModuleUnit
-uid: learn.oxford.intro-mlops-iot-edge.how-mlops-works-iot-edge
-title: How MLOps works for IoT Edge
-metadata:
-  title: How MLOps works for IoT Edge
-  description: In this section, we provide a high-level explanation of the parts of the product and explain how these parts work together. We also show how the product would work when solving the scenario outlined in the introduction section.
-  ms.date: 11/28/2023
-  author: PatAltimore
-  ms.author: leestott
-  ms.topic: unit
-  ms.custom: team=nextgen
-durationInMinutes: 10 # dummy number at present
-content: |
-  [!include[](includes/3-how-mlops-works.md)]
-
+### YamlMime:ModuleUnit
+uid: learn.oxford.intro-mlops-iot-edge.how-mlops-works-iot-edge
+title: How MLOps works for IoT Edge
+metadata:
+  title: How MLOps works for IoT Edge
+  description: In this section, we provide a high-level explanation of the parts of the product and explain how these parts work together. We also show how the product would work when solving the scenario outlined in the introduction section.
+  ms.date: 05/12/2025
+  author: PatAltimore
+  ms.author: leestott
+  ms.topic: unit
+  ms.custom: team=nextgen
+durationInMinutes: 10
+content: |
+  [!include[](includes/3-how-mlops-works.md)]
+

learn-pr/student-evangelism/intro-mlops-iot-edge/4-when-use-mlops.yml

@@ -1,15 +1,15 @@
-### YamlMime:ModuleUnit
-uid: learn.oxford.intro-mlops-iot-edge.when-use-mlops-iot-edge
-title: When to use MLOps for IoT Edge
-metadata:
-  title: When to use MLOps for IoT Edge
-  description: In this section, we describe the criteria customers should use when deciding whether the product meets their needs.
-  ms.date: 11/28/2023
-  author: PatAltimore
-  ms.author: leestott
-  ms.topic: unit
-  ms.custom: team=nextgen
-durationInMinutes: 6 # dummy number at present
-content: |
-  [!include[](includes/4-when-use-mlops.md)]
-
+### YamlMime:ModuleUnit
+uid: learn.oxford.intro-mlops-iot-edge.when-use-mlops-iot-edge
+title: When to use MLOps for IoT Edge
+metadata:
+  title: When to use MLOps for IoT Edge
+  description: In this section, we describe the criteria customers should use when deciding whether the product meets their needs.
+  ms.date: 05/12/2025
+  author: PatAltimore
+  ms.author: leestott
+  ms.topic: unit
+  ms.custom: team=nextgen
+durationInMinutes: 6
+content: |
+  [!include[](includes/4-when-use-mlops.md)]
+

learn-pr/student-evangelism/intro-mlops-iot-edge/5-knowledge-check.yml

@@ -1,49 +1,49 @@
-### YamlMime:ModuleUnit
-uid: learn.oxford.intro-mlops-iot-edge.knowledge-check
-title: Module assessment
-metadata:
-  title: Module assessment
-  description: In this section, we create interactive questions that validate if the learner has understood the learning objectives
-  ms.date: 11/28/2023
-  author: PatAltimore
-  ms.author: leestott
-  ms.topic: unit
-  ms.custom: team=nextgen
-durationInMinutes: 5 # dummy number at present
-content: |
-quiz:
-  questions:
-  - content: "If you want to deploy MLOps, what is the correct sequence of deployment?"
-    choices:
-    - content: "Build and Train; Package and Deploy; Monitor and Retrain"
-      isCorrect: true
-      explanation: "Correct. You first create the model, then you can package and deploy the model. The model is monitored and retrained as needed."
-    - content: "Monitor and Retrain; Package and Deploy; Build and Train"
-      isCorrect: false
-      explanation: "Incorrect. Build and Train is the first step in the deployment of MLOps."
-    - content: "Package and Deploy; Monitor and Retrain; Build and Train"
-      isCorrect: false
-      explanation: "Incorrect. You can't package and deploy a model without building it first."
-  - content: "MLOps brings the philosophy of DevOps to the Data science community. In the absence of MLOPs, how would the work of a data scientist be impacted?"
-    choices:
-    - content: "A data scientist won't be able to conduct experiments."
-      isCorrect: false
-      explanation: "Incorrect. A data scientist can conduct experiments without MLOps."
-    - content: "A data scientist won't be able to test models."
-      isCorrect: false
-      explanation: "Incorrect. A data scientist can test models without MLOps."
-    - content: "A data scientist wouldn't be able to collaborate with developers efficiently."
-      isCorrect: true
-      explanation: "Correct. A data scientist wouldn't be able to collaborate effectively with developers in the absence of MLOps because they would be each following different workflow."
-  - content: "A company has decided to implement MLOps on Edge devices. Which step would they need to implement before deploying MLOPs on Edge devices?"
-    choices:
-    - content: "The company should deploy IoT Edge and capture data from sensors."
-      isCorrect: true
-      explanation: "Correct. Without IoT Edge being operational, you can't acquire data to build models."
-    - content: "The company should be able to visualize data from sensors."
-      isCorrect: false
-      explanation: "Incorrect. The ability to visualize data isn't a prerequisite for MLOps on edge devices."
-    - content: "Developers should follow CI/CD processes before MLOps is deployed."
-      isCorrect: false
-      explanation: "Incorrect. The ability to use CI/CD isn't a prerequisite for MLOps on edge devices."
-
+### YamlMime:ModuleUnit
+uid: learn.oxford.intro-mlops-iot-edge.knowledge-check
+title: Module assessment
+metadata:
+  title: Module assessment
+  description: In this section, we create interactive questions that validate if the learner has understood the learning objectives
+  ms.date: 05/12/2025
+  author: PatAltimore
+  ms.author: leestott
+  ms.topic: unit
+  ms.custom: team=nextgen
+durationInMinutes: 5
+content: |
+quiz:
+  questions:
+  - content: "If you want to deploy MLOps, what is the correct sequence of deployment?"
+    choices:
+    - content: "Build and Train; Package and Deploy; Monitor and Retrain"
+      isCorrect: true
+      explanation: "Correct. You first create the model, then you can package and deploy the model. The model is monitored and retrained as needed."
+    - content: "Monitor and Retrain; Package and Deploy; Build and Train"
+      isCorrect: false
+      explanation: "Incorrect. Build and Train is the first step in the deployment of MLOps."
+    - content: "Package and Deploy; Monitor and Retrain; Build and Train"
+      isCorrect: false
+      explanation: "Incorrect. You can't package and deploy a model without building it first."
+  - content: "MLOps brings the philosophy of DevOps to the Data science community. In the absence of MLOPs, how would the work of a data scientist be impacted?"
+    choices:
+    - content: "A data scientist won't be able to conduct experiments."
+      isCorrect: false
+      explanation: "Incorrect. A data scientist can conduct experiments without MLOps."
+    - content: "A data scientist won't be able to test models."
+      isCorrect: false
+      explanation: "Incorrect. A data scientist can test models without MLOps."
+    - content: "A data scientist wouldn't be able to collaborate with developers efficiently."
+      isCorrect: true
+      explanation: "Correct. A data scientist wouldn't be able to collaborate effectively with developers in the absence of MLOps because they would be each following different workflow."
+  - content: "A company has decided to implement MLOps on Edge devices. Which step would they need to implement before deploying MLOPs on Edge devices?"
+    choices:
+    - content: "The company should deploy IoT Edge and capture data from sensors."
+      isCorrect: true
+      explanation: "Correct. Without IoT Edge being operational, you can't acquire data to build models."
+    - content: "The company should be able to visualize data from sensors."
+      isCorrect: false
+      explanation: "Incorrect. The ability to visualize data isn't a prerequisite for MLOps on edge devices."
+    - content: "Developers should follow CI/CD processes before MLOps is deployed."
+      isCorrect: false
+      explanation: "Incorrect. The ability to use CI/CD isn't a prerequisite for MLOps on edge devices."
+

learn-pr/student-evangelism/intro-mlops-iot-edge/6-summary.yml

@@ -1,15 +1,15 @@
-### YamlMime:ModuleUnit
-uid: learn.oxford.intro-mlops-iot-edge.summary
-title: Summary
-metadata:
-  title: Summary
-  description: In this section, we summarize the key ideas in the module and emphasize the ideas to ensure learning retention
-  ms.date: 11/28/2023
-  author: PatAltimore
-  ms.author: leestott
-  ms.topic: unit
-  ms.custom: team=nextgen
-durationInMinutes: 2 # dummy number at present
-content: |
-  [!include[](includes/6-summary.md)]
-
+### YamlMime:ModuleUnit
+uid: learn.oxford.intro-mlops-iot-edge.summary
+title: Summary
+metadata:
+  title: Summary
+  description: In this section, we summarize the key ideas in the module and emphasize the ideas to ensure learning retention
+  ms.date: 05/12/2025
+  author: PatAltimore
+  ms.author: leestott
+  ms.topic: unit
+  ms.custom: team=nextgen
+durationInMinutes: 2
+content: |
+  [!include[](includes/6-summary.md)]
+