ipip-462: reword motivation

https://github.com/ipfs/specs/pull/462/files#r1492996318

Author: lidel

src/ipips/ipip-0462.md

@@ -25,11 +25,21 @@ This IPIP adds gateway support for optional `Ipfs-Path-Affinity` HTTP request he
 Endpoints that implement :cite[trustless-gateway] may receive requests for a
 single block, or a CAR request sub-DAG of a biger tree.
 
-Not every CID is announced today, some providers limit announcements to
-top-level root CIDs due to time and cost.
-The introduction of an optional `Ipfs-Path-Affinity` header can increase the success rate of the gateway retrieving the request block, especially if the requested block is not announced. 
-What does this mean for the ecosystem? It should adapt. Over time, both clients and
-servers should leverage the concept of "affinity".
+While every piece of data that is supposed to be able to be accessed
+independently should be advertised on routing system, not every CID is today.
+Some providers limit announcements to top-level root CIDs due to time, cost, or
+misconfiguration.
+
+What does this mean for the ecosystem? It should adapt and ensure
+implementations leverage all infromation provided by the end user.
+
+Over time, both clients and servers should leverage the concept of "affinity".
+
+The introduction of an optional `Ipfs-Path-Affinity` header aims to increase
+the success rate of the gateway retrieving internal standalone blocks or byte
+ranges, especially if the requested blocks are not announced on routing
+systems, but belong to a bigger DAG, and only the root CID of that parent DAG
+is announced.
 
 ## Detailed design