A few more fixes

Author: Mohammad Fawaz

documentation/cli/00_overview.md

@@ -17,7 +17,7 @@ You can print the list of commands by running `leo --help`
 - [`abi`](./02b_abi.md) - Generate an ABI JSON file from a compiled `.aleo` bytecode file.
 - [`account`](./01_account.md) - Create a new Aleo account, sign and verify messages.
   - [`new`](./01_account.md#leo-account-new) - Generates a new Aleo account.
-  - [`import`](./01_account.md#leo-account-import) - Derive and Aleo account from a private key.
+  - [`import`](./01_account.md#leo-account-import) - Derive an Aleo account from a private key.
   - [`sign`](./01_account.md#leo-account-sign) - Sign a message using your Aleo private key.
   - [`verify`](./01_account.md#leo-account-verify) - Verify a message and signature from an Aleo address.
 - [`add`](./02_add.md) - Add a new onchain or local dependency to the current project.

documentation/code_snippets/data_types/const_generic_consumer/program.json

@@ -0,0 +1,14 @@
+{
+  "program": "pair_user.aleo",
+  "version": "0.1.0",
+  "description": "",
+  "license": "MIT",
+  "dependencies": [
+    {
+      "name": "pair_lib",
+      "location": "local",
+      "path": "../const_generic_dep",
+      "edition": null
+    }
+  ]
+}

documentation/code_snippets/data_types/const_generic_consumer/src/main.leo

@@ -0,0 +1,16 @@
+program pair_user.aleo {
+    // ANCHOR: file
+    // Construct a const-generic struct defined in another package.
+    fn build() -> pair_lib::Pair::[3u32] {
+        return pair_lib::Pair::[3u32] { first: 1u32, second: 2u32 };
+    }
+
+    // Call a const-generic helper defined in another package.
+    fn triple(x: u32) -> u32 {
+        return pair_lib::scale::[3u32](x);
+    }
+    // ANCHOR_END: file
+
+    @noupgrade
+    constructor() {}
+}

documentation/code_snippets/data_types/const_generic_dep/program.json

@@ -0,0 +1,6 @@
+{
+  "program": "pair_lib",
+  "version": "0.1.0",
+  "description": "Library exposing a const-generic struct and helper.",
+  "license": "MIT"
+}

documentation/code_snippets/data_types/const_generic_dep/src/lib.leo

@@ -0,0 +1,10 @@
+// A const-generic pair, parameterised by an integer tag `N`.
+struct Pair::[N: u32] {
+    first: u32,
+    second: u32,
+}
+
+// A const-generic helper that scales `x` by the type-level constant `N`.
+fn scale::[N: u32](x: u32) -> u32 {
+    return x * N;
+}

documentation/code_snippets/migration/test_target/tests/test_test_program.leo

@@ -13,7 +13,6 @@ program test_test_program.aleo {
     @should_fail
     fn test_overflow() {
         let result: u8 = test_program.aleo::sum_u8(255u8, 1u8);
-        assert_eq(result, 0u8);
     }
 
     @noupgrade

documentation/code_snippets/testing/example_program/src/main.leo

@@ -22,6 +22,14 @@ program example_program.aleo {
     }
     // ANCHOR_END: mint_record
 
+    // ANCHOR: pause
+    const ADMIN: address = aleo1yzlta2q5h8t0fqe0v6dyh9mtv4aggd53fgzr068jvplqhvqsnvzq7pj2ke;
+
+    fn pause() {
+        assert_eq(self.signer, ADMIN);
+    }
+    // ANCHOR_END: pause
+
     @noupgrade
     constructor() {}
 }

documentation/code_snippets/testing/example_program/tests/test_example_program.leo

@@ -37,6 +37,19 @@ program test_example_program.aleo {
     }
     // ANCHOR_END: test_with_private_key
 
+    // ANCHOR: test_admin_pair
+    @test(private_key = "APrivateKey1zkpG9Af9z5Ha4ejVyMCqVFXRKknSm8L1ELEwcc4htk9YhVK")
+    fn test_admin_can_pause() {
+        example_program.aleo::pause();
+    }
+
+    @test
+    @should_fail
+    fn test_non_admin_cannot_pause() {
+        example_program.aleo::pause();
+    }
+    // ANCHOR_END: test_admin_pair
+
     @noupgrade
     constructor() {}
 }

documentation/guides/01_finalization.md

@@ -35,9 +35,7 @@ Leo enables developers to call entry functions from imported programs. A call to
 
 ### The `Final` Type
 
-`Final` is an opaque value: once produced, you can either run it (with `.run()`) or pass it onward to another finalize-aware function, but you **cannot** inspect, copy, reassign, pattern-destructure, or otherwise manipulate it. The compiler enforces this — every `Final` produced in a function must be consumed exactly once on every execution path, and any attempt to use a `Final` "in another way" produces an `ESAZ0374005` error (`Finals should be created, assigned to a variable, and consumed without being moved or reassigned`).
-
-In particular, expressions like `f.0`, `f.1`, … **do not** index the inputs of a `Final`. The `.N` syntax works only on tuples; if a function returns `(record, Final)`, then `result.0` is the record and `result.1` is the `Final` itself, but there is no syntax to peek at the inputs that the `Final` will pass to its finalize body.
+`Final` is an opaque value: once produced, you can either run it (with `.run()`) or pass it onward to another finalize-aware function, but you **cannot** inspect, copy, reassign, or otherwise manipulate it. The compiler enforces this — every `Final` produced in a function must be consumed exactly once on every execution path.
 
 If a finalize body needs values that were available in the caller's proof context, pass them as additional arguments to the finalize call rather than trying to extract them from the `Final` afterwards.
 
@@ -57,7 +55,7 @@ When binding a `Final` to a `let`, you have two options:
 
   `Final<Fn()>` is the type of a finalize value with no inputs (typically produced by an inline `final { }` block whose body references no external state).
 
-The two forms are interchangeable at the binding site; the compiler emits the same code for both. The parametric form is what `Final` expands to internally and what appears in error messages.
+The two forms are interchangeable at the binding site; the compiler emits the same code for both. The parametric form is what `Final` expands to internally and what appears in error messages. The type parameters of `Final` are used purely for type-checking the inputs supplied to `.run()`; there is no syntax to read the inputs from a `Final` value.
 
 ## Managing Both Public and Private State
 

documentation/guides/05_signing.md

@@ -51,7 +51,7 @@ leo account verify -a {$ADDRESS} -m 5field -s sign1signaturehere
 ✅ The signature is valid
 
 # Error Output:
-Error [ECLI0377002]: cli error: ❌ The signature is invalid
+Error: ❌ The signature is invalid
 ```
 
 To verify signatures of signed plaintext values, run:
@@ -64,5 +64,5 @@ leo account verify -a {$ADDRESS} --raw -m "Hello, Aleo" -s sign1signaturehere
 ✅ The signature is valid
 
 # Error Output:
-Error [ECLI0377002]: cli error: ❌ The signature is invalid
+Error: ❌ The signature is invalid
 ```