EndInvoke and WaitOne seem redundant from this article.

### Type of issue

Typo

### Description

This is a great documentation. However, can you please provide an example and a use case that demonstrates that the **WaitOne** is not _redundant_ and it serves a different purpose than the **EndInvoke**. This article lacks that.
I asked Copilot for Edge to tell me the difference between the two but after a long convo, it said that the **EndInvoke** can only be called once per asynchronous operation. If that's the case, then it can be the differentiating factor between **WaitOne** and **EndInvoke**.
Please update this article to deal with this confusion.
Thanks,

[Enter feedback here]

### Page URL

https://learn.microsoft.com/en-us/dotnet/standard/asynchronous-programming-patterns/calling-synchronous-methods-asynchronously

### Content source URL

https://github.com/dotnet/docs/blob/main/docs/standard/asynchronous-programming-patterns/calling-synchronous-methods-asynchronously.md

### Document Version Independent Id

a6a6845f-e7cf-8c6f-65a8-04ed09f64a1e

### Article author

@BillWagner