Update OPEN_PROBLEMS/DECENTRALIZED_DATA_DELIVERY_MARKETS.md

Co-authored-by: Jorge Soares <[email protected]>

Author: yiannisbot

OPEN_PROBLEMS/DECENTRALIZED_DATA_DELIVERY_MARKETS.md

@@ -238,7 +238,7 @@ The area of graph forming for Decentralised Data Delivery Markets revolves aroun
 
 In order to achieve the above goals, we need to answer certain architectural questions: where do end-users connect (e.g., to a retrieval miner, or to a separate content resolution system), which entity in the architecture makes content resolution and request forwarding decisions and finally, which entity(ies) has(ve) the required knowledge to forward requests to the closest (to the requesting user) copy, _aka_ nearest replica routing.
 
-We generally consider that retrieval miners are relatively powerful devices with local storage dedicated to storing hot copies of the content, high uptime (close to zero churn) and ideally public IP (i.e., reachable from anywhere). The architecture should ideally be able to take advantage of storage in less-powerful and more ephemerally-connected end-user devices, such as laptops and mobile phones - this is discussed as a different area further down. Although not a strict requirement, this is what will make the decentralised storage network take the full benefit of planetary-scale unused storage.
+We generally consider that retrieval miners are relatively powerful devices with local storage dedicated to storing hot copies of the content, high uptime (close to zero churn) and, ideally, a public IP address (reachable from anywhere). The architecture should be able to take advantage of storage in less powerful and intermittently-connected end-user devices, such as laptops and mobile phones - this is discussed as a different area further down. Although not a strict requirement, this is what will make the decentralised storage network take full benefit of planetary-scale unused storage.
 
 It is worth highlighting that the system should be able to serve different use-cases and therefore different setups and architectures could apply depending on the use-case. For instance, the content resolution system can be different between the cases where: i) the application operates based on a closed-content ecosystem (e.g., subscriber-based music or video streaming, where control of the content is solely with the content publisher) and ii) the application operates on a totally open content space, e.g., web.