changed files by pdets auto publish service, publishid[801b4fe8-d8f9-4b49-96ee-41fb0f619b69] and do [publish].

Author: wwlpublish

learn-pr/wwl-azure/discover-interfaces/1-introduction.yml

@@ -4,7 +4,7 @@ title: Introduction
 metadata:
   title: Introduction
   description: "Introduction"
-  ms.date: 02/12/2025
+  ms.date: 02/13/2025
   author: wwlpublish
   ms.author: eric
   ms.topic: unit

learn-pr/wwl-azure/discover-interfaces/2-understand-interfaces.yml

@@ -1,10 +1,10 @@
 ### YamlMime:ModuleUnit
 uid: learn.wwl.discover-interfaces.understand-interfaces
-title: Understand Interfaces
+title: Understand interfaces
 metadata:
-  title: Understand Interfaces
-  description: "Understand Interfaces in C# code."
-  ms.date: 02/12/2025
+  title: Understand interfaces
+  description: "Understand interfaces in C# code."
+  ms.date: 02/13/2025
   author: wwlpublish
   ms.author: eric
   ms.topic: unit

learn-pr/wwl-azure/discover-interfaces/3-create-interface-properties.yml

@@ -3,8 +3,8 @@ uid: learn.wwl.discover-interfaces.create-interface-properties
 title: Implement interface properties
 metadata:
   title: Implement interface properties
-  description: "Implement interface properties"
-  ms.date: 02/12/2025
+  description: "Implemnt interface properties in C# code."
+  ms.date: 02/13/2025
   author: wwlpublish
   ms.author: eric
   ms.topic: unit

learn-pr/wwl-azure/discover-interfaces/4-create-interface-methods.yml

@@ -4,7 +4,7 @@ title: Create interface methods
 metadata:
   title: Create interface methods
   description: "Create interface methods in C# code."
-  ms.date: 02/12/2025
+  ms.date: 02/13/2025
   author: wwlpublish
   ms.author: eric
   ms.topic: unit

learn-pr/wwl-azure/discover-interfaces/5-understand-the-value-of-interfaces.yml renamed to learn-pr/wwl-azure/discover-interfaces/5-understand-value-interfaces.yml

@@ -1,13 +1,13 @@
 ### YamlMime:ModuleUnit
-uid: learn.wwl.discover-interfaces.understand-the-value-of-interfaces
+uid: learn.wwl.discover-interfaces.understand-value-interfaces
 title: Understand the value of interfaces
 metadata:
   title: Understand the value of interfaces
   description: "Understand the value of interfaces in C# code."
-  ms.date: 02/12/2025
+  ms.date: 02/13/2025
   author: wwlpublish
   ms.author: eric
   ms.topic: unit
 durationInMinutes: 5
 content: |
-  [!include[](includes/5-understand-the-value-of-interfaces.md)]
+  [!include[](includes/5-understand-value-interfaces.md)]

learn-pr/wwl-azure/discover-interfaces/6-exercise-implement-interfaces-in-project.yml

@@ -0,0 +1,13 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.discover-interfaces.exercise-implement-interfaces-project
+title: 'Exercise: Implement interfaces in project'
+metadata:
+  title: 'Exercise: Implement interfaces in project'
+  description: "Exercise: Implement interfaces in project with C#."
+  ms.date: 02/13/2025
+  author: wwlpublish
+  ms.author: eric
+  ms.topic: unit
+durationInMinutes: 20
+content: |
+  [!include[](includes/6-exercise-implement-interfaces-project.md)]

learn-pr/wwl-azure/discover-interfaces/6-exercise-implement-interfaces-project.yml

@@ -4,10 +4,55 @@ title: Knowledge check
 metadata:
   title: Knowledge check
   description: "Knowledge check."
-  ms.date: 02/12/2025
+  ms.date: 02/13/2025
   author: wwlpublish
   ms.author: eric
   ms.topic: unit
 durationInMinutes: 2
