fix(language): fix broken english language

packages/grc-stamp-frontend/src/routes/about/Chapters/About.tsx

@@ -10,19 +10,24 @@ function ChapterAbout() {
       </Typography>
       <Box component="article">
         <Typography gutterBottom variant="body1" component="p">
-          This service is intended to provide a simple implementation of the Proof of Existence method on the Gridcoin blockchain.
-          You can anonymously and securely store the proof of the existence of any of your documents (images, videos, documents, binaries...) in the distributed ledger.
+          This service provides a straightforward implementation of the Proof of Existence concept on the Gridcoin blockchain.
+          You can securely and anonymously store proof of the existence of any of your documents (e.g. images, videos, documents, binaries)
+          in the decentralized ledger without revealing the actual content of the document.
         </Typography>
         <Typography gutterBottom variant="body1" component="p">
-          <b>We DO NOT store any of your data (except the document hash of course). We store your documents neither in our database nor in the blockchain. Furthermore, your documents are NOT uploaded to the server. </b>
-          The document is required to calculate sha256 of it, these calculations are done in the browser (on the client-side) only.
+          <b>
+            We do not store any of your data (with the exception of the document&apos;s hash).
+            Your documents are not uploaded to our database or stored on the blockchain, and they never leave your device.
+          </b>
+          The document&apos;s SHA-256 hash is calculated client-side, in your browser, to ensure the security of your data.
         </Typography>
         <Typography gutterBottom variant="body1" component="p">
-          We do not use any of the tracking pixels, the only exception is
+          We also prioritize privacy and do not use any tracking pixels.
+          The only exception is
           {' '}
           <Link href="https://github.com/plausible/analytics" rel="nofollow">Plausible</Link>
           {' '}
-          which claims to be the privacy-friendly web analytics alternative to Google Analytics.
+          , which is considered a privacy-friendly alternative to Google Analytics.
         </Typography>
       </Box>
     </Box>

packages/grc-stamp-frontend/src/routes/about/Chapters/Costs.tsx

@@ -10,26 +10,26 @@ function ChapterCosts() {
       </Typography>
       <Box component="article">
         <Typography gutterBottom variant="body1" component="p">
-          At the moment of writing this article, the cost of the stamp transaction is relatively low.
-          It consists of the amount burned plus transaction fees.
-          The amount to be burned is
-          {' '}
+          As of the time of writing, the cost of a stamp transaction is low, consisting of a small burned amount
+          (
           <b>0.00000001</b>
           {' '}
-          grc (one Halford), plus a fee (may vary, it depends on the transaction size and network load) is approximately
+          grc or one
           {' '}
-          <b>0.05</b>
+          <b>Halford</b>
+          ) and a transaction fee (approximately
           {' '}
-          grc. So the average price is about
+          <b>0.05 grc</b>
+          ). The average cost is around
           {' '}
           <b>0.06</b>
           {' '}
           grc per proof.
         </Typography>
         <Typography gutterBottom variant="body1" component="p">
-          <b>The service is provided free of charge, </b>
-          although this could be reconsidered in the future if demand will be high.
-          But considering the low price, demand, and amount of donations at the moment of writing this article, the service is ready to remain free for years.
+          <b>The service is currently offered for free</b>
+          , but this may change in the future if demand is high.
+          Currently, the low cost and level of donations suggest that the service will remain free for the foreseeable future.
         </Typography>
       </Box>
     </Box>

packages/grc-stamp-frontend/src/routes/about/Chapters/ProofOfExistence.tsx

@@ -10,28 +10,28 @@ function ChapterProofOfExistence() {
       </Typography>
       <Box component="article">
         <Typography gutterBottom variant="body1" component="p">
-          The Proof of Existence is all about recording and proving that certain data existed at the given time.
-          To maintain PoE the only timestamp and signature associated with the entity are required to prove in front of the authorized viewers that a particular entity was created at a particular time.
-          Blockchain technology gets very handy for this purpose. As proof gets stored on the public ledger, it is public and can never be modified or removed.
+          Proof of Existence is a method of verifying and recording that specific data existed at a certain time.
+          To establish proof, a timestamp and signature linked to the entity are needed to demonstrate its creation at a particular time.
+          Blockchain technology provides a convenient solution for this purpose, as proof is stored on a public ledger that is transparent, unalterable, and permanent.
         </Typography>
         <Typography gutterBottom variant="body1" component="section">
-          Common usecases:
+          Common Use Cases:
           <ul>
             <li>
               <b>Proof of ownership.</b>
               <br />
-              The owner of the data can prove the ownership of the data without revealing actual data.
+              The owner of the data can confirm ownership without revealing the actual data.
             </li>
             <li>
               <b>Data timestamping.</b>
               <br />
-              You can prove that certain data existed and a given time without a need of a central authority.
+              You can prove the existence of specific data at a particular time without relying on a central authority.
             </li>
             <li>
-              <b>Checking for data integrity.</b>
+              <b>Data Integrity Checking.</b>
               <br />
-              The slightest change in the document (even one bit is enough) will result in generating a completely different file hash.
-              So if you create a stamp of your data and then re-check it later, you can be sure that data wasn&apos;t changed.
+              If there is even the slightest change in the document (even a single bit), it will result in a different file hash.
+              By creating a stamp of your data and verifying it later, you can ensure that the data has not been altered.
             </li>
           </ul>
         </Typography>

packages/grc-stamp-frontend/src/routes/about/Chapters/Protocol.tsx

@@ -16,16 +16,15 @@ function ChapterProtocol() {
   return (
     <Box pb={3} id="protocol-overview">
       <Typography variant="h4" component="h3" pb={2}>
-        Protocol Overview
+        Protocol Summary
       </Typography>
       <Box component="article">
         <Typography gutterBottom variant="body1" component="p">
-          The data is stamped via embedding the sha256 hash of the data in the gridcoin blockchain.
-          A special transaction gets generated that encodes the hash via OP_RETURN script which marks the transaction&apo;s output as unspendable.
-          This script allows a small amount of data to be inserted.
+          The data is stamped on the Gridcoin blockchain by embedding the sha256 hash of the data in a transaction.
+          This is achieved through the use of an OP_RETURN script opcode, which creates an unspendable output in the transaction that encodes the hash.
         </Typography>
         <Typography gutterBottom variant="body1" component="p">
-          The typical transaction may look like this:
+          A typical transaction may contain one or two hashes, such as:
         </Typography>
         <CodePaper variant="outlined" elevation={0}>
           6a265ea1ed0000015f334f14161952476adde3fbd843f93f647d47a0d7e30eb5d1635fb7569a2503
@@ -37,11 +36,13 @@ function ChapterProtocol() {
           6a465ea1ed0000015bbbbbee48b735693478140de1b7f09fe0acddc0c7bce87f8665074efe53410f7158380aca149fa8422fb1274a69155303d4aaa76bf67defe0bb31628293afd2
         </CodePaper>
         <Typography gutterBottom variant="body1" component="p">
-          The difference between those two is that the second transaction has 2 hashes instead of one. The data allowed with the OP_RETURN script is sufficient to keep two sha256 hashes, so it is totally fine to have more than a single record.
-          It also helps to save on fees, as instead of two separate transactions we can have just one.
+          The key difference between the two transactions is that the second one includes two hashes,
+          while the first one only has one.
+          The OP_RETURN script is capable of accommodating two sha256 hashes, allowing for more than one record to be stored in a single transaction.
+          This not only helps to save on fees but also makes it more efficient.
         </Typography>
         <Typography gutterBottom variant="body1" component="p">
-          Let&apos;s see what the transaction consists of:
+          Let&apos;s take a closer look at what makes up the transaction:
         </Typography>
         <CodePaper variant="outlined" elevation={0}>
           <b>6a46</b>
@@ -51,25 +52,25 @@ function ChapterProtocol() {
           <br />
           <b>5ea1ed</b>
           {' '}
-          - The code, special character sequence, so we can recognize stamp transactions and process them. This is a `Hex word` and it reads like &ldquo;Sealed&rdquo;.
+          - A unique sequence of characters that helps identify the stamp transaction and process it. This is known as a &ldquo;hex word&rdquo; and reads as &ldquo;Sealed&rdquo;.
           <br />
           <br />
           <b>000001</b>
           {' '}
-          - Protocol version. We use
+          - The protocol version. The current version at the time of writing is 0.0.1, using
           {' '}
           <Link rel="nofollow" href="https://semver.org/">semantic versioning</Link>
-          , the current protocol version is 0.0.1. All further versions of the current service shall support all legacy protocols.
+          . All future versions shall support legacy protocols.
           <br />
           <br />
           <b>5bbbbbee48b735693478140de1b7f09fe0acddc0c7bce87f8665074efe53410f</b>
           {' '}
-          - First sha256 hash
+          - The first sha256 hash.
           <br />
           <br />
           <b>7158380aca149fa8422fb1274a69155303d4aaa76bf67defe0bb31628293afd2</b>
           {' '}
-          - Second sha256 hash (may not be presented)
+          - The second sha256 hash (if present).
         </CodePaper>
       </Box>
     </Box>

packages/grc-stamp-frontend/src/routes/about/Contents.tsx

@@ -35,7 +35,7 @@ export function Contents() {
         <Link href="#protocol-overview" passHref>
           <ListItem disablePadding>
             <ListItemButton>
-              <ListItemText>Protocol Overview</ListItemText>
+              <ListItemText>Protocol Summary</ListItemText>
             </ListItemButton>
           </ListItem>
         </Link>

packages/grc-stamp-frontend/src/routes/notarize/Instructions/Instructions.tsx

@@ -44,26 +44,25 @@ function InstructionsComponent() {
         <TextBox>
           <GradientLine />
           <Typography component="h1" variant="h4" mb={3}>
-            Notarize documents with Gridcoin blockchain
+            Notarize Documents with the Gridcoin Blockchain
           </Typography>
           <Text variant="body1" gutterBottom>
-            Timestamping of documents can allow a public verification of the issue history
-            which is permanently recorded to the public blockchain.
-            There is absolutely no way of potential malicious modification at a later stage.
-            Learn more
+            Timestamping your documents with the Gridcoin blockchain allows for a publicly
+            verifiable record of their creation and history.
+            This ensures that there is no possibility of malicious
+            modifications being made at a later time. To learn more, click
             {' '}
             <Link href="/about" passHref>
               <MLink>here</MLink>
             </Link>
             .
           </Text>
           <Text variant="body1" gutterBottom>
-            In order to notarize the document or check the proof of existence
-            {' '}
-            just drop the target file down below and follow the instructions.
+            To notarize a document or verify its existence,
+            simply drag and drop the target file below and follow the provided instructions.
           </Text>
           <Text variant="body1" gutterBottom>
-            The service is provided free of charge.
+            Our service is offered at no cost to you.
           </Text>
         </TextBox>
       </Wrapper>