doc: fix vm_space doc (#334)

Author: Marsman1996

ostd/specs/mm/vm_space.rs

@@ -352,7 +352,7 @@ impl<'a> VmSpaceOwner<'a> {
     /// # Verified Properties
     /// ## Preconditions
     /// - The [`VmSpace`] invariants must hold with respect to the [`VmSpaceOwner`], which must be active.
-    /// - The writer must be well-formed with respect to the `[VmSpaceOwner`].
+    /// - The writer must be well-formed with respect to the [`VmSpaceOwner`].
     /// - The writer's virtual address range must be mapped within the [`VmSpaceOwner`]'s memory view.
     /// ## Postconditions
     /// - The writer will be added to the [`VmSpace`]'s writers list.

ostd/src/mm/vm_space.rs

@@ -205,7 +205,7 @@ impl<'a> VmSpace<'a> {
     /// The newly created instance of [`VmReader`] and its associated [`VmIoOwner`] are not yet
     /// activated, so the guarantees about the memory view only require that the memory view is
     /// [`None`]. The guarantees about the memory view will be provided by the activation function
-    /// (see [`Self::activate_reader`] and [`Self::activate_writer`]).
+    /// (see [`VmSpaceOwner::activate_reader`] and [`VmSpaceOwner::activate_writer`]).
     ///
     /// We avoid mixing the creation, usage and deletion into one giant function as this would
     /// create some unnecessary life-cycle management complexities and not really help with the