chore(docs): proofreading the docs (#6129)

* Update extensions.mdx

* Update token.mdx

* Update single-pool.mdx

* Update algolia.css

docs/src/single-pool.mdx

@@ -99,7 +99,7 @@ $ solana config set --keypair usb://ledger/
 the wallet to draw funds from (for instance, to fund new stake accounts),
 and the signing authority on accounts that require one.
 When token accounts are required, it defaults to the default keypair's associated account.
-All of these roles can be overriden by command-line flags.
+All of these roles can be overridden by command-line flags.
 
   </TabItem>
   <TabItem value="jsc" label="WEB3.JS CLASSIC">

docs/src/theme/SearchBar/algolia.css

@@ -17,7 +17,7 @@
 .algolia-docsearch-suggestion--highlight {
   color: #3a33d1;
 }
-/* Highligted search terms in the main category headers */
+/* Highlighted search terms in the main category headers */
 .algolia-docsearch-suggestion--category-header
   .algolia-docsearch-suggestion--highlight {
   background-color: #4d47d5;

docs/src/token-2022/extensions.mdx

@@ -1811,7 +1811,7 @@ Token-2022 implements all of the instructions from the
 [spl-token-group-interface](https://github.com/solana-labs/solana-program-library/tree/master/token-group/interface).
 
 The group extension works directly with the group-pointer extension.
-To intialize group configurations within a mint, you must add the group-pointer
+To initialize group configurations within a mint, you must add the group-pointer
 extension, pointed at the mint itself, during mint creation.
 
 The tools do this for you automatically.
@@ -1886,7 +1886,7 @@ group address and the member's number, can be stored directly in the mint
 itself.
 
 The member extension, like the group extension, works directly with the
-member-pointer extension. To intialize member configurations within a mint,
+member-pointer extension. To initialize member configurations within a mint,
 you must add the member-pointer extension, pointed at the mint itself, during
 mint creation.
 

docs/src/token.mdx

@@ -978,7 +978,7 @@ account.
   <TabItem value="jsx" label="JS">
 
 The main difference in using multisign is specifying the owner as the multisig key,
-and giving the list of signers when contructing a transaction. Normally you would
+and giving the list of signers when constructing a transaction. Normally you would
 provide the signer that has authority to run the transaction as the owner, but in
 the multisig case the owner would be the multisig key.
 
@@ -1239,7 +1239,7 @@ console.log(`Minted ${mintInfo.supply} token`);
 
 ### Example: Offline signing with multisig
 
-Sometimes online signing is not possible or desireable. Such is the case for example when signers are not in the same geographic location
+Sometimes online signing is not possible or desirable. Such is the case for example when signers are not in the same geographic location
 or when they use air-gapped devices not connected to the network.  In this case, we use offline signing which combines the
 previous examples of [multisig](#example-mint-with-multisig-authority) with [offline signing](https://docs.solana.com/offline-signing)
 and a [nonce account](https://docs.solana.com/offline-signing/durable-nonce).