chore: fix some minor issues in the comments (#1018)

Signed-off-by: bytetigers <bytetiger@icloud.com>

Author: bytetigers

apps/nextra/pages/en/build/guides/aptos-keyless/integration-guide.mdx

@@ -22,7 +22,7 @@ At a high level, there are three steps to follow in order to integrate Keyless A
    2. Instantiate the user’s `KeylessAccount`
    3. Sign and submit transactions via the `KeylessAccount`.
 
-## Example Implementaion
+## Example Implementation
 
 You can find an example app demonstrating basic Keyless integration with Google in the [aptos-keyless-example repository](https://github.com/aptos-labs/aptos-keyless-example/). Follow the directions in the README to start with the example. For more detailed instructions on keyless, please read the rest of this integration guide.
 
@@ -31,7 +31,7 @@ You can find an example app demonstrating basic Keyless integration with Google
 
 The first step is to setup the configuration with your IdP(s).
 
-[Follow the intructions here](oidc-support.mdx)
+[Follow the instructions here](oidc-support.mdx)
 
 ### Step 2. Install the Aptos TypeScript SDK
 

apps/nextra/pages/en/build/sdks/ts-sdk/account/account-abstraction.mdx

@@ -268,7 +268,7 @@ console.log("Coin transfer transaction submitted! ", pendingCoinTransferTransact
 ### 7. Conclusion
 
 To verify that you have successfully sign and submitted the transaction using the abstracted account, you can use the explorer to check the transaction. If the 
-transaction signature contains a `function_info` and `auth_data` field, it means you succesfully used account abstraction! The full E2E demo can be found [here](https://github.com/aptos-labs/aptos-ts-sdk/blob/main/examples/typescript/public_key_authenticator_account_abstraction.ts).
+transaction signature contains a `function_info` and `auth_data` field, it means you successfully used account abstraction! The full E2E demo can be found [here](https://github.com/aptos-labs/aptos-ts-sdk/blob/main/examples/typescript/public_key_authenticator_account_abstraction.ts).
 
 ![Transaction Signature](https://i.imgur.com/HZylFnc.png)
 
@@ -618,7 +618,7 @@ console.log("Coin transfer transaction submitted! ", pendingCoinTransferTransact
 ### 8. Conclusion
 
 To verify that you have successfully sign and submitted the transaction using the abstracted account, you can use the explorer to check the transaction. If the 
-transaction signature contains a `function_info` and `auth_data` field, it means you succesfully used account abstraction! The full E2E demo can be found [here](https://github.com/aptos-labs/aptos-ts-sdk/blob/main/examples/typescript/public_key_authenticator_account_abstraction.ts)
+transaction signature contains a `function_info` and `auth_data` field, it means you successfully used account abstraction! The full E2E demo can be found [here](https://github.com/aptos-labs/aptos-ts-sdk/blob/main/examples/typescript/public_key_authenticator_account_abstraction.ts)
 
 ![Transaction Signature](https://i.imgur.com/3U40YSb.png)
 

apps/nextra/pages/en/build/smart-contracts/maps.mdx

@@ -175,8 +175,8 @@ Because it's layout affects what can be inserted and performance, there are a fe
 
 The Smart Table is a scalable hash table implementation based on linear hashing.
 This data structure aims to optimize storage and performance by utilizing linear hashing, which splits one bucket at a time instead of doubling the number of buckets, thus avoiding unexpected gas costs.
-Unfortunatelly, it's implementation makes every addition/removal be a conflict, making such transactions fully sequential.
-The Smart Table uses the SipHash function for faster hash computations while tolerating collisions. Unfortunatelly, this also means that collisions are predictable, which means that if end users can control the keys being inserted, it can have large number of collisions in a single bucket.
+Unfortunately, it's implementation makes every addition/removal be a conflict, making such transactions fully sequential.
+The Smart Table uses the SipHash function for faster hash computations while tolerating collisions. Unfortunately, this also means that collisions are predictable, which means that if end users can control the keys being inserted, it can have large number of collisions in a single bucket.
 
 ### SmartTable Structure