fs: doc fixes

uefi/src/fs/file_system/error.rs

@@ -28,8 +28,7 @@ pub struct IoError {
     pub uefi_error: crate::Error,
 }
 
-/// Enum that further specifies the context in that a [`Error`]
-/// occurred.
+/// Enum that further specifies the context in that an [`Error`] occurred.
 #[derive(Debug, Clone, Display, PartialEq, Eq)]
 pub enum FileSystemIOErrorContext {
     /// Can't delete the directory.

uefi/src/fs/mod.rs

@@ -21,11 +21,9 @@
 //! [`Path`] and [`PathBuf`].
 //!
 //! # API Hints
-//! There are no `File` and `Path` abstractions similar to those from `std` that
-//! are publicly exported. Instead, paths to files are provided as `&str`, and
-//! will be validated and transformed internally to the correct type.
-//! Furthermore, there are no `File` objects that are exposed to users. Instead,
-//! it is intended to work with the file system as in `std::fs`.
+//! There is no `File` abstraction as in the Rust `std` library. Instead, it is
+//! intended to work with the file system via dedicated functions, similar to
+//! the public functions of the `std::fs` module.
 //!
 //! There is no automatic synchronization of the file system for concurrent
 //! accesses. This is in the responsibility of the user.

uefi/src/fs/path/mod.rs

@@ -33,7 +33,7 @@ pub const SEPARATOR_STR: &CStr16 = uefi_macros::cstr16!("\\");
 
 /// Deny list of characters for path components. UEFI supports FAT-like file
 /// systems. According to <https://en.wikipedia.org/wiki/Comparison_of_file_systems>,
-/// paths should not contain the following symbols.
+/// paths should not contain these symbols.
 pub const CHARACTER_DENY_LIST: [Char16; 10] = unsafe {
     [
         NUL_16,