cdk section style checked

Author: kmurphypolygon

docs/cdk/how-to/index.md

@@ -1,4 +1,4 @@
-This section describes how to manage policies pertaining to data access in the case of a Validium.
+This section describes how to manage policies pertaining to data access in the case of a validium.
 
-Validia store data off-chain, and with this option comes the need to manage both the data and access to the data. This is facilitated through policies that stipulate which addresses can have access to data. Lists of addresses, such as the Allowlist and Denylist, are therefore kept to exclude or include certain addresses to having access.
+Validium architectures store data off-chain, and with this option comes the need to manage both the data and access to the data. This is facilitated through policies that stipulate which addresses can have access to data. Lists of addresses, such as the Allowlist and Denylist, are therefore kept to exclude or include certain addresses to having access.
 

docs/cdk/spec/index.md

@@ -2,6 +2,6 @@ This section gives a comparison between a validium and a zk-rollup.
 
 The main difference is the fact that a validium has a data availability layer whereas a zk-rollup does not. This difference alone is the reason for the substantially reduced gas fees for a validium compared to the zk-rollup.
 
-However, with this off-chain data availability, there is a trade-off between gas fees and security. Unlike in the zk-rollup, where forced batches are activated, the validium suffers from the possibility for the sequencer to go offline or the DAC to collude among themselves to withold state data.
+However, with this off-chain data availability, there is a trade-off between gas fees and security. Unlike in the zk-rollup, where forced batches are activated, the validium suffers from the possibility for the sequencer to go offline or the DAC to collude among themselves to withhold state data.
 
 What remains common between the two architectures is the generation of proofs.