markdown lint

docs/book/src/forc/plugins/forc_client/index.md

@@ -3,13 +3,15 @@
 Forc plugin for interacting with a Fuel node. Since transactions are going to require some gas, you need to sign them with an account that has enough tokens to pay for them.
 
 We offer multiple ways to sign the transaction:
+
   1. Sign the transaction via your local wallet using forc-client which integrates with our CLI wallet, forc-wallet.
   2. Use the default signer to deploy to a local node
   3. Use forc-wallet to manually sign transactions, and copy the signed transaction back to forc-client.
 
 The easiest and recommended way to interact with deployed networks, such as our testnets is the option 1, using forc-client to sign your transactions which reads your default forc-wallet vault. For interacting with local node, we recommend using the second option, which leads forc-client to sign transactions with the a private key that comes pre-funded in local environments.
 
 ## Option 1: Sign transactions via forc-client using your local forc-wallet vault
+
 If you used forc-wallet before, a vault which securely holds your private key is created and written to your file-system in a password encrypted format. forc-client is compatible with forc-wallet such that it can read that vault by asking you your password and use your account to sign transactions.
 
 Example:
@@ -48,6 +50,7 @@ As it can be seen from the example, forc-client asks for your password to decryp
 If you are not interacting with a deployed network, such as testnets, your local fuel-core environment can be structured such that it funds an account by default. Using `--default-signer` flag with forc-client binaries (run, deploy) will instruct forc-client to sign transactions with this pre-funded account. Which makes it a useful command while working against a local node.
 
 Example:
+
 ```console
 > forc deploy --default-signer