Couple more fixes

node/core/prospective-parachains/src/fragment_tree.rs

@@ -619,7 +619,7 @@ impl FragmentTree {
 		let mut depths = bitvec![u16, Msb0; 0; max_depth + 1];
 
 		// iterate over all nodes where parent head-data matches,
-		// relay-parent number is <= candidate, and depth <= max_depth.
+		// relay-parent number is <= candidate, and depth < max_depth.
 		let node_pointers = (0..self.nodes.len()).map(NodePointer::Storage);
 		for parent_pointer in std::iter::once(NodePointer::Root).chain(node_pointers) {
 			let (modifications, child_depth, earliest_rp) = match parent_pointer {

roadmap/implementers-guide/src/node/backing/statement-distribution-legacy.md

@@ -33,7 +33,7 @@ Output:
 
 Implemented as a gossip protocol. Handles updates to our view and peers' views. Neighbor packets are used to inform peers which chain heads we are interested in data for.
 
-The Statement Distribution Subsystem is responsible for distributing signed statements that we have generated and for forwarding statements generated by other validators. It also detects a variety of Validator misbehaviors for reporting to [Misbehavior Arbitration](../utility/misbehavior-arbitration.md). During the Backing stage of the inclusion pipeline, Statement Distribution is the main point of contact with peer nodes. On receiving a signed statement from a peer in the same backing group, assuming the peer receipt state machine is in an appropriate state, it sends the Candidate Receipt to the [Candidate Backing subsystem](candidate-backing.md) to handle the validator's statement. On receiving `StatementDistributionMessage::Share` we make sure to send messages to our backing group in addition to random other peers, to ensure a fast backing process and getting all statements quickly for distribution.
+The Statement Distribution Subsystem is responsible for distributing signed statements that we have generated and for forwarding statements generated by other validators. It also detects a variety of Validator misbehaviors for reporting to the [Provisioner Subsystem](../utility/provisioner.md). During the Backing stage of the inclusion pipeline, Statement Distribution is the main point of contact with peer nodes. On receiving a signed statement from a peer in the same backing group, assuming the peer receipt state machine is in an appropriate state, it sends the Candidate Receipt to the [Candidate Backing subsystem](candidate-backing.md) to handle the validator's statement. On receiving `StatementDistributionMessage::Share` we make sure to send messages to our backing group in addition to random other peers, to ensure a fast backing process and getting all statements quickly for distribution.
 
 This subsystem tracks equivocating validators and stops accepting information from them. It establishes a data-dependency order: