From 8952c0a90fcf40cb9d42a89a28d3d653c3845ff9 Mon Sep 17 00:00:00 2001
From: Bukkit/Spigot <noreply+git-bukkit@papermc.io>
Date: Tue, 18 Jun 2024 06:45:40 +1000
Subject: [PATCH] Clarify ambiguity around what is API

By: md_5 <git@md-5.net>
---
 paper-api/src/main/javadoc/overview.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/paper-api/src/main/javadoc/overview.html b/paper-api/src/main/javadoc/overview.html
index b477a2259b..5d7dbc5278 100644
--- a/paper-api/src/main/javadoc/overview.html
+++ b/paper-api/src/main/javadoc/overview.html
@@ -18,10 +18,10 @@
     not guaranteed, especially across major versions. In particular the
     following is a (incomplete) list of things that are <b>not</b> API.
     <ul>
-    <li>Implementing interfaces. The Bukkit API is designed to only be
+    <li>Implementing interfaces or extending classes. The Bukkit API is designed to only be
     implemented by server software. Unless a class/interface is obviously
     designed for extension (eg {@link org.bukkit.scheduler.BukkitRunnable}), or
-    explicitly marked as such, it should not be implemented by plugins. Although
+    explicitly marked as such, it should not be implemented or extended by plugins. Although
     this can sometimes work, it is not guaranteed to do so and resulting bugs
     will be disregarded.</li>
     <li>Constructing inbuilt events. Although backwards compatibility is