Merge branch 'main' of https://github.com/0xPolygon/polygon-docs into cdk/erigon-setup

Author: kmurphypolygon

.github/assets/nginx.conf

@@ -5,6 +5,8 @@ server {
 
     error_page 404 /404.html;
 
+    add_header Content-Security-Policy upgrade-insecure-requests;
+
     location / {
         try_files $uri.html $uri $uri/ =404;
     }

docs/img/404.png

@@ -19,4 +19,4 @@ You can obtain test MATIC for testing purposes on the Amoy testnet. Testnet toke
 3. Choose the **Polygon PoS (Amoy)** network.
 4. Enter your account address and confirm.
 
-For interactions between Sepolia and Amoy, consider using tools like [Matic.js](https://maticnetwork.github.io/matic.js/), or use the the [Polygon Portal](https://portal.polygon.technology/).
+For interactions between Sepolia and Amoy, consider using tools like [Matic.js](https://maticnetwork.github.io/matic.js/), or use the [Polygon Portal](https://portal.polygon.technology/).

docs/pos/concepts/tokens/matic.md

@@ -42,7 +42,7 @@ Choose the JavaScript project and go through these steps to compile, test and de
 
 ### Checking the contract
 
-The `contracts` folder contains `Lock.sol`, which is a sample contract which consistis of a simple digital lock, where users could only withdraw funds after a given period of time.
+The `contracts` folder contains `Lock.sol`, which is a sample contract which consists of a simple digital lock, where users could only withdraw funds after a given period of time.
 
 ```solidity
 // SPDX-License-Identifier: UNLICENSED

docs/tools/dApp-development/common-tools/hardhat.md

@@ -162,6 +162,6 @@ sol-merger \"./contracts/*.sol\" ./build
 
 - Choose the license type of your contract
 
-In the next section, paste your flattened samrt contract here. If you had enabled optimization, then adjust the `optimization` section accordingly.
+In the next section, paste your flattened smart contract here. If you had enabled optimization, then adjust the `optimization` section accordingly.
 
 Constructor arguments should have been filled in automatically. If not, they can be retrieved from the trailing bytes of the deployment transaction (example: `000000000000000000000000a6fa4fb5f76172d178d61b04b0ecd319c5d1c0aa`).

docs/tools/dApp-development/common-tools/remix.md

@@ -8,7 +8,7 @@ The stream client-server protocol messages are $\texttt{Start}$, $\texttt{StartB
 
     If the stream client knows the entry number at which the stream should start, it sends a $\texttt{Start}$ message with that particular entry number. That is, $\mathtt{entryNumber} \not= \texttt{0}$.
 
-- $\texttt{StartBookmark}$ message is the type of message the stream client can send if the the stream client does not the know entry number, but knows something more meaningful to the application, like a bookmark.
+- $\texttt{StartBookmark}$ message is the type of message the stream client can send if the stream client does not the know entry number, but knows something more meaningful to the application, like a bookmark.
 
     In the case of the Polygon zkEVM, if the stream client wants to receive information from a certain L2 block number, then it provides the appropriate bookmark by sending a $\texttt{StartBookmark}$ message.
 

docs/zkEVM/architecture/data-streamer/client-server-messages.md

@@ -27,7 +27,7 @@ In the non-recursive case, a PIL specification is transformed into a verifiable
 
 Subsequently, CIRCOM takes the above _STARK_ proof as an input and generates an _Arithmetic circuit_ and its corresponding _witness_.
 
-The Arithmetic circuit is expressed in terms of its equivalent _Rank-1 Constraint System (R1CS)_, while the _witness_ is actuallly a set of input, intermediate and output values of the circuit wires, satisfying the R1CS.
+The Arithmetic circuit is expressed in terms of its equivalent _Rank-1 Constraint System (R1CS)_, while the _witness_ is actually a set of input, intermediate and output values of the circuit wires, satisfying the R1CS.
 
 Finally, _Rapid SNARK_ takes the above Witness together with the _STARK Verifier data_ and generates a _SNARK_ proof corresponding to the previous _STARK_ proof.
 

docs/zkEVM/architecture/zkprover/stark-recursion/index.md

@@ -70,7 +70,7 @@ A schema of the _recursive2_ circuit generated is as shown in the below Figure.
 
 ![Figure 16: Convert the _recursive1_ circuit to its associated STARK](../../../../img/zkEVM/16prf-rec-recursive2-circuit.png)
 
-Observe that, since the upper proof is of the $\mathtt{\pi_{rec2}}$-type, the multiplexor does not provides the constant root _rootC_ to the _Verifier A_ for hardcoding it, because this verifier should get it through a public input from the previous circuit.
+Observe that, since the upper proof is of the $\mathtt{\pi_{rec2}}$-type, the multiplexor does not provide the constant root _rootC_ to the _Verifier A_ for hardcoding it, because this verifier should get it through a public input from the previous circuit.
 
 Otherwise, since the lower proof has the $\mathtt{\pi_{rec1}}$-type, the Multiplexor lets it pass through by providing the constant root to the Verifier B, so that it can be hardcoded when the corresponding template is filled.
 

docs/zkEVM/architecture/zkprover/stark-recursion/intermediate-recursion.md

@@ -1,7 +1,82 @@
 {% extends "main.html" %}
 
 {% block content %}
-  <h1>404 - Not found</h1>
+  <body
+    style="
+      height: 100dvh;
+      padding: 20px;
+      margin: 0;
+      width: 100%;
+    "
+  >
+    <div class="container"
+      style="
+      display: flex;
+      flex-direction: column;
+      align-items: center;
+      justify-content: center;
+      "
+    >
+      <p style="
+              font-size: 20px;
+              line-height: 26px;
+              font-family: Space Mono, monospace;
+            ">
+        ERROR
+      </p>
+      <p style="
+              font-size: 120px;
+              line-height: 120px;
+              margin: 0;
+              font-family: Space Mono, monospace;
+            ">
+      404
+    </p>
+    <img src="/img/404.png" alt="404 image" width="294" height="282">
+    <p
+      style="
+        font-size: 42px;
+        line-height: 48px;
+        font-weight: 500;
+        text-align: center;
+        margin: 0;
+        max-width: 100%;
+      "
+    >
+      Uh Oh. Sorry there&apos;s something wrong.
+    </p>
+    <p
+      style="
+        font-size: 20px;
+        line-height: 26px;
+        font-weight: 500;
+        color: #67666e;
+        text-align: center;
+        max-width: 100%;
+      "
+    >
+      We couldn&apos;t find the page you&apos;re looking for.
+    </p>
+    <button
+      style="
+        padding: 10px 14px 10px 14px;
+        border-radius: 48px;
+        outline: none;
+        border: none;
+        background: #7047eb;
+        color: #fff;
+        font-size: 12px;
+        line-height: 15.6px;
+        font-weight: 500;
+        cursor: pointer;
+      "
+      onclick="window.location.href = 'https://docs.polygon.technology'"
+    >
+      Back to Home
+    </button>
+  </body>
+</html>
+
 {% endblock %}
 
 {% block htmltitle %}