clarify goals

Signed-off-by: Miroslav Bajtoš <[email protected]>

FRCs/frc-retrieval-checking-requirements.md

@@ -36,10 +36,11 @@ Meeting these requirements needs support in software implementations like Boost,
 
 When we set out to build [Spark](https://filspark.com), a protocol for testing whether _payload_ of Filecoin deals can be retrieved back, we designed it based on how [Boost](https://github.com/filecoin-project/boost) worked at that time (mid-2023). Soon after FIL+ allocator compliance started to use Spark retrieval success score (Spark RSR) in mid-2024, we learned that [Venus](https://github.com/filecoin-project/venus) [Droplet](https://github.com/ipfs-force-community/droplet), an alternative miner software, is implemented slightly differently and requires tweaks to support Spark. Things evolved quite a bit since then. We need to overhaul most of the Spark protocol to support Direct Data Onboarding deals. We will need all miner software projects (Boost, Curio, Venus) to accommodate the new requirements imposed by the upcoming Spark v2 release.
 
-This FRC has three goals:
-1. Specify what Spark needs from miner software.
-2. Collaborate with the community to tweak the requirements to work well for all parties involved.
-3. Let this spec and the building blocks like [IPNI Reverse Index](https://github.com/filecoin-project/devgrants/issues/1781) empower other builders to design & implement their own retrieval-checking networks as alternatives to Spark.
+This FRC has the following goals:
+1. Document the retrieval process based on IPFS/IPLD.
+2. Specify what Spark needs from miner software.
+3. Collaborate with the community to tweak the requirements to work well for all parties involved.
+4. Let this spec and the building blocks like [IPNI Reverse Index](https://github.com/filecoin-project/devgrants/issues/1781) empower other builders to design & implement their own retrieval-checking networks as alternatives to Spark.
 
 ## Change Motivation
 <!--The motivation is critical for FIPs that want to change the Filecoin protocol. It should clearly explain why the existing protocol specification is inadequate to address the problem that the FIP solves. FIP submissions without sufficient motivation may be rejected outright.-->