chore: prettier fix

src/pages/build-apps/guides/transaction-signing.md

@@ -238,13 +238,13 @@ interface ContractCallOptions {
 ```
 
 | parameter       | type             | required | description                                                                                                                                                                                                  |
-| --------------- | ---------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --- |
+| --------------- | ---------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
 | contractAddress | string           | true     | Stacks address to which contract is deployed                                                                                                                                                                 |
 | contractName    | string           | true     | Name of contract to sign                                                                                                                                                                                     |
 | functionName    | string           | true     | Name of function for signing / execution, which needs to be a [public function](/references/language-functions#define-public).                                                                               |
 | functionArgs    | `ClarityValue[]` | true     | Arguments for calling the function. [Learn more about constructing clarity values](https://github.com/blockstack/stacks.js/tree/master/packages/transactions#constructing-clarity-values). Defaults to `[]`. |
 | appDetails      | object           | true     | Dictionary that requires `name` and `icon` for app                                                                                                                                                           |
-| onFinish        | function         | true     | Callback executed by app when transaction has been signed and broadcasted. [Read more](#onFinish-option)                                                                                                     |     |
+| onFinish        | function         | true     | Callback executed by app when transaction has been signed and broadcasted. [Read more](#onFinish-option)                                                                                                     |  |
 | network         | StacksNetwork    | false    | Specify the network that this transaction should be completed on. [Read more](#network-option)                                                                                                               |
 
 ## Getting the signed transaction back after completion {#onFinish-option}

src/pages/understand-stacks/integrate-stacking-delegation.md

@@ -105,7 +105,6 @@ This method calls the [`delegate-stx`](/references/stacking-contract#delegate-st
 
 **Congratulations!** With the completion of this step, you successfully learnt how to use the Stacking library to delegate STX tokens as an account holder.
 
-
 ## Optional: Revoke delegation rights
 
 Delegators will be able to Stack STX tokens on the account holder's behalf until either the set burn height is reached or the account holder revokes the rights.
@@ -124,7 +123,6 @@ This method calls the [`revoke-delegate-stx`](/references/stacking-contract#revo
 
 -> To avoid handling private keys, it is recommended to use the [Stacks Wallet](https://www.hiro.so/wallet) to sign the revoke transaction
 
-
 ## Step 3: Stack delegated STX tokens
 
 With an established delegation relationship, the delegator can stack STX tokens on behalf of the account holder. This happens usually in a different client app than the delegation.
@@ -192,17 +190,13 @@ const delegetateCommitResponse = await delegatorClient.stackAggregationCommit({
 // }
 ```
 
-
 This method calls the [`stack-aggregation-commit`](/references/stacking-contract#stack-aggregation-commit) function of the Stacking contract. This call also includes locked Stacks from previous cycles. This is the second part of delegated stacking for the delegator.
 
 This method has to be called once for each reward cycle, even if all account holders have already locked their Stacks for several cycles in a row. If no new account holders are added to the pool, then this method call can be made even several cycles before the actual rewards cycle.
 
 Locking delegated Stacks together with a aggregation commits can be done several times before the cycle starts as long as the minimum increment amount of locked Stacks is met.
 
-
 **Congratulations!** With the completion of this step, you successfully learnt how to use the Stacking library to ...
 
 - Stack STX token on behalf of an account holder
 - Commit to Stacking with all delegated STX tokens
-
-