Update 2021-06-07-v0.3.5-released.md

content/en/blog/2021-06-07-v0.3.5-released.md

@@ -19,17 +19,18 @@ Below, I call out to a summary of the versions and known issues.
 ### feat(gh-301): add tree command
 
 Occasionally, software systems encounter cycles in the graph.
-As depscloud doesn't currently follow subsets of edges, we occasionally encounter cycles in the graph.
-When this happens, the `topology` query truncates silently (not great).
-To help give more information to callers, we added a "tree" command that will return the entire subtree.
+When this happens, the deps.cloud `topology` query truncates silently (not great).
+To help give more information to callers, we added a "tree" command that will return the entire subtree (nodes and edges included).
 With the addition of this new `tree` command, we've updated the `topology` command to write an error when it encounters a cycle.
+Users will still be able to obtain partial orders... but will need to handle the err message at the end.
 
 ### feat(gh-15): support field indexes
 
-This started as an idea, and a quick implementation came together rather quick.
-After a quick refactor of the database support structures, adding support for this was much easier.
-This indexes a handful of fields (namely, `url` on sources and `language` and `name` for modules). 
-This allows clients to quickly search for nodes in their graph.
+Data stored in deps.cloud now has some minor indexing support to improve exploration.
+This mostly started as an idea, but was able to grow into a useful implemenation rather quick.
+In order to support indexes, we did need to refactor some elements around the database layer.
+We currently index a handful of fields (namely, `url` on sources and `language` and `name` for modules). 
+This allows clients to quickly search for nodes in their graph and use subsequent calls for traversals.
 
 **New Endpoints**