Rectify typographical inaccuracies

README.md

@@ -38,7 +38,7 @@ Musig2 ensures the security and flexibility of Bitcoin's threshold signatures, w
 - ***zkstark ultra-light node:*** To optimize the light nodes mentioned above, zkstark technology can be used to realize the ultra-light nodes of BTC.
 
 ### Four advantages compared to other layer2/cross-chain bridges （Take [tBTC](https://www.thresholdusd.org/en/) as an example）
-- 1, ***No centralized initial setup required.*** There is no need to use sharding private keys to implement distributed threshold signatures, which avoids the security problem of private key leakage caused by sharding private keys.  Directly use BTC's native threshold signature scheme: [MuSig2](https://eprint.iacr.org/2020/1261).
+- 1, ***No centralized initial setup is required.*** There is no need to use sharding private keys to implement distributed threshold signatures, which avoids the security problem of private key leakage caused by sharding private keys.  Directly use BTC's native threshold signature scheme: [MuSig2](https://eprint.iacr.org/2020/1261).
 - 2, ***Distributed network on the chain, more decentralized.*** The validators of the distributed threshold network are all block verification nodes on the chain, and the network on the chain increases trust. It avoids the opaque and easy-to-operate defects of the distributed network under the chain.
 - 3, ***No permission required, just trust the code.*** The BTC to Layer2 network uses BTC light nodes. The blockchain logic of fully trusting the code avoids the centralized fraud problem caused by the submission of data oracle to the distributed network under the chain.
 - 4, ***Distributed network communication with complete privacy.*** The [Signal protocol](https://en.wikipedia.org/wiki/Signal_Protocol) is used to complete the communication problem of the BTC taproot threshold signature. Solve the privacy communication problem of distributed network. Avoid the risks of data leakage, collusion or external attacks when threshold signatures appear

contracts/ENS/README.md

@@ -72,7 +72,7 @@ Implementation of the ENS Registry, the central contract used to look up resolve
 
 ### ENSRegistryWithFallback
 
-The new impelmentation of the ENS Registry after [the 2020 ENS Registry Migration](https://docs.ens.domains/ens-migration-february-2020/technical-description#new-ens-deployment).
+The new implementation of the ENS Registry after [the 2020 ENS Registry Migration](https://docs.ens.domains/ens-migration-february-2020/technical-description#new-ens-deployment).
 
 ### FIFSRegistrar
 

contracts/ENS/contracts/auction/ClockAuction.sol

@@ -30,7 +30,7 @@ contract ClockAuction is Pausable, ClockAuctionBase {
     /// @param _nftAddress - address of a deployed contract implementing
     ///  the Nonfungible Interface.
     /// @param _tokenId - ID of token to auction, sender must be owner.
-    /// @param _startingPrice - Price of item (in wei) at beginning of auction.
+    /// @param _startingPrice - Price of item (in wei) at beginning of the auction.
     /// @param _endingPrice - Price of item (in wei) at end of auction.
     /// @param _duration - Length of time to move between starting
     ///  price and ending price (in seconds).

contracts/ENS/contracts/ethregistrar/BaseRegistrar.sol

@@ -20,7 +20,7 @@ abstract contract BaseRegistrar is Ownable, IERC721 {
     // The namehash of the TLD this registrar owns (eg, .eth)
     bytes32 public baseNode;
 
-    // A map of addresses that are authorised to register and renew names.
+    // A map of addresses that are authorized to register and renew names.
     mapping(address=>bool) public controllers;
 
     // Authorises a controller, who can register and renew domains.

contracts/ENS/contracts/resolvers/PublicResolver.sol

@@ -19,9 +19,9 @@ contract PublicResolver is Multicallable, ABIResolver, AddrResolver, ContentHash
     ENS ens;
 
     /**
-     * A mapping of operators. An address that is authorised for an address
+     * A mapping of operators. An address that is authorized for an address
      * may make any changes to the name that the owner could, but may not update
-     * the set of authorisations.
+     * the set of authorizations.
      * (owner, operator) => approved
      */
     mapping(address => mapping(address => bool)) private _operatorApprovals;

contracts/ENS/contracts/resolvers/Resolver.sol

@@ -13,7 +13,7 @@ import "./profiles/IPubkeyResolver.sol";
 import "./profiles/ITextResolver.sol";
 import "./ISupportsInterface.sol";
 /**
- * A generic resolver interface which includes all the functions including the ones deprecated
+ * A generic resolver interface that includes all the functions including the ones deprecated
  */
 interface Resolver is ISupportsInterface, IABIResolver, IAddressResolver, IAddrResolver, IContentHashResolver, IDNSRecordResolver, IDNSZoneResolver, IInterfaceResolver, INameResolver, IPubkeyResolver, ITextResolver {
     /* Deprecated events */

docs/xbtc_in_chainx_evm.md

@@ -1,7 +1,7 @@
 # [deprecated] XBTC in ChainX-EVM 
 
 ## 1. XBTC
-ChainX is the community-run layer2 network of bitcoin, and your portal into the world of Bitcoin ecosysterm.
+ChainX is the community-run layer2 network of bitcoin, and your portal into the world of Bitcoin ecosystem.
 Bitcoin on Chain is XBTC.
 
 ## 2. ChainX-EVM
@@ -660,4 +660,4 @@ When someone withdraw XBTC from evm to wasm, the total supply will decrease.
         "type": "function"
     }
 ]
-```
+```