Fix documentation for ProcInst and ProcDesc

Author: Raytwo

docs/app/procdesc/ProcDesc.md

@@ -1,3 +1,3 @@
-A Descriptor to be executed as part of a [`ProcInst`](crate::proc::ProcInst)
+A Descriptor to be executed as part of a [`ProcInst`](crate::app::procinst::ProcInst)
 
 Acts as a very high level assembly instruction that is executed sequentially.

docs/app/procinst/ProcInst.md

@@ -1,19 +1,7 @@
-Represents a Instruction unit for a [`Proc`].
+Represents an instruction unit for a [`Proc`](crate::app::proc::Proc).
 
 The ProcInst is chained to other ProcInsts to be executed in order by one of the three Proc instances of the game.
 
-They act as a high-level virtual machine to execute [instructions](crate::proc::ProcDesc) in sequence. Said instructions are queued in a ProcDesc array.
+They act as a high-level virtual machine to execute [instructions](crate::app::procdesc::ProcDesc) in sequence. Said instructions are queued in a ProcDesc array.
 
-A lot of classes inherit from it, so implement [`IsProcInst`] on them to represent this relation.
-
-If it is not possible for some reason, use the [cast](ProcInst::cast) methods to represent the chains as a ProcInst derivate of your choice.
-
-Example:
-
-```
-pub fn createmenubind_hook(proc: &mut Il2CppObject<ProcInst>) {
-    let casted_child = proc.child.cast_mut::<BasicMenu>();
-}
-```
-
-Keep in mind that [`IsProcInst`] is much more preferable, and [cast](ProcInst::cast) should only be used as a last resort.
+A lot of classes inherit from it; the bindgen emits `#[parent(...)]` chains so derived types coerce to `ProcInst` via the standard `Into` impls. For type-erased downcasts, use the methods on [`unity2::Cast`].