nydus-image: fix some comments

Some comments are wrong or not accurate enough, fix them. Signed-off-by: zhaoshang <zhaoshangsjtu@linux.alibaba.com>
dragonflyoss · Jun 9, 2022 · 7916ce4 · 7916ce4
1 parent fdee599
commit 7916ce4
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/src/bin/nydus-image/core/node.rs b/src/bin/nydus-image/core/node.rs
@@ -193,7 +193,7 @@ pub struct Node {
     /// Device id associated with the source inode.
     ///
     /// A source directory may contain multiple partitions from different hard disk, so
-    /// a pair of (dev, read_ino) is needed to uniquely identify an inode from source directory.
+    /// a pair of (real_ino, dev) is needed to uniquely identify an inode from source directory.
     pub src_dev: u64,
     /// Inode number of the source inode.
     pub src_ino: Inode,

diff --git a/src/bin/nydus-image/core/prefetch.rs b/src/bin/nydus-image/core/prefetch.rs
@@ -16,7 +16,7 @@ use crate::node::Node;
 pub enum PrefetchPolicy {
     None,
     /// Readahead will be issued from Fs layer, which leverages inode/chunkinfo to prefetch data
-    /// from blob no mather where it resides(OSS/Localfs). Basically, it is willing to cache the
+    /// from blob no matter where it resides(OSS/Localfs). Basically, it is willing to cache the
     /// data into blobcache(if exists). It's more nimble. With this policy applied, image builder
     /// currently puts readahead files' data into a continuous region within blob which behaves very
     /// similar to `Blob` policy.