chore: use args in deployments script

src/account/NexusSmartAccount.ts

@@ -186,7 +186,7 @@ export class NexusSmartAccount extends BaseSmartContractAccount {
    * This method will create a NexusSmartAccount instance but will not deploy the Smart Account
    * Deployment of the Smart Account will be donewith the first user operation.
    *
-   * - Docs: https://docs.biconomy.io/Account/integration#integration-1
+   * - Docs: https://docs.biconomy.io/account/integration#integration-1
    *
    * @param nexusSmartAccountConfig - Configuration for initializing the NexusSmartAccount instance {@link NexusSmartAccountConfig}.
    * @returns A promise that resolves to a new instance of NexusSmartAccount.
@@ -1008,7 +1008,7 @@ export class NexusSmartAccount extends BaseSmartContractAccount {
    * @returns Promise<Hash>
    * Sends a user operation
    *
-   * - Docs: https://docs.biconomy.io/Account/transactions/userpaid#send-useroperation
+   * - Docs: https://docs.biconomy.io/account/methods#senduserop-
    *
    * @param userOp Partial<{@link UserOperationStruct}> the userOp params to be sent.
    * @param params {@link SendUserOpParams}.
@@ -1253,7 +1253,7 @@ export class NexusSmartAccount extends BaseSmartContractAccount {
   /**
    * Sends a transaction (builds and sends a user op in sequence)
    *
-   * - Docs: https://docs.biconomy.io/Account/transactions/userpaid#send-transaction
+   * - Docs: https://docs.biconomy.io/account/methods#sendtransaction-
    *
    * @param manyOrOneTransactions Array of {@link Transaction} to be batched and sent. Can also be a single {@link Transaction}.
    * @param buildUseropDto {@link BuildUserOpOptions}.
@@ -1353,7 +1353,7 @@ export class NexusSmartAccount extends BaseSmartContractAccount {
    *
    * This method will also simulate the validation and execution of the user operation, telling the user if the user operation will be successful or not.
    *
-   * - Docs: https://docs.biconomy.io/Account/transactions/userpaid#build-useroperation
+   * - Docs: https://docs.biconomy.io/account/methods#builduserop-
    *
    * @param transactions Array of {@link Transaction} to be sent.
    * @param buildUseropDto {@link BuildUserOpOptions}.

src/modules/utils/Helper.ts

@@ -19,7 +19,7 @@ import type {
 /**
  * Rule
  *
- * https://docs.biconomy.io/Modules/abiSessionValidationModule#rules
+ * https://docs.biconomy.io/modules/sessions/sessionvalidationmodule
  *
  * Rules define permissions for the args of an allowed method. With rules, you can precisely define what should be the args of the transaction that is allowed for a given Session. Every Rule works with a single static arg or a 32-byte chunk of the dynamic arg.
  * Since the ABI Encoding translates every static param into a 32-bytes word, even the shorter ones (like address or uint8), every Rule defines a desired relation (Condition) between n-th 32bytes word of the calldata and a reference Value (that is obviously a 32-bytes word as well).
@@ -31,7 +31,7 @@ import type {
 //    *
 //    * offset
 //    *
-//    * https://docs.biconomy.io/Modules/abiSessionValidationModule#rules
+//    * https://docs.biconomy.io/modules/sessions/sessionvalidationmodule
 //    *
 //    * The offset in the ABI SVM contract helps locate the relevant data within the function call data, it serves as a reference point from which to start reading or extracting specific information required for validation. When processing function call data, particularly in low-level languages like Solidity assembly, it's necessary to locate where specific parameters or arguments are stored. The offset is used to calculate the starting position within the calldata where the desired data resides. Suppose we have a function call with multiple arguments passed as calldata. Each argument occupies a certain number of bytes, and the offset helps determine where each argument begins within the calldata.
 //    * Using the offset to Extract Data: In the contract, the offset is used to calculate the position within the calldata where specific parameters or arguments are located. Since every arg is a 32-bytes word, offsets are always multiplier of 32 (or of 0x20 in hex).