README.md

@@ -204,7 +204,7 @@ In more complex setups, taking a look at the event handler execution order can b
 Event Bus offers a method for this purpose which can be used as follows:
 
 ```java
-System.out.println(EventBus.getInstance().printExecutionOrder(SimpleEvent.class));
+System.out.println(EventBus.getInstance().debugExecutionOrder(SimpleEvent.class));
 ```
 
 Then, the execution order can be inspected in the console.

event-bus-core/src/main/java/dev/kske/eventbus/core/EventBus.java

@@ -381,7 +381,7 @@ public final class EventBus {
 	 * @return a human-readable event handler list suitable for debugging purposes
 	 * @since 1.2.0
 	 */
-	public String printExecutionOrder(Class<?> eventType) {
+	public String debugExecutionOrder(Class<?> eventType) {
 		var	handlers	= getHandlersFor(eventType);
 		var	sj			= new StringJoiner("\n");
 

event-bus-core/src/test/java/dev/kske/eventbus/core/DispatchTest.java

@@ -45,13 +45,13 @@ class DispatchTest {
 	}
 
 	/**
-	 * Tests {@link EventBus#printExecutionOrder(Class)} based on the currently registered handlers.
+	 * Tests {@link EventBus#debugExecutionOrder(Class)} based on the currently registered handlers.
 	 *
 	 * @since 1.2.0
 	 */
 	@Test
 	void testPrintExecutionOrder() {
-		String executionOrder = bus.printExecutionOrder(SimpleEvent.class);
+		String executionOrder = bus.debugExecutionOrder(SimpleEvent.class);
 		System.out.println(executionOrder);
 		assertEquals(
 			"Event handler execution order for class dev.kske.eventbus.core.SimpleEvent (3 handler(s)):\n"