diff --git a/.cargo/config.toml b/.cargo/config.toml
index 35342d8f2..079d24ee4 100644
--- a/.cargo/config.toml
+++ b/.cargo/config.toml
@@ -13,5 +13,4 @@ rustflags = [
 ]
 
 [alias]
-vfmt = "run-script vfmt" # Format verus codes
 verify = "v build --features verus"
diff --git a/Documentation/docs/developer/VERIFICATION.md b/Documentation/docs/developer/VERIFICATION.md
index ff646f139..e81a09832 100644
--- a/Documentation/docs/developer/VERIFICATION.md
+++ b/Documentation/docs/developer/VERIFICATION.md
@@ -1,12 +1,12 @@
 # VERIFICATION
 
-Formal verification is done via [Verus](https://github.com/verus-lang/verus).
-To run verification, you need to setup the verification tools in order to run
+Formal verification is done via [Verus](https://github.com/verus-lang/verus). 
+To execute verification, ensure you have set up the necessary tools to run
 `cargo verify`.
 
 ## Setup
 
-Run the following commands to install verus and cargo-verify.
+Run the following commands to install Verus tools.
 
 ```
 cd svsm
@@ -22,15 +22,16 @@ cd svsm/kernel
 cargo verify
 ```
 
-By default, it only verifies the current crate.
+By default, it only verifies the current crate (`cargo verify` is an alias of `cargo v --features verus`), while using spec/proof from external crates. To verify all external crates, run `cargo v --features verusall`
 
 
-### Pass verus arguments for verification.
 
-For debugging purposes, it may be helpful to pass additional Verus arguments.
-You can specify extra arguments using environmental variable
-{crate}_{lib/bin}_VERUS_ARGS to a specific crate
-{crate} or VERUS_ARGS to all crates.
+### Pass verus arguments for verification
+
+For debugging purposes, it is helpful to pass additional Verus arguments.
+You can specify extra arguments using the environmental variable
+{crate}_{lib/bin}_VERUS_ARGS for a specific crate
+{crate} or VERUS_ARGS for all crates.
 
 **Examples**
 
@@ -43,11 +44,9 @@ You can specify extra arguments using environmental variable
 * Compiles a crate while only verifying address module in svsm crate:
 
     ```
-    svsm_lib_VERUS_ARGS="--verify-module address" cargo verify
+    svsm_lib_VERUS_ARGS="--verify-module address --verify-function VirtAddr::new" cargo verify
     ```
 
-
-
 ### Build without verification
 
 ```
@@ -55,28 +54,92 @@ cd svsm/kernel
 cargo build
 ```
 
-## Developing specification and proof
+All Verus-related annotations, specifications, and proofs are ignored.
 
-While Verus allows you to write specifications and proofs in Rust, it's
-beneficial to use the verus!{} macro for a more concise, mathematical syntax
-similar to Dafny, F*, and Coq. To get started, be sure to read the [Verus
-Tutorial](https://verus-lang.github.io/verus/guide/overview.html)
+## Verification Plan
+
+- [x] Set up verification as an experimental development.
+- [ ] Verify SVSM kernel protocol (similar to [VeriSMo](https://github.com/microsoft/verismo))
+  - [ ] Allocator
+  - [ ] Page table
+  - [ ] Protocol
+- [ ] Verifying other security-critical components.
+
+## Verification Development
+
+To enable verification, developers need to add annotations in executable Rust
+and to write specification and proofs in ghost mode.
 
 
 ### Development Guidelines
 
-* Minimize annotations inside executable Rust.
-* For a module `x`, define code-related specification and proof in `x.verus.rs` .
-* Codes wrapped in verus!{} macro could be formatted via verusfmt.
-  ./script/vfmt.sh triggers verusfmt for `*.verus.rs`
-* Use external specification and proofs from
+* Code Collaboration: Unverified and verified code can co-exist. See [SVSM VeriSMo meeting](https://github.com/coconut-svsm/governance/blob/main/Meetings/Data/verismo-10-23-2024-talk.pdf) for more details.
+* Minimize Annotations: Keep simple annotations in executable Rust, by defining
+  complicated specifications in spec functions and group proofs.
+* Specification and Proof Structure: For each module `x`, define code-related
+  specification and proof in `x.verus.rs` .
+* Code Formatting: Use `cargo fmt` for excutable Rust. Codes wrapped in verus!{}
+  macro could be formatted via verusfmt. Run `./script/vfmt.sh` to format
+  `*.verus.rs`
+* Reusing spec/proof: Use external specification and proofs from
   [vstd](https://verus-lang.github.io/verus/verusdoc/vstd/) when possible.
-* When verifying with functions/structs/traits from external crates, define
-  specifications in `verify_external/` if `vstd` does not provide.
-* Expensive and reusable proofs are stored in `verify_proof/` if `vstd` does not
-  provide.
-
-```
-cd svsm
-cargo vfmt
+* Specifications for dependencies (external crates): If functions, structs, or
+  traits from external crates lack specifications from vstd, define their
+  specifications in `verify_external/`.
+* Performance: Store expensive and reusable proofs in `verify_proof/` if not
+  provided by `vstd`. The `svsm/build.rs` sets `rlimit=1`, while
+  `verify_proof/build.rs` sets `rlimit=4`, helping developers decide when they
+  need more proof engineering to run verification within minutes.
+
+### Annotation in Executable Rust
+
+* #[verus_verify]: Indicates the item is Verus-aware.
+* #[verus_verify(external_body)]: Indicates the item is Verus-aware, but marks the function body as uninterpreted by the verifier.
+* #[verus_verify(external)]: Instructs Verus to ignore the item. By default, items are treated as #[verus_verify(external)].
+* #[requires(x,y,z)]: Specifies preconditions to a function.
+* #[ensures(|ret: RetType| [x,y,z])]: Specifies postconditions to a function.
+* #[invariant(x,y,z)]: Specifies loop invariant.
+* proof!{...}: Inserts proofs to help solver to avoid false positives or improve
+  performance. You can also add assert(..) inside proof macro to statically
+  check assertions.
+
+For example,
+
+```rust
+
+use vstd::prelude::*;
+#[verus_verify]
+trait A: Sized {
+  #[requires(m > 0)]
+  #[ensures(|ret: usize| 0 <= ret < m )]
+  fn op(self, m: usize) -> usize;
+}
+
+#[verus_verify]
+impl A for usize {
+  // Failed postcondition.
+  fn op(self, m: usize) -> usize {
+    self
+  }
+}
+
+#[verus_verify]
+impl A for u64 {
+  // Verified.
+  fn op(self, m: usize) -> usize {
+    (self % (m as u64)) as usize
+  }
+}
 ```
+
+### Developing specification and proof (Verification developers)
+
+While Verus allows you to write specifications and proofs in Rust, it's
+beneficial to use the verus!{} macro for a more concise, mathematical syntax
+similar to Dafny, F*, and Coq. To get started, be sure to read the [Verus
+Tutorial](https://verus-lang.github.io/verus/guide/overview.html). To find
+examples about recursive proof, quantifier, traits, pointers, type invariant, or
+other advanced usage, please refer to [Verus
+Tests](https://github.com/verus-lang/verus/tree/main/source/rust_verify_test/tests)
+and [Verus
+Examples](https://github.com/verus-lang/verus/tree/main/source/rust_verify/example).