diff --git a/docs/standard/garbage-collection/implementing-disposeasync.md b/docs/standard/garbage-collection/implementing-disposeasync.md index 63349540f36ff..4f12adaf14db8 100644 --- a/docs/standard/garbage-collection/implementing-disposeasync.md +++ b/docs/standard/garbage-collection/implementing-disposeasync.md @@ -19,7 +19,7 @@ The interface was in It's typical when implementing the interface that classes also implement the interface. A good implementation pattern of the interface is to be prepared for either synchronous or asynchronous disposal, however, it's not a requirement. If no synchronous disposable of your class is possible, having only is acceptable. All of the guidance for implementing the disposal pattern also applies to the asynchronous implementation. This article assumes that you're already familiar with how to [implement a Dispose method](implementing-dispose.md). > [!CAUTION] -> If you implement the interface but not the interface, your app can potentially leak resources. If a class implements , but not , and a consumer only calls `Dispose`, your implementation would never call `DisposeAsync`. This would result in a resource leak. +> If you implement the interface but not the interface, your app can potentially leak resources. If a class implements , but not , and a consumer only calls `DisposeAsync`, your implementation would never call `DisposeAsync`. This would result in a resource leak. [!INCLUDE [disposables-and-dependency-injection](includes/disposables-and-dependency-injection.md)]