chore: further touch up

ibc-core/ics24-host/cosmos/src/utils.rs

@@ -1,6 +1,6 @@
 use ibc_app_transfer_types::VERSION;
 use ibc_core_host_types::identifiers::{ChannelId, PortId};
-pub use ibc_primitives::prelude::*;
+use ibc_primitives::prelude::*;
 use sha2::{Digest, Sha256};
 
 /// Helper function to generate an escrow address for a given port and channel

ibc-core/ics25-handler/src/lib.rs

@@ -2,6 +2,14 @@
 //! entry points are responsible for processing incoming IBC messages,
 //! performing validation, and execution logics by invoking the appropriate
 //! module handler.
+//!
+//! When processing a given message `M`, if any method in this library returns
+//! an error, the runtime is expected to rollback all state modifications made
+//! to the context (e.g.
+//! [`ExecutionContext`](crate::core::host::ExecutionContext)) while processing
+//! `M`. If a transaction on your blockchain contains multiple messages, then
+//! typically the state modifications from all messages is expected to be rolled
+//! back as well.
 #![no_std]
 #![forbid(unsafe_code)]
 #![cfg_attr(not(test), deny(clippy::unwrap_used))]

ibc/src/lib.rs

@@ -30,14 +30,6 @@
 //! This is the part of the protocol that abstracts away the core protocol and
 //! focuses solely on business logic.
 //!
-//! When processing a given message `M`, if any method in this library returns
-//! an error, the runtime is expected to rollback all state modifications made
-//! to the context (e.g.
-//! [`ExecutionContext`](crate::core::host::ExecutionContext)) while processing
-//! `M`. If a transaction on your blockchain contains multiple messages, then
-//! typically the state modifications from all messages is expected to be rolled
-//! back as well.
-//!
 //! [ibc-standard]: https://github.com/cosmos/ibc
 //! [ibc-rs]: https://github.com/cosmos/ibc-rs