Merge branch 'main' into object-writer

examples/object.rs

@@ -20,7 +20,7 @@ use opendal::Operator;
 use opendal::Result;
 
 /// Visit [`opendal::services`] for more service related config.
-/// Visit [`opendal::Objecct`] for more object level APIs.
+/// Visit [`opendal::Object`] for more object level APIs.
 #[tokio::main]
 async fn main() -> Result<()> {
     let _ = env_logger::builder()

src/docs/concepts.rs

@@ -19,7 +19,7 @@
 //! There are three core concepts in OpenDAL:
 //!
 //! - [`Builder`]: Build an instance of underlying services.
-//! - [`Operator`]: A bridge between underlying implementation detail and  unified abstraction.
+//! - [`Operator`]: A bridge between underlying implementation detail and unified abstraction.
 //! - [`Object`]: The smallest unit representing a file/dir/... with path in specified services.
 //!
 //! If you are interested in internal implementation details, please have a look at [`internals`][super::internals].
@@ -80,7 +80,7 @@
 //! ```
 //!
 //! - `Operator` has it's internal `Arc`, so it's **cheap** to clone it.
-//! - `Operator` doesn't have generice parameters or lifetimes, so it's **easy** to use it everywhere.
+//! - `Operator` doesn't have generic parameters or lifetimes, so it's **easy** to use it everywhere.
 //! - `Operator` implements `Send` and `Sync`, so it's **safe** to send it between threads.
 //!
 //! # Object

src/error.rs

@@ -38,10 +38,10 @@ use std::fmt::Display;
 use std::fmt::Formatter;
 use std::io;
 
-/// Result that is a wrapper of `Reustl<T, opendal::Error>`
+/// Result that is a wrapper of `Result<T, opendal::Error>`
 pub type Result<T> = std::result::Result<T, Error>;
 
-/// ErrorKind is all kinds of opendal's Error.
+/// ErrorKind is all kinds of Error of opendal.
 #[derive(Clone, Copy, Debug, PartialEq, Eq)]
 #[non_exhaustive]
 pub enum ErrorKind {

src/raw/http_util/bytes_range.rs

@@ -39,8 +39,8 @@ use crate::Result;
 ///
 /// # Notes
 ///
-/// BytesRange support construct via rust native range syntex like `..`, `1024..`, `..2048`.
-/// But it's has different symantic on `RangeTo`: `..<end>`.
+/// BytesRange support construct via rust native range syntax like `..`, `1024..`, `..2048`.
+/// But it's has different semantic on `RangeTo`: `..<end>`.
 /// In rust, `..<end>` means all items that `< end`, but in BytesRange, `..<end>` means the
 /// tailing part of content, a.k.a, the last `<end>` bytes of content.
 ///