refactor: include continuation of admonition within the box

docs/velocity/dev/getting-started/api-basics.mdx

@@ -102,8 +102,6 @@ construction. Notably, you can't register an event listener in your constructor,
 have a valid plugin registration, but Velocity can't register the plugin until the plugin has been
 constructed, causing a "chicken or the egg" problem.
 
-:::
-
 To break this vicious cycle, you should always wait for initialization, which is indicated when
 Velocity fires the <Javadoc name={"com.velocitypowered.api.event.proxy.ProxyInitializeEvent"} project={"velocity"}>`ProxyInitializeEvent`</Javadoc>.
 We can do things on initialization by adding a listener for this event, as shown below.
@@ -118,6 +116,8 @@ public void onProxyInitialization(ProxyInitializeEvent event) {
 }
 ```
 
+:::
+
 ## Getting your plugin's directory
 
 At some point you may need your plugin's directory. To do this, add