concepts/index edited

Author: kmurphypolygon

docs/cdk/concepts/dac.md

@@ -32,7 +32,7 @@ The DAC works together with the sequencer to control the flow of data. The proce
 
 2. **Batch authentication**: Once the batches are assembled, they are authenticated. The sequencer forwards the batch data and its corresponding hash to the DAC.
 
-3. **Data validation and storage**:  The DAC nodes independently validate the batch data. Once validated, the hash is stored in each node's local database for future reference.
+3. **Data validation and storage**: The DAC nodes independently validate the batch data. Once validated, the hash is stored in each node's local database for future reference.
 
 4. **Signature generation**: Each DAC node generates a signature for the batch hash. This serves as an endorsement of the batch's integrity and authenticity.
 

docs/cdk/concepts/index.md

@@ -1,3 +1,3 @@
-This section covers some of the basic concepts needed to understand the CDK setting, which is a platform designed to allow developers to choose between validium and zk-rollup architectures.
+This section explores basic concepts underpinning CDK; a platform designed to allow developers to choose between validium and rollup architectures.
 
-Concepts such as a rollup, a validium and data availability committee (DAC) are defined. Implications of off-chain data availability are briefly discussed.
+The section currently defines concepts such as rollup, validium, and data availability committee (DAC). Some implications of off-chain data availability are mentioned.