Added and updated README.md as well as added 2-4 more methods, added a definition and function for all methods.

Fixed README.md

Fixed README.md (again)

Author: McCapy

README.md

@@ -2,11 +2,10 @@
 An API that allows you to execute, parallelize, and async code dynamically, and simply.
 
 > [!NOTE]
-> > This is not a shaded project. If you plan on using it then you will
-> > **Have** to have the dependency downloaded.
+> > This is not a shaded project.
 
 > [!WARNING]
-> > This project is very early in development. Beware that the API will
+> > This project is very early in development. Beware that the API **WILL**
 > > change, although functionality will still be extremely performant and well > verse.
 
 > [!NOTE]
@@ -57,7 +56,7 @@ public final MyPlugin extends JavaPlugin {
 ```
 ## Features & Methods
 While there are sparse features, there is a large sum of methods you can use to suit your needs.
-> [!FEATURES]
+> ## Features
 > - The ability to run code parallel.
 > - The ability to run code async.
 > - The ability to run code async, later joining it into the parent thread.
@@ -67,8 +66,8 @@ While there are sparse features, there is a large sum of methods you can use to
 > [!NOTE]
 > This is Extremely important to know,
 > There are **TWO** types of AsyncTask's
-> * Runnables
-> * Returnables
+> * **Runnables**
+> * **Returnables**
 > 
 > Runnables have a `AsyncTask<Void>` type
 > Returnables have a `AsyncTask<?>` where `?` is **NOT** `Void`
@@ -118,8 +117,16 @@ While there are sparse features, there is a large sum of methods you can use to
 > ### Behavior & Hooking Tasks
 > 
 > While examples and explanations will be provided further down, we will provide clarifications here.
-> Firstly, **Runnables** and **Returnables** can be converted between each other fluidly through **.after()**
-> Secondly, `.after()` should not be used as a substitution for `.onComplete()` or other events tied to threads. See more about events after this section.
+> 1. Firstly, **Runnables** and **Returnables** can be converted between each other fluidly through `**.after()**`
+> 2. Secondly, `.after()` should not be used as a substitution for `.onComplete()` or other events tied to threads. See more about events after this section.
+> ```java
+> void main() {
+>   AsyncTask<Integer> runnableToReturnable = 
+>       AsyncTask.of(() -> System.out.println("I Executed!")) // only a runnable
+>           .after(() -> 15) // it's now a returnable of type "Integer"
+>           .start(); // start thread to execute, will print "I Executed" and nothing else.
+> }
+> ```
 > 
 > ### Events
 >