docs: update

docs/pages/coro-blocking-code.mdx

@@ -27,6 +27,10 @@ try pool.start(std.testing.allocator, 0);
 defer pool.deinit(); // pool must always be destroyed before scheduler
 
 _ = try scheduler.spawn(task, .{&pool}, .{});
+
+// Or alternatively, which does the same as above
+_ = try pool.spawnForCompletition(&scheduler, blockingCode, .{}, .{});
+
 try scheduler.run();
 ```
 

docs/pages/coro-context-switches.mdx

@@ -22,3 +22,11 @@ switch (task.state(SomeEnum)) {
     value => task.wakeup(),
 }
 ```
+
+Shorthand for waking up task when the state is as expected.
+
+```zig
+task.wakeupIf(Task.SomeEnum);
+```
+
+Trying to wakeup a task that was not yielded by the user code is an programming error.

docs/pages/coro-io.mdx

@@ -25,4 +25,4 @@ outside a task then the call would be equal to calling the equal function from t
 Use `aio.Cancel` operation to cancel the currently running operations in a task.
 The `out_error` of such operation will then be set as `error.Canceled`.
 
-Alternatively it's possible to call `task.complete(.cancel);` to actively cancel a task and collect its partial result.
+Alternatively it's possible to call `task.cancel()`, or `task.complete(.cancel);` to actively cancel a task and collect its partial result.

docs/pages/coro-scheduler.mdx

@@ -31,19 +31,25 @@ yields or performs a IO operation using one of the `coro.io` namespace functions
 var task = try scheduler.spawn(entrypoint, .{ 1, "args" }, .{});
 ```
 
+In case the return type of the function can not be deduced by the compiler, use the spawnAny variant.
+
+```zig
+var task = try scheduler.spawnAny(void, entrypoint, .{ 1, "args" }, .{});
+```
+
 ### Collecting result from a task
 
 Use the following to collect a result of a task.
 After collecting the result, the task handle is no longer valid.
 
 ```zig
-const res = task.collect(.wait);
+const res = task.complete(.wait);
 ```
 
 To cancel and collect partial result.
 
 ```zig
-const res = task.collect(.cancel);
+const res = task.complete(.cancel);
 ```
 
 ### Running