From ed1e1df7e65b6b8b21a776f7291da9cd3d1e3ee6 Mon Sep 17 00:00:00 2001 From: Karol Lewandowski Date: Thu, 5 Dec 2024 11:10:02 +0100 Subject: [PATCH] disposers.md: Avoid caps-lock --- topics/basics/disposers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/topics/basics/disposers.md b/topics/basics/disposers.md index 81c4f41da..2da543e56 100644 --- a/topics/basics/disposers.md +++ b/topics/basics/disposers.md @@ -107,7 +107,7 @@ Use the following guidelines to choose the correct parent: * For resources with a shorter lifetime, create a disposable using `Disposer.newDisposable()` and dispose it manually using `Disposable.dispose()`. Note that it's always best to specify a parent for such a disposable (e.g., a project-level service), so that there is no memory leak if the `Disposable.dispose()` call is not reached because of an exception or a programming error. -> Even though `Application` and `Project` implement `Disposable`, they must NEVER be used as parent disposables in plugin code. +> Even though `Application` and `Project` implement `Disposable`, they must **never** be used as parent disposables in plugin code. > Disposables registered using those objects as parents will not be disposed when the plugin is unloaded, leading to memory leaks. > > Consider a case of a disposable resource created by a plugin and registered with a project as its parent.