clean up

zksecurity · Oct 17, 2024 · 68608c7 · 68608c7
1 parent fb1a309
commit 68608c7
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 2 deletions.
diff --git a/source/starknet/fri.md b/source/starknet/fri.md
@@ -498,7 +498,7 @@ We process it in the following way:
 
 ### Query Phase
 
-FRI queries are generated once, and then refined through each reduction of the FRI protocol. The number of queries that is randomly generated is based on [configuration]().
+FRI queries are generated once, and then refined through each reduction of the FRI protocol. The number of queries that is pseudo-randomly generated is based on [configuration](#configuration).
 
 Each FRI query is composed of the following fields:
 
@@ -524,6 +524,8 @@ Or in terms of commitment, that the decommitment at path the path behind `index`
 
 <aside class="note">This is not exactly correct. The Commitment section explains that `index` points to a point, whereas we need to point to the path in the Merkle tree commitment that gathers its associated points. In addition, `y_value` only gives one evaluation, so the prover will need to witness associated evaluations surrounding the `y_value` as well (see Table Commitment section).</aside>
 
+See the [Converting A Query to a Path section of the Merkle tree specification](merkle.html#converting-a-query-to-a-path) for more details.
+
 #### Generating The First Queries
 
 The generation of each FRI query goes through the same process:

diff --git a/source/starknet/polynomial_commitment.md → source/starknet/merkle.md b/source/starknet/polynomial_commitment.md → source/starknet/merkle.md
diff --git a/source/starknet/stark.md b/source/starknet/stark.md
@@ -170,7 +170,7 @@ The oracle should provide the evaluations, under the same set of FRI queries (an
 * the traces polynomials, which include both the original trace polynomial and the interaction trace polynomial)
 * the composition column polynomials
 
-In addition the oracle should verify decommitment proofs (Merkle membership proofs) for each of these evaluations. We refer to the [Merkle Tree Polynomial Commitments specification](polynomial_commitment.html) on how to verify evaluation proofs.
+In addition the oracle should verify decommitment proofs (Merkle membership proofs) for each of these evaluations. We refer to the [Merkle Tree Polynomial Commitments specification](merkle.html) on how to verify evaluation proofs.
 
 <aside class="warning">The logic of the oracle must be implemented as part of the verification. The term "oracle" simply refers to an opaque callback function from the FRI protocol's perspective.</aside>