*: fix doc build errors

Signed-off-by: Aleksa Sarai <[email protected]>

Author: cyphar

src/error.rs

@@ -149,11 +149,6 @@ pub enum Error {
         backtrace: Backtrace,
     },
 
-    /// The requested libpathrs operation directly resulted in an operating
-    /// system error. This should be contrasted with [`InternalOsError`]
-    /// (which is an error triggered internally by libpathrs while servicing
-    /// the user request).
-    ///
     /// The requested libpathrs operation resulted in a [`SyscallError`] by
     /// one of libpathrs's syscall wrappers. This should be contrasted with
     /// [`OsError`] -- which indicates an error triggered by a Rust stdlib

src/resolvers/mod.rs

@@ -86,7 +86,7 @@ impl ResolverBackend {
 /// conduct path resolutions. It's not recommended to change the
 /// [`ResolverBackend`] but it wouldn't hurt.
 ///
-/// [`Root`] /struct.Root.html
+/// [`Root`]: struct.Root.html
 /// [`ResolverBackend`]: enum.ResolverBackend.html
 #[derive(Copy, Clone, Debug, Default, Eq, PartialEq)]
 pub struct Resolver {

src/root.rs

@@ -55,7 +55,7 @@ pub enum InodeType<'a> {
 
     /// Symlink with the given [`Path`], as in [`symlinkat(2)`].
     ///
-    /// Note that symlinks can contain any arbitrary [`CStr`]-style string (it
+    /// Note that symlinks can contain any arbitrary `CStr`-style string (it
     /// doesn't need to be a real pathname). We don't do any verification of the
     /// target name.
     ///