find replace product name

Author: kmurphypolygon

docs/cdk/architecture/type-1-prover/intro-t1-prover.md

@@ -1,4 +1,4 @@
-The Polygon CDK type-1 prover is a zk-evm proving component used for creating proofs on your ZK-EVM chain. It has been developed in collaboration with the Toposware team.
+The Polygon Type-1 Prover is a zk-evm proving component used for creating proofs on your ZK-EVM chain. It has been developed in collaboration with the Toposware team.
 
 ## Get started
 

docs/cdk/architecture/type-1-prover/t1-architecture.md

@@ -1,4 +1,4 @@
-The Polygon CDK type-1 prover is designed for efficient implementation of STARK proofs and verification of Ethereum transactions. It achieves efficiency by restricting the Algebraic Intermediate Representation (AIR) to constraints of degree 3.
+The Polygon Type-1 Prover is designed for efficient implementation of STARK proofs and verification of Ethereum transactions. It achieves efficiency by restricting the Algebraic Intermediate Representation (AIR) to constraints of degree 3.
 
 The execution trace needed to generate a STARK proof can be assimilated to a large matrix, where columns are registers and each row represents a view of the registers at a given time.
 
@@ -25,19 +25,19 @@ In addition to the constraints of each module, this design requires an additiona
 
 For this reason, this design utilizes _Cross-table lookups_ (CTLs), based on a [logUp argument](https://eprint.iacr.org/2022/1530.pdf) designed by Ulrich Haböck, to cheaply add copy-constraints in the overall system.
 
-The Polygon CDK type-1 prover uses a central component dubbed the **CPU** to orchestrate the entire flow of data that occurs among the STARK modules during execution of EVM transactions. The CPU dispatches instructions and inputs to specific STARK modules, as well as fetches their corresponding outputs.
+The Polygon Type-1 Prover uses a central component dubbed the **CPU** to orchestrate the entire flow of data that occurs among the STARK modules during execution of EVM transactions. The CPU dispatches instructions and inputs to specific STARK modules, as well as fetches their corresponding outputs.
 
 Note here that “dispatching” and “fetching” means that initial values and final values resulting from a given operation are being copied with the CTLs to and from the targeted STARK module.
 
 ## Prover primitives
 
-We now look at the cryptographic primitives used to engineer the Polygon CDK type-1 prover, which is a custom-built prover capable of tracing, proving, and verifying the execution of the EVM through all state changes.
+We now look at the cryptographic primitives used to engineer the Polygon Type-1 Prover, which is a custom-built prover capable of tracing, proving, and verifying the execution of the EVM through all state changes.
 
 The proving and verification process is made possible by the zero-knowledge (ZK) technology. In particular, a combination of STARK[^1] and SNARK[^2], proving and verification schemes, respectively.
 
 ### STARK for proving
 
-The Polygon CDK type-1 prover implements a STARK proving scheme, a robust cryptographic technique with fast proving time.
+The Polygon Type-1 Prover implements a STARK proving scheme, a robust cryptographic technique with fast proving time.
 
 Such a scheme has a proving component, called the STARK prover, and a verifying component called the STARK verifier. A proof produced by the STARK prover is referred to as a STARK proof.
 

docs/cdk/architecture/type-1-prover/t1-cpu-component.md

@@ -1,4 +1,4 @@
-The CPU is the central component of the Polygon CDK type-1 prover. Like any central processing unit, it reads instructions, executes them, and modifies the state (registers and the memory) accordingly. 
+The CPU is the central component of the Polygon Type-1 Prover. Like any central processing unit, it reads instructions, executes them, and modifies the state (registers and the memory) accordingly. 
 
 Other complex instructions, such as Keccak hashing, are delegated to specialized STARK tables. 
 

docs/cdk/architecture/type-1-prover/testing-and-proving-costs.md

@@ -1,12 +1,12 @@
 ### Testing the prover
 
-Find a parser and test runner for testing compatible and common Ethereum full node tests against the Polygon CDK type-1 prover [here](https://github.com/0xPolygonZero/evm-tests).
+Find a parser and test runner for testing compatible and common Ethereum full node tests against the Polygon Type-1 Prover [here](https://github.com/0xPolygonZero/evm-tests).
 
 The prover passes all relevant and official [Ethereum tests](https://github.com/ethereum/tests/).
 
 ### Proving costs
 
-Instead of presenting gas costs, we focus on the cost of proving EVM transactions with the Polygon CDK type-1 prover.
+Instead of presenting gas costs, we focus on the cost of proving EVM transactions with the Polygon Type-1 Prover.
 
 Since the prover is more like a 'CPU' for the EVM, it makes sense to look at proving costs per VM instance used, as opposed to TPS or other benchmarks.
 

docs/cdk/how-to/deploy-t1-prover-devnet.md

@@ -60,7 +60,7 @@ Running a devnet like this provides the best way to understand Ethereum proof-of
 
 ## Type-1 prover testing procedure
 
-The aim of this devnet setup is to use Polygon CDK type-1 prover to test Erigon state witnesses.
+The aim of this devnet setup is to use Polygon Type-1 Prover to test Erigon state witnesses.
 
 The following steps create some test data.
 

docs/cdk/how-to/deploy-t1-prover.md

@@ -1,4 +1,4 @@
-This document shows you how to run the Polygon CDK type-1 prover, specifically for proving transactions, but with the option to test full blocks of less than 4M gas, which means it is similar to [`eth-proof`](https://github.com/wborgeaud/eth-proof) but for transaction proofs.
+This document shows you how to run the Polygon Type-1 Prover, specifically for proving transactions, but with the option to test full blocks of less than 4M gas, which means it is similar to [`eth-proof`](https://github.com/wborgeaud/eth-proof) but for transaction proofs.
 
 ## Quick start