diff --git a/Folders:-Collected-Clippings.md b/Folders:-Collected-Clippings.md
index f4d7359..1867e52 100644
--- a/Folders:-Collected-Clippings.md
+++ b/Folders:-Collected-Clippings.md
@@ -25,7 +25,7 @@ of brews. Each of those brews will have a resource uri of just
 `/user/name/:brewid` — the folder path will not be exposed (for a
 couple of reasons).
 
-Or maybe not. [RESOLVE]
+Or maybe not. [RESOLVED: folders have visible paths, brews are direct by :id]
 
 
 
@@ -110,20 +110,25 @@ We could likely get away with a simple structure of an array of
 queries, each query being executed in order and compiled into one
 collection. The simplest version would be
 
+```
 [
   [tag1, tag2, tag3], 
   [tag6, tag7]
 ]
+```
 
 .. but lets look ahead a little bit and make that more explicit, like this..
 
+```
 [
   { "and": [tag1, tag2, tag3] }, 
   { "and": [tag6, tag7] }
 ]
+```
 
 .. so we could later extend that to this..
 
+```
 [
   { "and": [tag1, tag2, tag3], "not": [tag4, tag5]},    // or ..
   { "and": [tag6, tag7] },                              // or ..
@@ -131,6 +136,7 @@ collection. The simplest version would be
   { "omit": [tag9, tag10] },                            // 
   { "omit": [tag11] }
 ]
+```
 
 But that is getting way ahead of what would be needed. Probably ever.
 
@@ -150,7 +156,7 @@ userpage).
 
 There is some use cases where being able to place a given folder into multiple other folders (e.g. "Social Policies" into "Friday Game", "Open Table Group", "Thursday Group").
 
-Since all brews and all folders are retrieved as flat data tables and then assembled for the userpage, this approach won't actually the Laws of Time and Relative Dimensions in Space and we can cope. 
+Since all brews and all folders are retrieved as flat data tables and then assembled for the userpage, this approach won't actually violate the Laws of Time and Relative Dimensions in Space and we can cope. 
 
 More thought and discussion is called for.