Skip to content

Commit 1c7985c

Browse files
v-maudelRon Petrusha
authored andcommitted
C26874: replacing Markdon Italics by HTML Italic tags (#6352)
Hello, @mairaw , Localization team has reported source content issue that causes localized version to have broken/different format compared to en-us version. "Italics should be replaced with HTML tags <em></em> to avoid broken content on localization" Please review and merge the proposed file change to fix to target versions. If you make related fix in another PR then share your PR number so we can confirm and close this PR. Many thanks in advance.
1 parent ce6d77b commit 1c7985c

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/standard/asynchronous-programming-patterns/best-practices-for-implementing-the-event-based-asynchronous-pattern.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,14 +22,14 @@ The Event-based Asynchronous Pattern provides you with an effective way to expos
2222
If you implement the Event-based Asynchronous Pattern, you must provide a number of guarantees to ensure that your class will behave properly and clients of your class can rely on such behavior.
2323

2424
### Completion
25-
Always invoke the *MethodName***Completed** event handler when you have successful completion, an error, or a cancellation. Applications should never encounter a situation where they remain idle and completion never occurs. One exception to this rule is if the asynchronous operation itself it designed so that it never completes.
25+
Always invoke the <em>MethodName</em>**Completed** event handler when you have successful completion, an error, or a cancellation. Applications should never encounter a situation where they remain idle and completion never occurs. One exception to this rule is if the asynchronous operation itself it designed so that it never completes.
2626

2727
### Completed Event and EventArgs
28-
For each separate *MethodName***Async** method, apply the following design requirements:
28+
For each separate <em>MethodName</em>**Async** method, apply the following design requirements:
2929

30-
- Define a *MethodName***Completed** event on the same class as the method.
30+
- Define a <em>MethodName</em>**Completed** event on the same class as the method.
3131

32-
- Define an <xref:System.EventArgs> class and accompanying delegate for the *MethodName***Completed** event that derives from the <xref:System.ComponentModel.AsyncCompletedEventArgs> class. The default class name should be of the form *MethodName***CompletedEventArgs**.
32+
- Define an <xref:System.EventArgs> class and accompanying delegate for the <em>MethodName</em>**Completed** event that derives from the <xref:System.ComponentModel.AsyncCompletedEventArgs> class. The default class name should be of the form *MethodName***CompletedEventArgs**.
3333

3434
- Ensure that the <xref:System.EventArgs> class is specific to the return values of the *MethodName* method. When you use the <xref:System.EventArgs> class, you should never require developers to cast the result.
3535

0 commit comments

Comments
 (0)