-content: |
-  [!include[](includes/7-knowledge-check.md)]
+quiz:
+  title: "Check your knowledge"
+  questions:
+  - content: "Which of the following is true about properties in an interface?"
+    choices:
+    - content: "They can have instance data fields."
+      isCorrect: false
+      explanation: "Incorrect. Properties in an interface don't declare instance data fields."
+    - content: "They typically don't have a body."
+      isCorrect: true
+      explanation: "Correct. Interface properties typically don't have a body; they only define accessors."
+    - content: "They must be static."
+      isCorrect: false
+      explanation: "Incorrect. Interface properties are not required to be static."
+  - content: "You're implementing an interface in a class. What must you ensure?"
+    choices:
+    - content: "Provide public, non-static implementations for all interface members."
+      isCorrect: true
+      explanation: "Correct. When a class implements an interface, it must provide public, non-static implementations for all interface members."
+    - content: "Provide private implementations for all interface members."
+      isCorrect: false
+      explanation: "Incorrect. Interface members must be implemented as public, not private."
+    - content: "Provide static implementations for all interface members."
+      isCorrect: false
+      explanation: "Incorrect. Interface members should be implemented as non-static."
+  - content: "In a scenario where you need to implement an interface in a class, what syntax is used?"
+    choices:
+    - content: "class ClassName : InterfaceName"
+      isCorrect: true
+      explanation: "Correct. The correct syntax to implement an interface in a class is 'class ClassName : InterfaceName'."
+    - content: "class ClassName implements InterfaceName"
+      isCorrect: false
+      explanation: "Incorrect. The 'implements' keyword is not used in C#; the correct keyword is ':'."
+    - content: "class ClassName extends InterfaceName"
+      isCorrect: false
+      explanation: "Incorrect. The 'extends' keyword is not used in C#; the correct keyword is ':'."
+  - content: "What is a key benefit of using interfaces in C# programming?"
+    choices:
+    - content: "They allow for better code organization and flexibility."
+      isCorrect: true
+      explanation: "Correct. Interfaces provide a way to define contracts for classes, enabling better code organization and flexibility."
+    - content: "They allow classes to inherit from multiple base classes."
+      isCorrect: false
+      explanation: "Incorrect. Interfaces don't allow multiple inheritance of classes; they allow a class to implement multiple interfaces."
+    - content: "They provide default implementations for all members."
+      isCorrect: false
+      explanation: "Incorrect. Interfaces may define default implementations for some members starting with C# 8.0, but this is not their primary benefit."

learn-pr/wwl-azure/discover-interfaces/7-knowledge-check.yml

@@ -4,7 +4,7 @@ title: Summary
 metadata:
   title: Summary
   description: "Summary."
-  ms.date: 02/12/2025
+  ms.date: 02/13/2025
   author: wwlpublish
   ms.author: eric
   ms.topic: unit

learn-pr/wwl-azure/discover-interfaces/8-summary.yml

@@ -1,18 +1,18 @@
-An interface is like a to-do list or a contract. It outlines what jobs need to be done, without specifying how these jobs should be done. The contract nature of interfaces allows for the accomplishment of different tasks in their own unique ways.
+An interface is like a to-do list or a contract. It outlines what jobs need to be done, without specifying how these jobs should be done. The contract nature of interfaces allows for multiple classes to accomplish the same tasks in their own unique ways.
 
 ### Interfaces are like a contract
 
 Each of them - the car, the person, and the horse - has its own unique way of moving. An interface could be used to define the contract requirement "You need to be able to move," but the interface doesn't define how to move.
 
 ### Parts of an Interface
 
-In C#, an interface is a "contract" that outlines the required properties and methods. An interface doesn't hold any data itself, but it does specify what kind of information should be provided through properties. For instance, in a "Move" interface, 'X' and 'Y' could be properties, representing location coordinates. These properties enable the retrieval or modification of their values.
+In C#, an interface outlines the required properties and methods. An interface doesn't hold any data itself, but it does specify what kind of information should be provided through properties. For instance, in a "Move" interface, 'X' and 'Y' could be properties, representing location coordinates. These properties enable the retrieval or modification of their values.
 
 Additionally, interfaces define methods, which are actions that can be performed. However, they don't provide the implementation for these methods. For example, the "Move" interface could include a contract requiring a "Dance" method. However, what exactly happens when the "Dance" method is called by the objects that use this interface, whether it's a car, person, or horse.
 
-### Using an Interface
+### Use an Interface
 
-To utilize an interface, entities like a car, a person, or a horse from our example adopt it as part of their functionality. The car, for instance, needs to understand how to perform all the tasks listed in the interface. This process of adopting an interface by the car is known as 'implementing' the interface. In this process, the car agrees to follow the 'contract' set by the interface, defining its own unique ways to complete the tasks such as moving by "driving." Similarly, the person and the horse would also implement the interface, each defining their own unique ways to 'move' such as "run" or "gallop."
+To utilize an interface, entities like a car, a person, or a horse from the "move" example adopt it as part of their functionality. The car, for instance, needs to understand how to perform all the tasks listed in the interface. This process of adopting an interface by the car is known as 'implementing' the interface. In this process, the car agrees to follow the 'contract' set by the interface, defining its own unique ways to complete the tasks such as moving by "driving." Similarly, the person and the horse would also implement the interface, each defining their own unique ways to 'move' such as "run" or "gallop."
 
 Consider the classes "Person" and "Horse." Both implement the "Move" interface, and it's the responsibility of "Person" and "Horse" classes to define ways to "Move."