From 882462082112f06069141f658ff635648965cb9f Mon Sep 17 00:00:00 2001
From: Flancian <0@flancia.org>
Date: Sat, 20 Aug 2022 18:34:31 +0200
Subject: [PATCH] autopushed

---
 agora pkg chapter.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/agora pkg chapter.md b/agora pkg chapter.md
index d7f9d4815..552b6571f 100644
--- a/agora pkg chapter.md	
+++ b/agora pkg chapter.md	
@@ -114,7 +114,7 @@ On a more pragmatic level:
 
 When interpreting the above and extensions, an Agora is liberal in what it accepts and when in doubt tries to default to being extra useful to the user -- meaning it is optimistic in association and surfaces all resources that have a claim to being associated with the context being queried. For example: #CamelCase will be provided in all contexts matching [[camel case]] and all known variations, and this relationship is symmetric by default, in the sense that the user might provide either and be later served matching resources in all associated contexts.
 
-To put simply, an Agora optimistically defines equivalence classes with good intention. Later we will cover two hypotheses associated with this being an optimal policy in social spaces.
+To put simply, an Agora optimistically defines equivalence classes with good intention. Later we will cover two hypotheses associated with this being an optimal default policy.
 
 Note that outlines plus linking are sufficient to encode a [[hypergraph]] in an easily parseable way, heterarchies encoding relationships between [[wikilinks]] at different levels. In the opinion of the author this structure is sufficient to encode a [[hypergraph]] in a human friendly way, which might do away with the need for programmatically generated [[block references]][^blockrefs].