chore: fix typos (evmos#2570)

* fix typo Signed-off-by: omahs <[email protected]> * fix typos * fix typos * fix typo --------- Signed-off-by: omahs <[email protected]>
ramacarlucho · May 29, 2024 · fad3d97 · fad3d97
1 parent 6afe636
commit fad3d97
Show file tree

Hide file tree

Showing 4 changed files with 6 additions and 6 deletions.
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
@@ -3,7 +3,7 @@
 <!-- Add a description of the changes that this PR introduces and the files that
 are the most critical to review. -->
 
-<!-- Please keep your PR as draft until its ready for review -->
+<!-- Please keep your PR as draft until it's ready for review -->
 
 <!-- Pull requests that sit inactive for longer than 30 days will be closed.  -->
 

diff --git a/LICENSE_FAQ.md b/LICENSE_FAQ.md
@@ -45,7 +45,7 @@ transaction of economic value.
 
 "Designated Blockchains" refers to the version of the digital blockchain ledger
 that, at any given time, is recognized as canonical in accordance with the
-blockchain consensus.The initial Designated Blockchains shall be the Evmos
+blockchain consensus. The initial Designated Blockchains shall be the Evmos
 blockchains, identified by chain identifiers 9000 (testing network or testnet)
 and 9001 (main network or mainnet).
 
@@ -169,7 +169,7 @@ ENCL code in violation of the conditions of the license.
 to maintain the code as part of the ENCL-1.0 project. How do I contribute it?**
 
 **A:** First, a big thank you! You can contribute the code to the official Evmos
-repository by following the contributing guidelines a nd the official Code of
+repository by following the contributing guidelines and the official Code of
 Conduct (see CONTRIBUTING). You will need to sign a Contributor License
 Agreement (CLA) before your contribution is peer-reviewed and accepted. A bot
 has been implemented to assist you through the signing process when

diff --git a/SAFU.md b/SAFU.md
@@ -6,7 +6,7 @@ This Simple Arrangement for Funding Upload (the
 “[SAFU](https://jumpcrypto.com/safu-creating-a-standard-for-whitehats/)” or
 “Arrangement”) is intended as a simple yet extensible way to specify a
 post-exploit policy for whitehats, particularly rewards and distributions. It is
-based in the SAFU Framework designed by [Jump Crypto](https://jumpcrypto.com/).
+based on the SAFU Framework designed by [Jump Crypto](https://jumpcrypto.com/).
 
 This Arrangement attempts to address the following issues during active
 vulnerabilities and post-exploits:

diff --git a/SECURITY.md b/SECURITY.md
@@ -65,7 +65,7 @@ Once the vulnerability severity is defined, the following steps apply:
        We also publish a security Advisory on GitHub and publish a
        [CVE](https://en.wikipedia.org/wiki/Common_Vulnerabilities_and_Exposures)
 
-- For `Informational` , `Low` and `Medium` severities:
+- For `Informational`, `Low` and `Medium` severities:
     1. `Medium` and `Low` severity bug reports are included in a public issue
        and will be incorporated in the current sprint and patched in the next release.
        `Informational` reports are additionally categorized as with low or medium priority
@@ -133,7 +133,7 @@ excluded from scope:
 - Findings derived from social engineering (e.g., phishing).
 
 Examples of vulnerabilities that are of interest to us include memory allocation bugs, race conditions,
-timing attacks,information leaks, authentication bypasses, denial of service
+timing attacks, information leaks, authentication bypasses, denial of service
 (specifically at the application- or protocol-layer),
 lost-write bugs, unauthorized account or capability access, stolen or loss of funds, token inflation bugs,
 payloads/transactions that cause panics, non deterministic logic, etc.