diff --git a/Cargo.lock b/Cargo.lock
index 778832f463..a309ee6c88 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -5435,6 +5435,12 @@ dependencies = [
  "num-traits",
 ]
 
+[[package]]
+name = "num-conv"
+version = "0.1.0"
+source = "registry+https://github.com/rust-lang/crates.io-index"
+checksum = "51d515d32fb182ee37cda2ccdcb92950d6a3c2893aa280e540671c2cd0f3b1d9"
+
 [[package]]
 name = "num-format"
 version = "0.4.4"
@@ -12053,12 +12059,13 @@ dependencies = [
 
 [[package]]
 name = "time"
-version = "0.3.31"
+version = "0.3.36"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "f657ba42c3f86e7680e53c8cd3af8abbe56b5491790b46e22e19c0d57463583e"
+checksum = "5dfd88e563464686c916c7e46e623e520ddc6d79fa6641390f2e3fa86e83e885"
 dependencies = [
  "deranged",
  "itoa",
+ "num-conv",
  "powerfmt",
  "serde",
  "time-core",
@@ -12073,10 +12080,11 @@ checksum = "ef927ca75afb808a4d64dd374f00a2adf8d0fcff8e7b184af886c3c87ec4a3f3"
 
 [[package]]
 name = "time-macros"
-version = "0.2.16"
+version = "0.2.18"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "26197e33420244aeb70c3e8c78376ca46571bc4e701e4791c2cd9f57dcb3a43f"
+checksum = "3f252a68540fde3a3877aeea552b832b40ab9a69e318efd078774a01ddee1ccf"
 dependencies = [
+ "num-conv",
  "time-core",
 ]
 
diff --git a/cli/main.rs b/cli/main.rs
index 73c2f6d6e1..f9263870cb 100644
--- a/cli/main.rs
+++ b/cli/main.rs
@@ -20,10 +20,12 @@
 //! Substrate's programmatic testing framework.
 //!
 //! > As the name suggests, `try-runtime` is a detailed testing framework that gives you a lot of
-//! control over what is being executed in which environment. It is recommended that user's first
-//! familiarize themselves with substrate in depth, particularly the execution model. It is critical
-//! to deeply understand how the wasm/client/runtime interactions, and the runtime apis work in the
-//! substrate runtime, before commencing to working with `try-runtime`.
+//! > control over what is being executed in which environment. It is recommended that user's first
+//! > familiarize themselves with substrate in depth, particularly the execution model. It is
+//! > critical
+//! > to deeply understand how the wasm/client/runtime interactions, and the runtime apis work in
+//! > the
+//! > substrate runtime, before commencing to working with `try-runtime`.
 //!
 //! #### Resources
 //!
@@ -176,9 +178,9 @@
 //!
 //! For the following examples, we assume the existence of the following:
 //!
-//! 1. a substrate node compiled with `--features try-runtime`, called `substrate`. This will be
-//! the running node that you connect to, and provide a wasm blob that has try-runtime
-//! functionality enabled.
+//! 1. a substrate node compiled with `--features try-runtime`, called `substrate`. This will be the
+//!    running node that you connect to, and provide a wasm blob that has try-runtime functionality
+//!    enabled.
 //! 2. the `try-runtime` CLI binary on your path.
 //!
 //! ```bash
@@ -200,8 +202,8 @@
 //! ```
 //!
 //! * Same as the previous example, but run it at specific block number's state and using the live
-//! polkadot network. This means that this block hash's state should not yet have been pruned by the
-//! node running at `rpc.polkadot.io`.
+//!   polkadot network. This means that this block hash's state should not yet have been pruned by
+//!   the node running at `rpc.polkadot.io`.
 //!
 //! ```bash
 //! try-runtime \