fix(docs): Implement Kristap's comments

Author: nikerzetic-aflabs

docs/smart-accounts/3-custom-instruction.mdx

@@ -64,9 +64,9 @@ We expand the workflow described in the [Flare Smart Accounts overview](/smart-a
 Custom instructions are an array of the `CustomInstructions.CustomCall` Solidity struct.
 The struct contains three fields:
 
-- **targetContract**: the address of the smart contract that will execute the custom function
-- **value**: the amount of FLR paid to the contract
-- **data**: transaction calldata, which includes a function selector and values of the function's arguments
+- `targetContract`: the address of the smart contract that will execute the custom function
+- `value`: the amount of FLR paid to the contract
+- `data`: transaction calldata, which includes a function selector and values of the function's arguments
 
 Each of the custom instructions in the array will be performed in order.
 A call to the `targetContract` address is made, with the specified `value` and the calldata `data`.
@@ -108,7 +108,7 @@ function encodeCustomInstruction(
     }
 ```
 
-Behind the scenes, the `MasterAccountController` contract calls the `encodeCustomInstruction` function of the `CustomInstructions` library..
+Behind the scenes, the `MasterAccountController` contract calls the `encodeCustomInstruction` function of the `CustomInstructions` library.
 
 ```Solidity
 function encodeCustomInstruction(
@@ -128,6 +128,7 @@ We register a custom instruction by calling the `registerCustomInstruction` func
 The `CustomInstructions.CustomCall` array is provided as an argument.
 It is encoded as described above and stored in a `CustomInstructions` mapping.
 
-To obtain the instruction that can be sent as the memo of an XRPL Payment transaction, we do the following.
-We take the call hash, produced by the `encodeCustomInstruction` function, remove the first two bytes, and prepend to it the hexadecimal value `ff` and the `walletId`.
+To obtain the instruction that can be sent as the memo of an XRPL Payment transaction, we take the call hash produced by the `encodeCustomInstruction` function and modify it the following way.
+First, we remove the initial two bytes from this hash.
+Next, we prepend the hexadecimal value `ff` followed by the `walletId`.
 This is the encoded custom instruction.

docs/smart-accounts/guides/typescript-viem/01-state-lookup.mdx

@@ -14,7 +14,6 @@ keywords:
     flare-network,
     account-abstraction,
   ]
-unlisted: false
 ---
 
 import CodeBlock from "@theme/CodeBlock";

docs/smart-accounts/guides/typescript-viem/03-custom-instruction.mdx

@@ -109,7 +109,6 @@ contract NoticeBoard {
     function pinNotice(string memory message) public payable {
         require(msg.value > 0);
 
-        // NOTE:(Nik) The subscription is 1 FLR per month.
         uint256 duration = THIRTY_DAYS * (msg.value / 1 ether);
         uint256 expirationTimestamp = block.timestamp + duration;
 
@@ -428,7 +427,7 @@ async function waitForCustomInstructionExecutedEvent({
 }
 ```
 
-The vehicle for bridging the instruction is FDC, which puts a maximum cap of 180 seconds on the process duration.
+The vehicle for bridging the instruction is the [Flare Data Connector](/fdc/overivew), which puts a maximum cap of 180 seconds on the process duration.
 
 ## Full script
 
@@ -525,3 +524,4 @@ CustomInstructionExecuted event: {
   blockTimestamp: undefined
 }
 ```
+