changed files by pdets auto publish service, publishid[b62d07dc-9e81-49f3-a6ba-716535fc6fac] and do [publish].

Author: wwlpublish

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

@@ -3,7 +3,7 @@ uid: learn.wwl.discover-interfaces.introduction
 title: Introduction
 metadata:
   title: Introduction
-  description: "Introduction"
+  description: "Introduction to C# interfaces."
   ms.date: 02/13/2025
   author: wwlpublish
   ms.author: eric

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

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

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

@@ -22,7 +22,7 @@ quiz:
       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."
+      explanation: "Incorrect. Interface properties aren't 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."
@@ -41,10 +41,10 @@ quiz:
       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 ':'."
+      explanation: "Incorrect. The 'implements' keyword isn't 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 ':'."
+      explanation: "Incorrect. The 'extends' keyword isn't 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."
@@ -55,4 +55,4 @@ quiz:
       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."
+      explanation: "Incorrect. Interfaces may define default implementations for some members starting with C# 8.0, but this isn't their primary benefit."

learn-pr/wwl-azure/discover-interfaces/includes/1-introduction.md

@@ -13,7 +13,7 @@ In this module, you learn how to design an interface with properties in .NET, de
 
 ## Prerequisites
 
-- Visual Studio Code installed with th3 C# Dev Kit
-- Basic knowledge of the Visual Studio Code IDE
-- Basic understanding of the C# programming language
-- Familiarity with classes
+- Visual Studio Code installed with the C# Dev Kit.
+- Basic knowledge of the Visual Studio Code IDE.
+- Basic understanding of the C# programming language.
+- Familiarity with classes.

learn-pr/wwl-azure/discover-interfaces/includes/2-understand-interfaces.md

@@ -4,21 +4,21 @@ An interface is like a to-do list or a contract. It outlines what jobs need to b
 
 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
+### Parts of an interface
 
 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.
 
-### Use an Interface
+### Use an interface
 
 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."
 
 In the "Person" class, 'Move' could mean walking, jogging, or running. In the "Horse" class, 'Move' could mean walking, trotting, or galloping. Even though they move in different ways, both classes fulfill the 'Move' job requirement from the "Move" interface.
 
-### Why Use an Interface?
+### Why use an interface?
 
 The properties defined by an interface are useful because they ensure that all classes handle information in the same way. An interface makes your related classes more consistent and easier to work with. As long as they all use the same interface, you can write instructions that work with all kinds of different classes.
 

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

@@ -13,7 +13,8 @@ public interface IVehicle
 }
 ```
 
-Note how the `Drive` method is declared without a body in the interface. When adding methods to an interface, include the method's signature in the interface declaration, but not its body. The class implementing the interface provides the method's body."
+> [!NOTE]
+> How the `Drive` method is declared without a body in the interface. When adding methods to an interface, include the method's signature in the interface declaration, but not its body. The class implementing the interface provides the method's body.
 
 ## Construct a class that implements the interface
 

learn-pr/wwl-azure/discover-interfaces/index.yml

@@ -23,13 +23,13 @@ abstract: |
 
   - Understand the value of interfaces.
 prerequisites: |
-  - Visual Studio Code installed with the C# Dev Kit
+  - Visual Studio Code installed with the C# Dev Kit.
 
-  - Basic knowledge of the Visual Studio Code IDE
+  - Basic knowledge of the Visual Studio Code IDE.
 
-  - Basic understanding of the C# programming language
+  - Basic understanding of the C# programming language.
 
-  - Familiarity with classes
+  - Familiarity with classes.
 iconUrl: /training/achievements/generic-badge.svg
 levels:
 - beginner