docs: fix some comments (#1633)

Signed-off-by: divdeploy <chenguangxue@outlook.com>

docs/aqd.rst

@@ -265,7 +265,7 @@ Solang Aqd simplifies this process by accepting these parameters as command-line
 Additionally, it ensures the submitted transaction aligns with the expected values in the Interface Description Language (IDL).
 
 .. note::
-  If unsure, you can always check the expected arguements and accounts for a specific function by using the ``show`` subcommand.
+  If unsure, you can always check the expected arguments and accounts for a specific function by using the ``show`` subcommand.
 
 Options specific to the ``call`` subcommand:
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

docs/code_gen_options.rst

@@ -59,7 +59,7 @@ Dead Storage pass
 
 Loading from contract storage, or storing to contract storage is expensive. This optimization removes any
 redundant load from and store to contract storage. If the same variable is read twice, then the value from
-the first load is re-used. Similarly, if there is are two successive stores to the same variable, the first
+the first load is re-used. Similarly, if there are two successive stores to the same variable, the first
 one is removed as it is redundant. For example:
 
 .. include:: ./examples/dead_storage_elimination.sol

docs/language/using.rst

@@ -21,7 +21,7 @@ The ``using`` declaration can be done on file scope. In this case, the type must
 be specified in place of ``*``. The first argument must match the type that is
 be used in the ``using`` declaration.
 
-If a user-defined type is used, the the ``global`` keyword can be used. This
+If a user-defined type is used, the ``global`` keyword can be used. This
 means the ``using`` binding can be used in any file, even when the type is
 imported.
 

docs/testing.rst

@@ -11,11 +11,11 @@ Solidity parser and semantics tests
 In the `tests <https://github.com/hyperledger/solang/tree/main/tests>`_ directory, there are
 a lot of tests which call `fn parse_and_resolve()`. This function parses Solidity, and returns
 the *namespace*: all the resolved contracts, types, functions, etc (as much as could be resolved),
-and all the compiler diagnositics, i.e. compiler warnings and errors. These tests check that
+and all the compiler diagnostics, i.e. compiler warnings and errors. These tests check that
 the compiler parser and semantic analysis work correctly.
 
-Note that Solidity can import other soldity files using the ``import`` statement. There are further
-tests which create a file cache with filenames and and their contents, to ensure that imports
+Note that Solidity can import other solidity files using the ``import`` statement. There are further
+tests which create a file cache with filenames and their contents, to ensure that imports
 work as expected.