Standardize spacing in code comments for better readability. (#1020)

Co-authored-by: Dustin Brickwood <dustinbrickwood204@gmail.com>

docs/build/tooling/block-explorer/contract-verification.md

@@ -63,6 +63,6 @@ You can output the constructor argument data at deploy time by adding the follow
 const your_constructor_argument = "Hi there!";
 const myContract = await deployer.deploy(artifact, [your_constructor_argument]);
 
-//obtain the Constructor Arguments
+// obtain the Constructor Arguments
 console.log("constructor args:" + myContract.interface.encodeDeploy([your_constructor_argument]));
 ```

docs/build/tooling/hardhat/getting-started.md

@@ -235,7 +235,7 @@ export default async function (hre: HardhatRuntimeEnvironment) {
 
   const greeterContract = await deployer.deploy(artifact, [greeting]);
 
-  //obtain the Constructor Arguments
+  // obtain the Constructor Arguments
   console.log("constructor args:" + greeterContract.interface.encodeDeploy([greeting]));
 
   // Show the contract info.

docs/build/tutorials/smart-contract-development/account-abstraction/daily-spend-limit.md

@@ -211,7 +211,7 @@ The code below sets and removes the limit.
         _updateLimit(_token, 0, 0, 0, false);
     }
 
-   // verify if the update to a Limit struct is valid
+    // verify if the update to a Limit struct is valid
     // Ensure that users can't freely modify(increase or remove) the daily limit to spend more.
     function isValidUpdate(address _token) internal view returns (bool) {
         // Reverts unless it is first spending after enabling