From 41e956d08eb8dbeb8d1efea4488712cf4c76bc95 Mon Sep 17 00:00:00 2001
From: kicmeri <58749831+kicmeri@users.noreply.github.com>
Date: Mon, 1 Aug 2022 11:36:14 +0200
Subject: [PATCH] Clarify how to use processExistingClasses in debugging.adoc
 (#3130)

Improve the phrasing and the hint for alternative setups,
notably hint that a static block might help.
---
 docs/asciidoc/debugging.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/asciidoc/debugging.adoc b/docs/asciidoc/debugging.adoc
index fc040cc7b9..0fbaee1be7 100644
--- a/docs/asciidoc/debugging.adoc
+++ b/docs/asciidoc/debugging.adoc
@@ -433,7 +433,7 @@ ReactorDebugAgent.init();
 ====
 
 TIP: Since the implementation will instrument your classes when they are loaded,
-the best place to put it is before everything else in your main(String[]) methood:
+the best place to put it is before everything else in your main(String[]) method:
 ====
 [source,java]
 ----
@@ -444,7 +444,7 @@ public static void main(String[] args) {
 ----
 ====
 
-You may also re-process existing classes if you cannot run the init eagerly (e.g. in the tests):
+You may also re-process existing classes with `processExistingClasses()` if you cannot run the init eagerly. For example, in https://junit.org/junit5/docs/current/user-guide/#launcher-api-listeners-custom[JUnit5 tests from a `TestExecutionListener`] or even in the class `static` initializer block:
 ====
 [source,java]
 ----